| Author: |
Carlos J. Quintero (Microsoft MVP) |
Applies to: |
Microsoft Visual Studio .NET 2002 |
| Date: |
January 2014 |
|
Microsoft Visual Studio .NET 2003 |
| |
|
|
Microsoft Visual Studio 2005 |
| |
|
|
Microsoft Visual Studio 2008 |
| |
|
|
Microsoft Visual Studio 2010 |
| |
|
|
Microsoft Visual Studio 2012 |
| |
|
|
Microsoft Visual Studio 2013 |
Introduction
When you try to load an add-in, you can get an error of the form:
Error Message: <Unknown error>
Error number: 8013XXXX
More Information
The error number is an HRESULT, a 32-bit value divided into three fields (see MSDN documentation):
- Severity code (bit 31). Indicates success or failure:
- Reserved bits (bits 27-30)
- Facility code (bits 16-26). Indicates the subsystem that caused the error:
- For Common Language Runtime (CLR) errors, it will be 0x13 (FACILITY_URT = Universal RunTime)
- Error code (bits 0-15):
- You can get the list of error codes in the CorError.h file ("C:\Program Files (x86)\Microsoft SDKs\Windows\<version>Include" folder)
So, CLR errors will be of the pattern 0x8013XXXX, where XXXX is the error code. Some common error codes are (see the causes in the article HOWTO: Troubleshooting Visual Studio and Office add-ins):
- 1018: COR_E_ASSEMBLYEXPECTED
- 101b: COR_E_NEWER_RUNTIME
- 141a: CORSEC_E_INVALID_STRONGNAME
- 1515: COR_E_NOTSUPPORTED
- 1522: COR_E_TYPELOAD
- 150a: COR_E_SECURITY
Go to the 'Visual Studio Extensibility (VSX)' web site for more articles like this (Articles section)
|
