May 29, 2003 at 11:37 am
I have a Windows NT Workstation client trying to connect to a SQL Server 2000 database. My application needs both 16 and 32 bit ODBC connections to this database. I setup the 32 bit and 16 bit ODBC connections. On testing them, my application connects using the 32 bit connection but not the 16 bit. The front end is Centura. This uses the 32 bit connection. This in turn invokes Aurora DS, a document assembly system which uses the 16 bit ODBC connection. At first I thought it was something to do with Aurora but then used a third party tool to test the 16 bit connection and saw that it failed. I'm using TCP/IP protocol. Any help will be greatly appretiated as I have tried all I can and I'm already late on schedule due to this.
The message I get is as follows.
Action failed with error code: (action, error code) SQLConnect; -1
SQLError: 01000; [Microsoft][ODBC SQL Server Driver][dbnmp3]ConnectionOpen (sopen()).
SQLError: 08001; [Microsoft][ODBC SQL Server Driver][dbnmp3]Access denied.
May 30, 2003 at 6:17 am
Check this out.
May 30, 2003 at 12:39 pm
Thank you for your response. The thing is, I have the driver. This thing was installed in production by someone and now I'm trying to install it on a new machine. The difference between the two machines (actually networks) is that the prod one uses MDAC 2.1 and the Test Lab machine uses MDAC 2.7. Other than this, there must be something installed on the prod machines that is missing here and I can't figure out what it could be. Any ideas ?
May 31, 2003 at 12:53 pm
There were some statements that things had been removed from the MDAC that I don't recall. I would try to get a machine on MDAC 2.1 to see but other than that I have nothing to test with and very little info.
June 2, 2003 at 2:05 pm
Have you installed the SQL Server 6.5 client?
I believe that is required for a 16 bit ODBC conncetion.
June 3, 2003 at 5:55 am
We have only SQL Server 2000. But let me talk to the DBA and see if we can get 6.5 to try it. Is there any way I could check to see if 6.5 was instaled on the client in production. That way I could eliminate it as the reason. I'll also work on the MDAC 2.1 and see if that is the problem. But it won't help in the long run coz we need to switch to MDAC 2.7 to keep up with IT Corporate Standards at the company here. Will get back to you with the results.
June 13, 2003 at 7:33 am
Just want to let you know I fixed the problem. Apparently, even though my client network configuration was set to TCP/IP, when I set the 16 bit ODBC connection, I had to change the network for each one explicitly to dbmssoc3 instead of default. or some reason the 16 bit driver was assuming the default to be Named Pipes. I found the dbmssoc3.dll and placed it in C:\WinNT\System. Then I was a able to connect to it. Thanks for trying to help.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply