RE: Cannot connect to MSDE on a W2003 server
From: Cindy Gross (cgross_at_online.microsoft.com)
Date: 03/01/04
- Next message: Cindy Gross: "RE: Link Server Connection failure"
- Previous message: Paul Ibison: "Re: OS error 53 for SQL servers VPN replication?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 01 Mar 2004 23:27:25 GMT
* Did you apply the SP3 version of MSDE? If not TCP will be disabled on
Windows 2003. You must apply SP3 before TCP connections (the default from a
remote client) will work.
* What error do you get when you try to connect?
* Do you get the same error from Query Analyzer, OSQL, and Enterprise
Manager or just from your application?
* If you force TCP, named pipes, or shared memory does it start working or
change the error?
* Do both remote and local connections fail for each protocol? For MSDE
2000 SP3 remote connections are disabled by default, you have to enable TCP
and/or named pipes on the server side before remote connections will work.
To Enable TCP/IP Sockets Server Net-Library
1. On the taskbar, click "Start", and then click "Run".
2. In the "Open" text box, type "svrnetcn.exe" (without the quotation
marks). Note: By default, the svrnetcn.exe is available in the
following folder: <Installation Drive>/Program Files/Microsoft SQL
Server/80/Tools/BINN
3. Click "OK".
4. In the "SQL Server Network Utility" dialog box, click "General" tab.
5. Click the desired instance of Microsoft SQL Server 2000 Desktop Engine
(Windows) or MSDE 2000 SP3a or SQL Server 2000 in the
"Instance(s) on this server" list.
6. In the "Disabled Protocols" list box, click "TCP/IP", and then click
"Enable".
7. In the "Enabled Protocols" list box, click "TCP/IP", and then click
"Properties".
8. In the "<Server Name> - TCP/IP" dialog box, in the "Default Port" text
box, type "0" (without the quotation marks), and then click "OK".
9. In the "SQL Server Network Utility" dialog box, click "OK". Note: You
may receive a message stating that the changes made will be saved, but will
take effect only after restarting the SQL Server service. In the "SQL
Server Network Utility" message box, click "OK".
10. Restart the SQL Server service of the instance of Microsoft SQL Server
2000 Desktop Engine (Windows) or MSDE 2000 SP3a or SQL Server 2000.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Cindy Gross: "RE: Link Server Connection failure"
- Previous message: Paul Ibison: "Re: OS error 53 for SQL servers VPN replication?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
