January 24, 2012 at 11:20 pm
Website was running good up to yesterday. Went to call it up on the internet and received the following message instead of default home page.
- - - - - -
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
/include/inc_data.asp, line 125
- - - - - -
Logged in remotely to server then opened up Services and noticed MSQLSERVER, Status is Starting, but doesn't Start. There are no error messages in Event Viewer referring to SQL Server not starting. When clicking on MSQLSERVER in Services to start or stop SQL Server the buttons are grayed out.
Running Windows 2000 Server Enterprise Manager Version (service pack 4)
Would like to ask for some help on what caused this and what it takes to resolve.
January 24, 2012 at 11:40 pm
Please post the error log information of the server.
You can find the error log from the following folder.
C:\Program Files\Microsoft SQL Server\MSSQL10_50\MSSQL\Log this is applicable if you server version is 2005 or higher.
if you are using sql 2000 the folder can be found in
c:\Program Files\Microsoft SQL Server\Mssql\Log
-- Babu
January 24, 2012 at 11:47 pm
this might be like services are in middle of restart. check application event log if you can see any error message.
January 24, 2012 at 11:50 pm
Using MS SQL 2000
c:\Program Files\Microsoft SQL Server [when I get to here, there no Mssql\Log]
January 24, 2012 at 11:54 pm
Go to the local services. Double click the mssql services. In the general tab will tell you where is the MSSQL program files are installed. Follow that and get the errorlog file from there.
--- Babu
January 24, 2012 at 11:55 pm
umasingh (1/24/2012)
this might be like services are in middle of restart. check application event log if you can see any error message.
Application event log 2 and half hours ago logged this SQL Server is starting at priority class 'normal'
January 25, 2012 at 12:03 am
baabhu (1/24/2012)
Go to the local services. Double click the mssql services. In the general tab will tell you where is the MSSQL program files are installed. Follow that and get the errorlog file from there.--- Babu
Server Process ID is 752.
Logging SQL Server messages in file 'f:\sqldata\MSSQL\log\ERRORLOG'.
SQL Server is starting at priority class 'normal'(1 CPU detected).
SQL Server configured for thread mode processing.
Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
Attempting to initialize Distributed Transaction Coordinator.
SQL Server terminating because of system shutdown.
--John
January 25, 2012 at 12:11 am
I found an article describing your symptons.
Can you try those options.
http://social.msdn.microsoft.com/Forums/en/sqltools/thread/04ab5152-b99d-41f7-a181-417dcea84275
Please update the forum if that has worked for you.
Happy troubleshooting.
--- Babu
January 25, 2012 at 12:28 am
baabhu (1/25/2012)
I found an article describing your symptons.Can you try those options.
http://social.msdn.microsoft.com/Forums/en/sqltools/thread/04ab5152-b99d-41f7-a181-417dcea84275
Please update the forum if that has worked for you.
Happy troubleshooting.
--- Babu
Nope ..this is not the answer. I'm unable to control start/stop on MSSQLSERVER then are grayed out not allowing me to select.
January 25, 2012 at 11:56 am
Noticed the hard drive was way to full, cleared out lots of aged backup files to have plenty of disk space. That made things work better, but even after doing this and sleeping, when I awoke MSSQLSERVER in Services still never started.
Any suggestions?
January 26, 2012 at 1:04 am
***SOLVED*** (kinda)
Went to Start > Run > typed in ‘cmd’ > typed in command window ‘net stop mssqlserver’.
Services was already open so, I click refresh and noticed the MSSQLSERVER status changed from ‘starting’ to being blank. Right clicked on MSSQLSERVER > clicked start and SQL Server started.
Then went to my internet browser, called up website and it loaded right up.
But .. noticed that when I did a remote restart MSSQLSERVER was again hung in the Status of Stating. So nothing had really been solved. Just a little closer to the problem and found a way to work around it for now. The problem is that MSSQLSERVER will not start automatically in services anymore right now. I wonder why?
January 26, 2012 at 4:02 pm
While doing some testing on my laptop, I inadvertently triggered a known bug in SQL Server Configuration Manager where if one of the SQL Server services is disabled it cannot be re-enabled (to Manual or Automatic start). This means the service cannot be restarted. If that service is SQL Server itself, the server is down.
This bug was supposed to be fixed for SQL Server 2008 but it was not. The fix is to use the Windows Services Manager to set the status of the disabled service from Disabled to Automatic. Then, use the SQL Server Configuration Manager to start the service.
http://connect.microsoft.com/SQLServer/feedback/details/386929/sql-server-configuration-manager-cannot-change-the-start-mode-for-a-service-that-is-disabled# - click on the “Workarounds(s) view in the upper right corner of the web page.
I don't know if the problem I had is the one you have but I wanted to offer this information just in case it is similar.
LC
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply