How to convert Windows error code into Simple English decription

By -
While troubleshooting, most of the times you can see Windows OS is throwing error in Hexadecimal code. You may find this error in event viewer or msi logs, or CBS logs. Most of the time there wont be any description for this error code in the logs or events. You can convert this error codes into Simple error description. Here I am going to show how to do this. Lets take the below error code as an example.




You can see from the above error message that calling of vbscript.dll was failed with error code 0x80004005. The error code is in Hexadecimal. You have to convert the code into decimal before finding out its error description. Lets convert the code 0x80004005 in to decimal. You donot need to convert whole number into decimal. Take only last four or three last digits from the error code. Here we are going to convert last 3 digit of the error code "005". 

Open the calculator in Programmer mode.  



Enter the value in Hexadecimal


Click on Decimal to get the decimal value

Copy the decimal value. Open a command prompt and run the command net helpmsg <decimalnumber>
in our example command will be net helpmsg 5

You can see the error description for decimal value 5 as "Access is denied". You can further investigate the issue according to the error description. There might be permission issue to access the regitsry location of vbscript.dll in our example, hence the windows throwed the error. Below are some more error codes and its description

0x80070490 - Element not found. 
0x80004005  -  Access is denied. 
0x8007054f  -  An internal error occurred. 
0x80070bc2   -  The requested operation is successful. Changes will not be effective until the system is rebooted. 
0x80070643  -  Fatal error during installation. 






Comments

Post a Comment

Popular posts from this blog

Boot configuration Data Store --BCDEdit /set

By -
The  BCDEdit /set  command sets a boot entry option value in the Windows boot configuration data store (BCD). Use the  BCDEdit /set  command to configure specific boot entry elements, such as kernel debugger settings, data execution protection (DEP) and processor address extension (PAE) options, and to load alternate hardware abstraction layer (HAL) and kernel files. You can use these boot entry options when you are testing and debugging your driver for Windows Vista, Windows 7, and later versions of Windows. bcdedit /set [{ID}] datatype value Parameters [ { ID }] The  { ID }  is the GUID that is associated with the boot entry. If you do not specify an  { ID } , the command modifies the current operating system boot entry. If a boot entry is specified, the GUID associated with the boot entry must be enclosed in braces  { } . To view the GUID identifiers for all of the active boot entries, use the  bcdedit /enum  command. datatype value The fol
Read more

ADSI Edit

By -
Image
ADSI Edit (adsiedit.msc) Updated: March 19, 2010 Applies To: Windows SBS 2008, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2 Active Directory® Service Interfaces Editor (ADSI Edit) is a Lightweight Directory Access Protocol (LDAP) editor that you can use to manage objects and attributes in Active Directory. ADSI Edit (adsiedit.msc) provides a view of every object and attribute in an Active Directory forest. You can use ADSI Edit to query, view, and edit attributes that are not exposed through other Active Directory Microsoft Management Console (MMC) snap-ins: Active Directory Users and Computers, Active Directory Sites and Services, Active Directory Domains and Trusts, and Active Directory Schema. This topic includes the following sections: Installing ADSI Edit Using ADSI Edit
Read more

Userenv logging (User Environment logging)

By -
When you enable userenv logging, you can perform debug logging of the user profile and the system policy processes. Userenv log files also contain information about the status of each Group Policy extension, such as Application Deployment, Security, and Folder Redirection. Userenv log files reveal what is occurring in the background as a user logs on   Userenv.log file located in the %SystemRoot%\Debug\UserMode folder Userenv log files contains information about the following: Group Policy settings that are not processed or not applied as expected Folder redirection that does not occur Profile or registry hive load, unload, or deletion failures Logon script, or script not applied as expected Default behaviors occurring because a slow link was detected Roaming profile issues Slow logon issues Whether a given GPO is accessible, and if not, why access was denied. The name of the domain controller that is accessing SYSVOL. The Userenv log has a maximum size of 1 megabyt
Read more