March 7, 2003 at 1:40 pm
running Sql server 7 on NT4 and just recently an error condition surfaced which I cannot remedy. The error log states:
operating system error 10049
Any ideas what is causing this?
March 7, 2003 at 2:23 pm
Is there any more to this message? If not then I am thinking possible an network stack issue as 10049 in Win32 error codes is for
quote:
WSAEADDRNOTAVAIL(10049)
Cannot assign requested address.
The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (for example, address or port 0).
March 7, 2003 at 2:34 pm
Error: 17826, Severity: 18, State: 1
Could not set up ListenOn connection '1433'..
Operating system error 10049
quote:
Is there any more to this message? If not then I am thinking possible an network stack issue as 10049 in Win32 error codes is forquote:
WSAEADDRNOTAVAIL(10049)
Cannot assign requested address.
The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (for example, address or port 0).
March 7, 2003 at 2:55 pm
Yep sounds like something has already opened Port 1433 on the server. Do you have multiple instances of SQL installed. There is a way to see
open a command prompt and type
netstat -a -o
find 1433 and the number to the far right will be the process id.
open task manager and find the process id (PID) that matches.
March 7, 2003 at 3:12 pm
Both netstat and running a port scanner show 1433 not in use. I set sql server to use a different port and the same error condition persists. Grasping at straws, I re-applied the service pack and the issue persists.
quote:
Yep sounds like something has already opened Port 1433 on the server. Do you have multiple instances of SQL installed. There is a way to seeopen a command prompt and type
netstat -a -o
find 1433 and the number to the far right will be the process id.
open task manager and find the process id (PID) that matches.
March 7, 2003 at 6:11 pm
Did you make any changes to the server recently. Account permission for the account SQL is running under if not System Account, or maybe IP address change something unusual?
March 10, 2003 at 8:46 am
no changes were made to the server. IP address remains the same and, to my knowledge, the permissions remain the same for the account sql starts under. I noticed this problem in the afternoon of 2-28 after having rebooted the server earlier that day. I had thought the system had been comprimised, and/or perhaps a trojan was preventing the use of tcp/ip properly, but the port scans show nothing using '1433' and the problem follows regardless which port is set for use so that led me to believe that maybe something was corrupt with sql server itself with respect to the odbc and/or net-libraries - so, grasping at straws, I figured I'd re-apply the service pack which is currently installed and hope for the better, but no go. I really appreciate the help.
quote:
Did you make any changes to the server recently. Account permission for the account SQL is running under if not System Account, or maybe IP address change something unusual?
March 13, 2003 at 7:50 am
I don't know if this will help, but in the Server Network Utility, you can see the driver that is used for TCP/IP. Maybe try replacing it with a version that IS working on another SQL server (if you have another) or download a new version (after renaming current one in case you need to go back).
Also, any messages in the OS event logs...
March 13, 2003 at 11:19 am
Yeah, I tried that and problem persist. NT's event viewer shows nothing which would indicate a problem on its end.
quote:
I don't know if this will help, but in the Server Network Utility, you can see the driver that is used for TCP/IP. Maybe try replacing it with a version that IS working on another SQL server (if you have another) or download a new version (after renaming current one in case you need to go back).Also, any messages in the OS event logs...
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply