Groups | Blog | Home
all groups > sql server odbc > january 2004 >

sql server odbc : Please help-ODBC Error


Lucy
1/5/2004 6:41:10 PM
Folks - please, I desperatly need your help and ideas

We recently installed a SQL Server in our DMZ.
The DMZ servers are part of a DMZ workgroup and not a part of our internal domain
I must have an ODBC connection between this SQL Server and my PC so I am able to use MS Access Version XP to review/edit SQL data on the fly
The guys opened the firewall for SQL Port 1422 originating from our LAN into the DMZ
I have been able to sucessfully setup an ODBC connection on the DMZ SQL server on both the SA and workgroup Admin accounts.
When I try to setup the ODBC connection between my PC and the server using the ODBC wizard
I have tried both SA the workgroup Admin accounts and checked the SQL Port 1422 and use the IP Address of the DMZ SQL Server
To do a half hour test (I had to do a lot of begging) I had the guys open up the firewall from the LAN to the DMZ. I was able to map a drive using the SQL Server workgroup Admin account but I still had the same error message.

Connection Failed
SQL State: ‘01000â€
SQL Server Error: 1100
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect())
Connection failed
SQL State: ‘08001â€
SQL Server Error:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found

Thanks for your thoughts,
Luc
tlnguyen
1/6/2004 7:57:23 AM
Lucy,
In a SQL Server 2000 custom installation, if TCP/IP is the
only selected protocol and all other protocols are
disabled, SQL Server may not initialize and listen on
TCP/IP sockets. Microsoft's solutions are as follow:

-To identify if SQL Server is not listening on TCP/IP,
check to see if the value for TcpPort in the following
registry key is incorrectly set to blank or empty:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\[Instance Name]
\MSSQLServer\SuperSocketNetLib\Tcp\REG_SZ TcpPort=

-Start Registry Editor (Regedt32.exe).

-Locate the TcpPort value in the following key in the
registry:
Named instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\[InstanceName]
\MSSQLServer\SuperSocketNetLib\Tcp\TcpPort

Default instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServ
er\SuperSocketNetLib\TCP\TcpPort

-On the Edit menu, click String. Enter either of the
following values:
a) Type the port number you want. -or-
b) Enter a value of 0 to have SQL Server dynamically
detect and assign a port the next time SQL Server starts.

-Click OK.

-Quit Registry Editor.


Hope this helps
AddThis Social Bookmark Button