Common FBA Log File Errors

Article
10/07/2008

5/10/2007

The FBALOG.txt file logs all of the FBA actions, including any errors that may have occurred. The table below shows common FBA errors in a FBALOG.TXT file:

FBALOG.TXT Error	Win32 error code	Description
[FBALaunch] ExitCode: 0x4a020	Not Applicable	This error indicates that the network protocol was already installed and FBA attempted to initialize it again. This error can be ignored.
[FBALaunch] ExitCode: 0xc0000005".	Win32 Error: 5 "Access Denied".	This error indicates a third-party driver was used that is not compatible with the version of NDIS supplied with Windows XP Embedded.
[CallEntryPointThread] ewfOpen returned not valid file handle. ConfigureEwf() End, status = 0x57. Error: 0x57	"The parameter is incorrect." ERROR_INVALID_PARAMETER.	This error indicates that EWF.dll is unable to create a partition entry. To resolve this problem, see Troubleshooting Enhanced Write Filter.
[PnpEnumThread: InstallDevice] SetupDiCallClassInstaller Error: 0x2	Win32 Error: 2 ERROR_FILE_NOT_FOUND "The system cannot find the file specified."	This error indicates that your device is missing a dependency. The driver or class installer has a dependency on a file that is not in the run-time image. Usually this occurs when you build your run-time image without the Devices.pmq file created by TAP.exe, left out a dependency in Target Designer, or accidentally disabled a required dependency. To resolve this problem, use Target Analyzer (TAP.exe). For more information see Hardware Detection with Target Analyzer. Also, you can try running the Microsoft® Visual Studio® Depends utility (Depends.exe), against the file cited in the error. Search for required files that are missing from your run-time image.
[FBAInstallSecurity] SCE Error: 0x7e	Win32 Error: 126 "The specified module could not be found."	This error indicates that your device is missing a dependency. See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.
[FBARegQueue: DllInstall] C:\WINDOWS\System32\eventcls.dll Error: 0x8000ffff [FBARegQueue: DllInstall] C:\WINDOWS\System32\swprv.dll Error: 0x8000f	Not Applicable	"A catastrophic failure has occurred." This COM error indicates a dependency is missing. See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.
[FBARegQueue: DllRegisterServer] C:\WINDOWS\System32\activeds.dll Error: 0x80040154 [FBARegQueue: DllInstall] C:\WINDOWS\System32\userenv.dll Error: 0x80040154	Not Applicable	"Class not registered." This error indicates that your device is missing a dependency. See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.
[FBAChangeDisplaySettings] Settings not found!	Not Applicable	This error is a warning that FBA was unable to automatically configure the video adapter for the settings that were specified in the configurable UI of your video adapter. This could be due to any of the following: A PnP (user-mode) component is missing in your configuration. PnP is required in order for FBA to perform this action. An "FBA: PnP" or "PnP (kernel-mode)" component is disabled. To view these components, you must increase the visibility threshold in Target Designer to 200. The video driver component includes a setting that is not supported by the adapter. The driver settings can be for refresh rate, color depth or video resolution. If the driver for your adapter does not accept the setting as being valid, it will fail during FBA. In rare cases, a monitor may require its specific component driver to be added to the configuration instead of using the generic "Default Monitor" component that usually works with most monitors. If you componentized the video driver yourself, it is possible that there is a missing dependency in the driver package. This will force the operating system to use the VGASave.SYS driver in place of your driver. If the system is using VGASave.SYS, this indicates a problem with your component. You can verify if this is the case by several methods: If the Device Manager component is in the configuration, use Device Manager to verify that the display adapter is installed correctly. If the Control Panel Display component is in the configuration, use it to indicate whether the system is using VGASave.SYS or your driver. Check the FBALOG.TXT file to verify that the video driver was setup correctly in FBA. Browse the entries in the PNP phase near the top quarter of the log. Locate the Ven/Dev ID for your video adapter and see if there are any errors related to it when FBA PnP is attempting to set it up. If there are errors, this may indicate a missing dependency in the driver package.
[InstallEnumeratedDevices] SetupDiCallClassInstaller Error: 0xe000	ERROR_INVALID_CLASS_INSTALLER	This error indicates that your device is missing a needed class installer. See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.
[PnpEnumThread: InstallDevice] SetupDiCallClassInstaller Error: 0xe0000217	ERROR_BAD_SERVICE_INSTALLSECT	Indicates that the driver file associated with the device INF 'is not present on your device. This is usually resolved by running Target Analyzer Probe (Tap.exe) on the target machine to identify all devices that are installed. This error can also appear when running Tap.exe on Windows 2000 systems. Because Windows XP contains driver resource differences from Windows 2000, you must run Tap.exe on a Windows XP system.
[FBAPidGen] PIDGenW returned: [0] [FBASetProductKey] FBAPidGen Failed! [FBASetProductKey] Invalid product key	Not Applicable	This error indicates a not valid Product ID (PID) was entered. There are two types of licenses required for Windows XP Embedded: Tools Product Ids These are used to install the tools onto your development system. Product Ids (PID) These are used to license run-time images in Target Designer. The two types of licenses are not interchangeable. Contact your distributor and obtain Product IDs for your embedded runtimes. These Product Keys are entered in Target Designer before you deploy your run-time image. For more information, see Licensing a Run-Time Image.
"FBAInstallSecurity] SCE Error: 0x4b8 "	Not Applicable	This error can be ignored. If the run-time image is on a partition other than the C drive and the run-time image does not have the file system component for the file system on the C drive partition, you may receive an error in the FBA Log that is similar to this. This error can be safely ignored because it means that the run-time image was not able to read files on the boot partition. For example, if the run-time image is on the D drive and D:\ is FAT but C:\ is NTFS and the run-time image does not have NTFS support then this error occurs.
[FBASKIPDEVICE] For example: [FBASKIPDEVICE] ROOT\MOUSE\0000		When this message is displayed, most likely the hardware device was already installed. It is also possible, but not very likely, that the device is listed in the [InstalledDevicesToSkip] section of syssetup.inf.
[ScanQueue: Missing File] D:\WINDOWS\help\comexp.ch	Not Applicable	This message is displayed because a help file is missing. The help file will be provided again in a future release. This error can be ignored.
[ScanQueue: Missing File] D:\WINDOWS\help\comexp.hlp	Not Applicable	This message is displayed because a help file is missing. The help file will be provided again in a future release. This error can be ignored.

[FBALaunch]

ExitCode: 0x4a020

Not Applicable

This error indicates that the network protocol was already installed and FBA attempted to initialize it again.

This error can be ignored.

[FBALaunch]

ExitCode: 0xc0000005".

Win32 Error: 5

"Access Denied".

This error indicates a third-party driver was used that is not compatible with the version of NDIS supplied with Windows XP Embedded.

[CallEntryPointThread]

ewfOpen returned not valid file handle.

ConfigureEwf() End, status = 0x57.

Error: 0x57

"The parameter is incorrect."

ERROR_INVALID_PARAMETER.

This error indicates that EWF.dll is unable to create a partition entry.

To resolve this problem, see Troubleshooting Enhanced Write Filter.

[PnpEnumThread: InstallDevice] SetupDiCallClassInstaller

Error: 0x2

Win32 Error: 2

ERROR_FILE_NOT_FOUND

"The system cannot find the file specified."

This error indicates that your device is missing a dependency. The driver or class installer has a dependency on a file that is not in the run-time image. Usually this occurs when you build your run-time image without the Devices.pmq file created by TAP.exe, left out a dependency in Target Designer, or accidentally disabled a required dependency.

To resolve this problem, use Target Analyzer (TAP.exe). For more information see Hardware Detection with Target Analyzer.

Also, you can try running the Microsoft® Visual Studio® Depends utility (Depends.exe), against the file cited in the error. Search for required files that are missing from your run-time image.

[FBAInstallSecurity] SCE

Error: 0x7e

Win32 Error: 126

"The specified module could not be found."

This error indicates that your device is missing a dependency.

See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.

[FBARegQueue: DllInstall] C:\WINDOWS\System32\eventcls.dll

Error: 0x8000ffff

[FBARegQueue: DllInstall] C:\WINDOWS\System32\swprv.dll

Error: 0x8000f

Not Applicable

"A catastrophic failure has occurred."

This COM error indicates a dependency is missing.

See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.

[FBARegQueue: DllRegisterServer]

C:\WINDOWS\System32\activeds.dll

Error: 0x80040154

[FBARegQueue: DllInstall] C:\WINDOWS\System32\userenv.dll

Error: 0x80040154

Not Applicable

"Class not registered."

This error indicates that your device is missing a dependency.

See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.

[FBAChangeDisplaySettings] Settings not found!

Not Applicable

This error is a warning that FBA was unable to automatically configure the video adapter for the settings that were specified in the configurable UI of your video adapter.

This could be due to any of the following:

A PnP (user-mode) component is missing in your configuration. PnP is required in order for FBA to perform this action.
An "FBA: PnP" or "PnP (kernel-mode)" component is disabled. To view these components, you must increase the visibility threshold in Target Designer to 200.
The video driver component includes a setting that is not supported by the adapter. The driver settings can be for refresh rate, color depth or video resolution. If the driver for your adapter does not accept the setting as being valid, it will fail during FBA.
In rare cases, a monitor may require its specific component driver to be added to the configuration instead of using the generic "Default Monitor" component that usually works with most monitors.
If you componentized the video driver yourself, it is possible that there is a missing dependency in the driver package. This will force the operating system to use the VGASave.SYS driver in place of your driver. If the system is using VGASave.SYS, this indicates a problem with your component. You can verify if this is the case by several methods:
- If the Device Manager component is in the configuration, use Device Manager to verify that the display adapter is installed correctly.
- If the Control Panel Display component is in the configuration, use it to indicate whether the system is using VGASave.SYS or your driver.
- Check the FBALOG.TXT file to verify that the video driver was setup correctly in FBA. Browse the entries in the PNP phase near the top quarter of the log. Locate the Ven/Dev ID for your video adapter and see if there are any errors related to it when FBA PnP is attempting to set it up. If there are errors, this may indicate a missing dependency in the driver package.

[InstallEnumeratedDevices] SetupDiCallClassInstaller

Error: 0xe000

ERROR_INVALID_CLASS_INSTALLER

This error indicates that your device is missing a needed class installer.

See the previous suggestions in Win32 Error: 2 to include Devices.pmq in your run-time image, run Target Analyzer, or run the Depends utility.

[PnpEnumThread: InstallDevice] SetupDiCallClassInstaller

Error: 0xe0000217

ERROR_BAD_SERVICE_INSTALLSECT

Indicates that the driver file associated with the device INF 'is not present on your device.

This is usually resolved by running Target Analyzer Probe (Tap.exe) on the target machine to identify all devices that are installed.

This error can also appear when running Tap.exe on Windows 2000 systems. Because Windows XP contains driver resource differences from Windows 2000, you must run Tap.exe on a Windows XP system.

[FBAPidGen] PIDGenW returned: [0]

[FBASetProductKey] FBAPidGen Failed!

[FBASetProductKey] Invalid product key

Not Applicable

This error indicates a not valid Product ID (PID) was entered.

There are two types of licenses required for Windows XP Embedded:

Tools Product Ids These are used to install the tools onto your development system.
Product Ids (PID) These are used to license run-time images in Target Designer.

The two types of licenses are not interchangeable. Contact your distributor and obtain Product IDs for your embedded runtimes. These Product Keys are entered in Target Designer before you deploy your run-time image. For more information, see Licensing a Run-Time Image.

"FBAInstallSecurity] SCE

Error: 0x4b8 "

Not Applicable

This error can be ignored.

If the run-time image is on a partition other than the C drive and the run-time image does not have the file system component for the file system on the C drive partition, you may receive an error in the FBA Log that is similar to this. This error can be safely ignored because it means that the run-time image was not able to read files on the boot partition. For example, if the run-time image is on the D drive and D:\ is FAT but C:\ is NTFS and the run-time image does not have NTFS support then this error occurs.

[FBASKIPDEVICE]

For example: [FBASKIPDEVICE] ROOT\MOUSE\0000

When this message is displayed, most likely the hardware device was already installed. It is also possible, but not very likely, that the device is listed in the [InstalledDevicesToSkip] section of syssetup.inf.

[ScanQueue: Missing File] D:\WINDOWS\help\comexp.ch

Not Applicable

This message is displayed because a help file is missing. The help file will be provided again in a future release.

This error can be ignored.

[ScanQueue: Missing File] D:\WINDOWS\help\comexp.hlp

Not Applicable

This message is displayed because a help file is missing. The help file will be provided again in a future release.

This error can be ignored.

Share via

Common FBA Log File Errors

See Also

Other Resources

Additional resources