May 23, 2007 at 3:59 pm
I have an SQL 2005 Standard Server that has been running beautifully for over a year now. All of a sudden in the middle of the night the server service abruptly stopped. There are both application errors and system errors.
We have tried everything we can think of. Disabling named pipes, enabling named pipes, trying to start the Active Directory Integration service (it won't start), repairing Windows 2003 Server OS, repairing SQL 2005 Server (it won't change anything because it thinks the server is running fine).
In the logs it shows that it starts and then immediately stops. No one was doing anything in this server when it decided to stop dead in its tracks. Can I just move the databases "out of the way" and uninstall and re-install SQL server?
The error we get when we attempt to start the server is:
An error has occurred while establishing a connection to the server. WHen connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
We have tried the solutions suggested that we could find. We found that accomplishing some of these suggestions requires starting and stopping the server. We can't do that. This is the problem. At this point we are a bit baffled.
I can connect using the analysis section of SQL Manager Studio. But under databases it does not show any of the databases that are in there. MSSQL Agent won't start either, though I suspect it won't because it is dependent on MSSQL Server service being started.
I'll take any suggestions I can get.
Thanks! Jim K.
May 23, 2007 at 4:34 pm
May 23, 2007 at 7:48 pm
Unfortunately your solution didn't work. We had been doing the fix where you make sure you are set up for remote connections, disable named pipes, re-enable named pipes, check TCP/IP settings, etc.
We had not looked to see if the port numbers were correct. So we did that but the problem was still not solved. It simply won't start the server service and let us connect.
At this point I am copying all databases (7 of them) to a safe folder. I may have to do a clean re-install of SQL 2005. Its the only solution I haven't tried yet.
Thanks for you help and suggestions. They are greatly appreciated!
Regards, Jim K.
May 24, 2007 at 6:50 am
Is there any errors in the Windows logs? Such as hardware issues during start up? Tried an alternate network card?
May 24, 2007 at 12:47 pm
There were not any errors. In fact I installed another instance and it worked just fine on the machine, but because it named the instance <sql_server_name\sql_server_name> my software on other machines who send data to the SQL server did not like that naming convention and wouldn't connect.
I have no more time to try to get it to work, and I have backed up the databases. So I am using a new server I had yet to utilize, and creating a brand new seperate SQL server.
Then I can get our services back on line and then I have time to fool around with the "old" SQL server. I will probably just wipe it completely and install the OS and then intsll SQL new. The main thing is we are 24/7 to our clients and so I have to go this route in the name of expediency.
If you or anyone has ony more ideas as to what the problem was, though, I am all ears. Its just a very baffling case. One minute running flawlessly and the next all connections to it are gone and I can't even connect to the SQL server locally. Strange.
Thanks again for all the help and advice!
Sincerely, Jim K.
May 24, 2007 at 12:52 pm
Have you attempted to connect to MSSQL in single user mode? i.e. sqlservr -smssqlserver -c -f -m -T3608
Tommy
Follow @sqlscribeViewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply