December 18, 2005 at 6:29 pm
I have SQL Server 2000 installed on Windows Server 2003.
Iam not able to connect to the SQL Server using tcp/ip.
Error "Sql Server does not exist or access denied."
SQL Server is not listening on port 1433 or any other port.
> In the Server network utility, tcp is enabled on port 1433.
> I installed the SP4 for sql server 2000.
> Firewall is disabled.
----------------------------------------------
> The SQL Server log is shown as below
2005-12-18 18:55:13.31 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2005-12-18 18:55:13.31 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-12-18 18:55:13.31 server All rights reserved.
2005-12-18 18:55:13.31 server Server Process ID is 424.
2005-12-18 18:55:13.31 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL
Server\MSSQL\log\ERRORLOG'.
2005-12-18 18:55:13.32 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2005-12-18 18:55:13.51 server SQL Server configured for thread mode processing.
2005-12-18 18:55:13.53 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2005-12-18 18:55:13.56 server Attempting to initialize Distributed Transaction Coordinator.
2005-12-18 18:55:15.62 spid2 Starting up database 'master'.
2005-12-18 18:55:15.75 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-12-18 18:55:15.75 spid5 Starting up database 'model'.
2005-12-18 18:55:15.76 spid2 Server name is 'MYSQLSERVER'.
2005-12-18 18:55:15.76 spid8 Starting up database 'msdb'.
2005-12-18 18:55:15.76 spid9 Starting up database 'pubs'.
2005-12-18 18:55:15.76 spid10 Starting up database 'Northwind'.
2005-12-18 18:55:15.78 server SQL server listening on Shared Memory, Named Pipes, Rpc.
2005-12-18 18:55:15.78 server SQL Server is ready for client connections
2005-12-18 18:55:15.93 spid5 Clearing tempdb database.
2005-12-18 18:55:16.31 spid5 Starting up database 'tempdb'.
2005-12-18 18:55:16.39 spid2 Recovery complete.
2005-12-18 19:10:07.10 spid51 Using 'xpstar.dll' version '2000.80.194' to execute extended stored procedure
'xp_readerrorlog'.
----------------------------------------------
> Portqry tool reports as below
IP address resolved to MYSQLSERVER
querying...
TCP port 1433 (ms-sql-s service): NOT LISTENING
--------------------------------
Any ideas or suggestions would greatly help. Thanks!!
December 18, 2005 at 7:36 pm
This doesn't show SQL Server even attempting to listen on TCP/IP. Verify the configuration. If it's correct, be sure to restart SQL Server.
K. Brian Kelley
@kbriankelley
December 18, 2005 at 9:55 pm
> Tcp is enabled on port 1433 through server network utility.
> Server restarted after any change.
But it would not listen on 1433
TCP port 1433 (ms-sql-s service): NOT LISTENING
No relevant errors in the Sql Server error log or the windows error log.
Looks like this is a known bug reported by Microsoft which is resolved by installing sp3 or sp4. But it didnt help in my case.
December 18, 2005 at 11:02 pm
Typically if it wouldn't be able to listen, that's because another process has that port. However, in those cases you'd see the error reported in the SQL Server event log. One thing your SQL log reveals, though, is SQL Server still believes itself to be the release version, not one with a service pack (Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48). Check your sqlstp.log file in your C:\Windows directory to see if the service pack install completed successfully. Also, be sure to verify the firewall didn't get reactivated. We simply moved computers from one domain to another and saw the firewall reactivate on some of our XP machines.
K. Brian Kelley
@kbriankelley
December 19, 2005 at 9:17 am
Thanks Brian for catching it. I thought clicking the SP4 link installs the software, but all it does is extract files to a folder and the setup.bat needs to be run. A silly mistake, but if it helps somebody else, Iam glad.
December 20, 2005 at 8:52 pm
Thanks Raj, for creating this thread. I was totally stumped by this problem for 3 days. Googled like mad trying to find a solution and finally chanced on this forum. Its pretty ironic that theres no mention of this in the MS forums (that I could find), for an apparently somewhat widespread problem. Anyway, after applying SP4 SQL2K now binds to port 1433 as its supposed to. Good luck to anyone else having the same problem.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy