Understanding App-V Client Error Codes

The App-V Client error codes that appear as popups, in the Client Log file or Windows Event Log are formatted as follows:



A = Major Version of the component issuing the error
B = Minor Version of the component issuing the error
C = Patch (Service Pack) number
D = Build number
E = File ID
F = Line number
G = Info
H = Problem code

The info field is not officially defined, but seems to be a bit encoded format. After converting the info field characters into binary, it can be read thusly:

Bit 1 = Reserved (typically 0)
Bit 2 = Log, which is believed to be an App-V developer hint that the error is logged
Bit 3 = This STD bit indicates the PROBLEMCODE is a standard Windows error, rather than an App-V specific error
Bit 4 = Module ID (think DLL)
Bit 5 = Module ID (think DLL)
Bit 6 = Module ID (think DLL)
Bit 7 = Module ID (think DLL)
Bit 8 = Module ID (think DLL)

Here’s a table showing the complete Info fields for each module Id:

00-20-40-60 Unknown
01-21-41-61 Front-end component
02-22-42-62 Server
03-23-43-63 Client service
04-24-44-64 Client core (including OSD issues)
05-25-45-65 XML parser
06-26-46-66 User library
07-27-47-67 Core files system interface
08-28-48-68 FS interface
09-29-49-69 FS driver
0A-2A-4A-6A Network transport agent
0B-2B-4B-6B Codec
0C-2C-4C-6C SystemGuard interface (and scripting)
0D-2D-4D-6D SystemGuard driver
0E-2E-4E-6E Client interface
0F-2F-4F-6F Virtual service manager
10-30-40-70 App-V Sequencer
11-31-51-71 Synchronisation manager
12-32-52-72 Desktop configuration controller (DCC)
13-33-53-73 RPC
14-34-54-74 Platform library
15-35-55-75 ?
16-36-56-76 ?
17-37-57-77 ?
18-38-58-78 Custom scripts
19-39-59-79 Launcher

For more information about specific App-V error codes, see this resource. I will try to copy down more of these resourses so they are searchable in html / Google as time goes by. 🙂

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)

Leave a comment

Your email address will not be published. Required fields are marked *