December 15, 2011 at 9:00 am
This morning we had an issue where new connections couldn't be established to our sql server instances. I had a connection opened from yesterday and was able to view the databases just fine; it wasn't until I closed my connection, that I was able to duplicate the error. I am an administrator on the machine and of sql server.
We had a 2005 instance (SP3) and a 2008 (SP2) instance running on one active node of a two node cluster. We had to reboot to fix the issue.
All sql services were running, including browser. It is a Windows 2003 R2 Enterprise x64 SP2 server.
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)"
There is absolutely nothing in the event viewer or sql server logs that would indicate a problem. Please help!
December 15, 2011 at 9:05 am
Check with the IT department if they modified the firewall settings.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 15, 2011 at 9:11 am
Adi Cohn-120898 (12/15/2011)
Check with the IT department if they modified the firewall settings.Adi
OR help yourself 😉
Example:
portqry -n myserver -p udp -e 389
New features and functionality in PortQry version 2.0
December 15, 2011 at 9:14 am
Yup...I see this error message: "Length specified in network packet payload did not match number of bytes read; the connection has been closed. " which can correspond to something messing with the browser service.
December 15, 2011 at 9:20 am
DBAgal (12/15/2011)
Yup...I see this error message: "Length specified in network packet payload did not match number of bytes read; the connection has been closed. " which can correspond to something messing with the browser service.
Now you know where to attack 😀
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply