The typical App-V error code consists of 2 x 4 bytes in the form hexadecimal: "0x000000-0x000000". The first six characters refer to the App-V source code and can be ignored. For error analysis the last 10 characters are interesting. So "00-0x000000". The first two characters show the type of error and the source. The last eight characters are the actual error code. Once an error code is returned as a decimal number, then this decimal number must be converted to a hexadecimal value for analysis.
Building the App-V error code
.
If the first character is an "8" (4 bits, number 10 in the graphic), it is not an error. If it is a "4", an error has been logged. A "2" indicates that it is a Windows error code.
The second character (4 bits, number 9 in the graph) shows the source from an App-V perspective. The following table breaks down the codes:
.
| Hex Code |
Category | More information |
| 01 | Integration | Client Integration Log |
| 02 | Orchestration | Client Orchestration Log |
| 03 | Client Service | Client Service Log |
| 04 | Virtualization Manager | Client-VirtualizationManager Log or Client-Vemgr Log |
| 05 | Shared Components | Admin and Operational Logs |
| 06 | Catalog | Client catalog |
| 07 | Publishing | Client Publishing Log, Client-PackageConfig Log, or FileSystemmetadataLibrary Log |
| 08 | Client Common | Admin and Operational Logs |
| 09 | Policy | PolicyLibrary Log |
| 0A | Virtualization Subsystem | virtual subsystem debug logs. |
| 0B | Subsystem Controller | Client SubsystemController Log |
| 0C | Streaming Manager | streaming debug logs |
| 0E | Client Host | |
| 0F | Client Configuration | Registry/PowerShell |
| 10 | Scripting | Client Scripting Log |
| 11 | Client User Interface | Client StreamingUX Log |
| 12 | Sequencer | Only on Sequencer |
| 13 | Reporting | Client Reporting Log |
| 14 | Manifest | ManifestLibrary Log |
App-V error code
The actual error code follows. This can be an App-V specific error code (first digit "0"), but also a Windows return value (first digit "2") as "#HResult" or a system error code. The latter usually starts with a lot of zeros and can be analyzed using the "Net HelpMsg ###" command.
The system error codes (0x0000xxxx) can be looked up here:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx
For #HRESULT error codes, here is information:
https://msdn.microsoft.com/en-us/library/cc231198.aspx
A typical script integration error code is "10-0000000C". The first three bits are "0". The error source is "10", which is "scripting". That fits for now. "0C" in decimal is 12.
PS C:\Users\Andreas> net helpmsg 12
The access code is illegal.
If it is an HRESULT code, the error code usually starts with 0x8. This describes the first bit in the HRESULT. If it is a HRESULT code, only the first 16 bits are still interesting with the actual error code.
Microsoft HRESULT Code
- S: fatal error. If set, means that an error has occurred. If not set, then a success message is returned. For App-V, this is often the first "8" in the HResult (binary = 1,000).
- R: is associated with the "N" bit. If N is not set, R must also be set to 0. If the N bit is set, this bit is defined by the NTSTATUS.
- C: customer defined. This bit indicates whether the value is custom or Microsoft-defined. The bit is set to customer-defined values or disabled for Microsoft-defined values.
- N: if set, indicates that the error code is an NTSTATUS value (as specified in http://msdn.microsoft.com/en-us/library/cc231200.aspx) and bit is set.
- R: reserved. Should be set to 0.
Facility Codes (excerpt) https://msdn.microsoft.com/en-us/library/cc231198.aspx
1. FACILITY_NULL - the default setting code
2. FACILITY_RPC - the source of the error code is an RPC subsystem.
3. FACILITY_DISPATCH - the source of the error code is a COM Dispatch.
4. FACILITY_STORAGE - the source of the error code is OLE memory.
5. FACILITY_ITF - the source of the error code is COM/OLE interface management.
6. FACILITY_WIN32 - this region is reserved to map unprotected error codes into HRESULTs.
7. FACILITY_WINDOWS - error codes in the Windows subsystem
8. (19 HEX) FACILITY_HTTP - source of the error code is HTTP support.
Example: 14-00000007
14 is manifest 07 and returns "The memory control blocks were destroyed." with "Net helpMsg". This error occurred with a corrupted AppXManifest.xml in the package.
Example: 27-80190191
2 - it was logged (eventlog).
07 - App-V element is App-V publishing.
8 - it is a HRESULT in Facility Hex:19 (Dec 25) according to Facility table "FACILITY_HTTP"
0191 Hex or 401 Decimal is the error code in the Facility.
http status codes can be found here:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa383887(v=vs.85).aspx
HTTP_STATUS_DENIED 401 The requested resource requires user authentication.
A final example directly from PowerShell:
Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
Operation attempted: RefreshPublishingServer.
Windows Error: 0x801901F4 -
Error module: Publishing. Internal error detail: 45500D27801901F4.
Please consult AppV Client Event Log for more details.
.
At line:1 char:1
+ Sync-AppvPublishingServer 1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidResult: (:) [Sync-AppvPublishingServer], ClientException
.
+ FullyQualifiedErrorId : RefreshPublishingServerError,Microsoft.AppV.AppvClientPowerShell.SyncAppvPublishingServer
.
Getting server publishing data failed.
URL: http://suranav01.uran.local:8091/
Error code: 0x45500D27 - 0x801901F4
Error code 27-0x801901F4
2 - it was logged (event log).
07- App-V element is App-V publishing.
8 - it is a HRESULT in Facility Hex:19 (Dec 25) according to Facility table "FACILITY_HTTP".
01F4 = Dec. 500 "HTTP_STATUS_SERVER_ERROR", 500, "The server encountered an unexpected condition that prevented it from fulfilling the request".
Note: Of course, it is easier to always look for the error on the Internet first.
Here are some examples:
050009000A Microsoft Knowledge
070000000B Microsoft
05-00090001 Microsoft Knowledge
04-000028 anandthearchitect.com Microsoft Knowledge
27-801901F7 microsoft.com Microsoft Docs
0C-80070005 Microsoft Knowledge
0C-8007012F microsoft.com Microsoft Docs
00-c0000142 Microsoft Docs
You may also find this link helpful: