|
-
Port 1433 is already in use...........
Ok,
The Scenario is as follows:
24/7 Production Call Centre server running NT4.0 and SQL 6.5 with all the latest service packs.
SQL mail fails(with dull regularity) and the SQL server services stop.
When the SQL server Services are restarted an error message appears stating that Port 1433 is in use after which nobody can connect via TCP/IP. Obviously the port believes the previous SQL session is still running, and won't release the port to the "New Application requesting it".
On a unix system you can force a port reset so you don't need to shutdown and restart the box. Can you do this from either SQL or NT?
Any solutions would be greatly appreciated the DBA's are 100 Miles from the Servers, so restarts are reliant on other people!
-
Port 1433 is already in use........... (reply)
Should restart sql service at least.
------------
Rob Simmons at 6/7/00 11:18:25 AM
Ok,
The Scenario is as follows:
24/7 Production Call Centre server running NT4.0 and SQL 6.5 with all the latest service packs.
SQL mail fails(with dull regularity) and the SQL server services stop.
When the SQL server Services are restarted an error message appears stating that Port 1433 is in use after which nobody can connect via TCP/IP. Obviously the port believes the previous SQL session is still running, and won't release the port to the "New Application requesting it".
On a unix system you can force a port reset so you don't need to shutdown and restart the box. Can you do this from either SQL or NT?
Any solutions would be greatly appreciated the DBA's are 100 Miles from the Servers, so restarts are reliant on other people!
-
Port 1433 is already in use........... (reply)
To Clarify the problem, I can Start all SQL Server Services.
If we were using named pipes there would be no problem and we could ignore this problem.
The issue is connection over TCP/IP which for this particular Call Centre, is the only protocol that will work. Because the Server will not release port 1433 following the failure of SQL Server, clients using TCP/IP cannot connect.
We can't change the protocol so we have to reset the port.
Any Ideas gratefully recieved:-)
------------
Ray Miao at 6/7/00 3:06:23 PM
Should restart sql service at least.
------------
Rob Simmons at 6/7/00 11:18:25 AM
Ok,
The Scenario is as follows:
24/7 Production Call Centre server running NT4.0 and SQL 6.5 with all the latest service packs.
SQL mail fails(with dull regularity) and the SQL server services stop.
When the SQL server Services are restarted an error message appears stating that Port 1433 is in use after which nobody can connect via TCP/IP. Obviously the port believes the previous SQL session is still running, and won't release the port to the "New Application requesting it".
On a unix system you can force a port reset so you don't need to shutdown and restart the box. Can you do this from either SQL or NT?
Any solutions would be greatly appreciated the DBA's are 100 Miles from the Servers, so restarts are reliant on other people!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Reply With Quote