Trying to determine the missing component!

[Oliver Start]

Hello all!

I'm new to XP embedded but am intent on using it more in the future. I have
recently purchased an embedded pc with XP embedded pre-installed. I
specified that it should have .NET installed, file/printer sharing and usb
device support. These are all present including MDAC 2.81 SP1.

The problem is that when trying to install a software package i'm using, it
comes up with the error:

Error 1919. Error configuring ODBC data source blah_dbf, ODBC error 13:
Could not load the setup or translator library. Verify that the file
blah_dbf exists and that you can access it.

I realise that it cannot create the database - I used the MS component
checked to ensure all MDAC components where uniform - they are all correctly
matched before installation. There was one file (ODBC simple service
provider I think) that changed to version 2.00 something during the
installation. Although I suspected this might be the problem, I later
restored to the clean image.

I immedately went to ODBC data sources administration and attempted to
create a new data source using Microsoft dBase Driver (*.dbf). It presented
me with the error 126 -

The setup routines for..... (there was something here, will update when I
check again) ODBC driver could not be loaded due to system error code 126.

So it looks like non of the drivers where installed... but component checker
says that everything is 2.81 and good.

I am at a dead end now, and am desperate for some guidance - I beleive that
there must have been something missed out from the original image - does
anybody have any ideas?

Many thanks in advance

 

[Brad Combs]

Hi Oliver,

Admittedly, I really don't know alot about MDAC and the problems it has on
XPe. I will say this... Since you are getting a 126 (Specified Module Cannot
Be Found) when trying to create your own ODBC connection I would load
Filemon on the device and look at the output while you go through the
exercise of adding a connection. You'll be looking specifically for failures
probably coming from LoadLibrary() or similar. Here is a link to Filemon:

http://www.sysinternals.com/Utilities/Filemon.html

HTH,
Brad