Re: SQL 2000 server TCP bind problem
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 09/08/04
- Next message: Tillman Erb: "Re: xp_fileexist to SAMBA-mounted drive"
- Previous message: mmazick: "SQL 2000 server TCP bind problem"
- In reply to: mmazick: "SQL 2000 server TCP bind problem"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 07 Sep 2004 19:42:22 -0600
Is the error in your log:
SuperSocket Info: Bind failed on TCP port 1433
If so then some other service grabbed port 1433 before SQL
Server did. From the command prompt, you can use
netstat -an
to find what is using this port.
What exactly was in the log from the DBCC command? Try
executing the DBCC statement from Query Analyzer.
You can restore a backup of the master database if needed.
There is also a utility to rebuild the master database
called rebuildm. But it rebuilds a master database and not
your master database that had logins, servers, etc. For that
you need to restore from your backup.
You can find more information on the rebuildm utility in
books online.
-Sue
On Tue, 7 Sep 2004 17:28:27 -0700, "mmazick"
<anonymous@discussions.microsoft.com> wrote:
>I am running SQL 2000 sp3. I am getting an error in the
>log files that states the SQL server "can not bind to
>TCP: port 1433"
>
>I can not find much info on this other than what is in
>the log files. It appears that the server errored last on
>an integrity check of the SQL master db.
>
>Is there a recovery utility available that will recover
>or rebuild the master database?
>
>Thanks for the help....
- Next message: Tillman Erb: "Re: xp_fileexist to SAMBA-mounted drive"
- Previous message: mmazick: "SQL 2000 server TCP bind problem"
- In reply to: mmazick: "SQL 2000 server TCP bind problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
