The activeds and userenv errors can be safely ignored in this case because
they are simply warnings that dependent services have not yet been
registered, but will be registered later in FBA.
The class installer error looks like you probably neglected to add a
dependency in TD or perhaps you inadvertently disabled a required
dependency. Run depends.exe against that CI file to see what's missing.
Andy
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Henry Markov" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm evaluating XPe and sample hardware by building simple systems on
> various
> cPCI boards. One such configuration only has standard components except
> for a
> component I downloaded from Intel to support their 82541 GBe chip. The
> build
> was error free. The FBA log has the following errors:
>
> [PnpEnumThread: InstallDevice] SetupDiCallClassInstaller Error:
> 0xe0000217,
> Device: Plug and Play Software Device Enumerator
>
> [FBARegQueue: DllRegisterServer] C:\WINDOWS\System32\activeds.dll (Error:
> 0x80040154)
>
> [FBARegQueue: DllInstall] C:\WINDOWS\System32\userenv.dll (Error:
> 0x80040154)
>
> The explanation for error 0x80040154 in winerror.h is "Class not
> registered."
> There is no explanation for error 0xe0000217. Can anyone tell me what the
> problem could be?
>
> Henry
|