NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand problem with ntwdblib.dll

We took the TextCopy.cpp program supplied with SQL Server and set it for
integrated security using the following code.

// fill the login record
DBSETLUSER (pLoginRec, strLogin); // set the login
DBSETLPWD (pLoginRec, strPassword); // set the password
DBSETLAPP (pLoginRec, "textcopy"); // set the app name
DBSETLHOST (pLoginRec, "textcopy"); // set the host name
// To use secure, or trusted, connection, uncomment the following
line.
DBSETLSECURE (pLoginRec);

// attempt to connect to SQL Server
PDBPROCESS pDbproc;
pDbproc = dbopen (pLoginRec, strServer)

The database we are connecting to is MSDE 2000. The program works for me
on my workstation. It does not work for
me on another workstation. We
tried eight workstations and it works on half of them. The user account
doesn't appear to matter, but rather the workstation. We checked the
registry, the machines are all slightly different on the
MSSQLServer\Client\ConnectTo. We tried to make the keys the same as one
of the working workstations, but it did not help. On the machines that
it did not work on, it appears that the program is trying to use SQL
Server logins rather than integrated logins.

We also noticed that the systems that work have ntwdblib.dll
(2000.80.194.0) with out National Instruments Test Stand OR ntwdblib.dll
(1998.11.13.0) with National Instruments Test Stand. The systems that do
not work have ntwdblib.dll (2000.80.194.0) with National Instruments
Test Stand. It appears that the SQL tools installs ntwdblib.dll and
National instruments Test Stand will install the 1998 version if it
doesn't exist. The problem appears to actually be because of a different
library call
ed by ntwdblib.dll.

Does anyone have any ideas/suggestions?


TIA
Rich Hilt
0 Kudos
Message 1 of 2
(3,420 Views)
Rich -
TestStand 1.x installs MDAC 2.0 and TestStand 2.0 installs MDAC 2.5. Looking thru all of the CAB files, I do not see them installing the NTWDBLIB.DLL, so I do not think that we install this DLL. One suggestion is to figure out who installs this DLL, why the versions are different on the various systems and whether there is a versioning problem between various SQL server and MDAC components

Scott Richardson
Scott Richardson
https://testeract.com
0 Kudos
Message 2 of 2
(3,420 Views)