Authentication issue with BDE and MSSQL 7 on Windows XP SP2 machine
Hello.
I'm having difficulty with BDE 5.01 database connectivity using the native MSSQL driver connecting to a MSSQL 7 database on a Windows XP SP2 machine. It's not passing the Windows authentication user/pass credentials to MSSQL correctly. If I use an ODBC driver connection to the same SQL Server then I have no problem. I believe that the issue may have something to do with the MSSQL 7 client install on that machine not populating the ntwdblib.dll file into the C:\Windows\System32 directory (although the DB Library Options Tab of the SQL Client shows it to be there). I've manually placed the file there (tried the following versions: 2000.80.194.0 and 1998.11.13.0) and it didn't help. I've uninstalled/reinstalled the MSSQL client and still the ntwdblib.dll is not being populated on install. I've thought about reinstalling MDAC since I've read that the ntwdblib.dll file needs some of its components, but have had trouble with this in Win XP SP2 (the exact same version downloaded from the MS website will give an incompatibility error). The Windows firewall remains disabled.
Any constructive help is appreciated.
Thank you
I'm having difficulty with BDE 5.01 database connectivity using the native MSSQL driver connecting to a MSSQL 7 database on a Windows XP SP2 machine. It's not passing the Windows authentication user/pass credentials to MSSQL correctly. If I use an ODBC driver connection to the same SQL Server then I have no problem. I believe that the issue may have something to do with the MSSQL 7 client install on that machine not populating the ntwdblib.dll file into the C:\Windows\System32 directory (although the DB Library Options Tab of the SQL Client shows it to be there). I've manually placed the file there (tried the following versions: 2000.80.194.0 and 1998.11.13.0) and it didn't help. I've uninstalled/reinstalled the MSSQL client and still the ntwdblib.dll is not being populated on install. I've thought about reinstalling MDAC since I've read that the ntwdblib.dll file needs some of its components, but have had trouble with this in Win XP SP2 (the exact same version downloaded from the MS website will give an incompatibility error). The Windows firewall remains disabled.
Any constructive help is appreciated.
Thank you
What edition of sql is this ?
ASKER
7.00.91
ASKER
Check that.....7.00.961
i mean Standard, Enterprise, MSDE, DataCentre, Developer or Desktop
ASKER
It's the Standard edition of SQL Server 7.
Standard Edition does not run on Windows XP , it is a server product that must be installed on a server edition of windows
ASKER
The MSSQL 7 server is running on a server. What we're trying to do is make a BDE connection to the server from a workstation.
what does your connection string look like ?
ASKER
The same as Windows 2K/Windows XP pre SP2 workstations that connect fine. It's beginning to look like a bug here since I've found this now on additional sites besides the initial one in question. I can connect using SQL authentication in all these cases. What's the best way to contact Borland support if you don't have a contract w/them?
Is it borland drivers you are using or is it microsoft drivers ?
ASKER
It's the native MSSQL driver in BDE which on the configuration tab appears to be SQLMSS32.DLL .
ok, I believe this is a microsoft DLL as opposed to written by borland. Your best bet is to contact microsoft on there support line. They will ask you to pay money, but tell then that this is a bug and they wont charge you.
Before that you may want to check the microsoft website to see if there is a hot fix for it.
Before that you may want to check the microsoft website to see if there is a hot fix for it.
ASKER
Not wanting to leave this issue abandoned.................
Note to all: Borland does not support the BDE any longer (as per their support staff).
My fix was to have the client switch to SQL authentication which they did and is fine now.
Thanks for all posts.
Note to all: Borland does not support the BDE any longer (as per their support staff).
My fix was to have the client switch to SQL authentication which they did and is fine now.
Thanks for all posts.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.