Identify Win32 Error Codes in FBA with Net Command

5/10/2007

During the FBA phase, the log file FBALOG.txt is created. It lists registered binary files, networking protocols, Plug and Play devices, and any errors. The FBALOG.txt file is located in the \Windows\FBA\ directory.

Most FBA error codes correspond to standard Win32 error codes and can be interpreted by using Win32 error codes. You can use the Net command to identify Win32 error codes in the FBA log file.

Error codes in an FBALOG.TXT file are usually in hexadecimal form. To find the correct Win32 error code, convert FBA error codes to decimal form by using Microsoft Calculator. By using the scientific view, you can convert the error code numbers from hexadecimal to decimal.

The following list shows the additional steps that might be needed to find the correct decimal representation of an FBA error:

• When errors contain the most significant digits such as 0xc0000005, drop the most significant 4 digits (0xc000) then calculate the decimal equivalent. In this case, the correct decimal number for the Win32 error would be 5.
• When errors are large negative decimal numbers such as -1073741819, convert the error to hexadecimal then drop the required most significant digits. In this case, the correct decimal number for the Win32 error would be -1073741819 converted to 0xC0000005 which results in 5.

Examples of using the net command to find Win32 error codes are shown below.

In this example:

C:\> net helpmsg 126
"The specified module could not be found." 

An error code of 126 (0x7e hex) indicates a dependency issue to be resolved.

In this example:

C:\ >net helpmsg 5
Access is denied.

An error code of 5 indicates the use of a third-party driver that is not compatible with the version of NDIS supplied with Windows XP Embedded.

The following table shows some common Win32 errors that may appear in an FBA file.

See Also

Concepts

Common FBA Log File Errors

Other Resources

Troubleshooting FBA