Error logging results to database in TestStand

[ssidev]

I am attempting to configure a distrubted TestStand application to log
results to a MS Access database and I get the following error:

"An error occurred in the 'Open UUT Result SQL Statement' step of the
'Log UUT Results' sequence in 'Database.seq'.
Error executing substep 'Post'. Automation error code -2147352573
0x80020003
Member not found.
User-defined error code. Error Code: -12"

I followed all the steps in the TestStand User's Manual to link to a
MS Access database. I have successful linked to Access databases on
other machines following the same steps. However, I have tried
everything on this machine and I still can't get it to work. I have
reinstalled MS Access as well as TestStand and my distributed
application.

I am using TestStand 1.0.1, Win NT 4 service pack 5, MS Access 2000.

I tried to install MDAC version 2.1 as suggested in the discussion
below, but I got a message saying that my system did not support the
installation of that version of MDAC.

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000FC540000&ECategory=TestStand

Any help would be greatly appreciated.

Regards,
Kevin

[Scott Richardson]

Kevin -
I do not know why this happens on this one system. I can tell you
that the -12 error is an ODBC Driver error being returned to the
LabWindows/CVI SQL Toolkit that the Database step types use. The
toolkit is a wrapper for the ADO ActiveX server that comes from MDAC.
The member not found error states that the wrapper is attempting to
access the server and when asking the server for the ID of a method,
it says that it does not exist.

I assume that MS Access is having to problems accessing the database
but it does not use ADO, but instead uses DAO which is a different
library than MDAC.

If there is any way to uninstall/reinstall MDAC, this might help.

Do you know what version of MDAC is on the system? Microsoft's
website ususally has an standalone application that you can download
to help figure this out.

Scott Richardson

[ssidev]

Scott,
Thank you for your suggestion. It was very helpful and I was
eventually able to solve the problem.

I went to the microsoft website and downloaded the Component Checker
which is a utility for diagnosing MDAC installations. It told me that
I had MDAC 2.5 installed. The MS documentation on the web claimed
there was some means within Component Checker to uninstall or rollback
MDAC 2.5, but I could not find any and the documentation circularly
referred to itself for the instructions, which were no where to be
found.

Ultimately, I manually deleted every DLL associated with MDAC 2.5 (as
listed by the Component Checker utility). Then I installed MDAC 2.0,
which is included in the TestStand 1.01 software. After reboting and
reconfiguring the test results database, the problem was solved.

Kevin

[Scott Richardson]

Kevin -
I am glad it worked. TestStand 1.0.1 is an older version. I believe
that some of our components that use MDAC had to use the generic
interfaces exposed by MDAC 2.0. Starting with MDAC 2.5 and later
Microsoft had to rework their interfaces in an attempt to allow for
use of its new version and future versions, but this caused problems
for some components compiled against MDAC 2.0. These components
needed to be updated to reference the version specific interfaces to
better handle these version changes but I do not this that we caught
on to Microsoft's changes until TestStand 2.0. TestStand 2.0 uses
MDAC 2.5.

Scott Richardson