SQL Server 2000 Stopped working, possible after Backup Exec Backup
Hi there,
Unfortunately a Database server has stopped working. The issue appears to be that the Service will not start. When entering the SQL Management tool it tries to connect to the Server (local) and says:
'A connection could not be established to SERVER1, Â Reason: SQL Server does not exist or Access denied
When attempting to start the service it appears to start but if you refresh it will no longer be started.
Yesterday i was running some backups using backup exec and encountered some issues. It stated in the failed backup that some databases (which have not been used in years) are in restore mode. I ignored this, then last night I decided to restart the server. Since not long after that restart the logs are full (overnight) with error logs about the MSSQL.
Unfortunately i've turned this server off and are cloning it before I commence a reinstall of SQL Server 2000. I'm in a little bit of unchartered territory as i've not reinstalled SQL onto an existing broken install and I also did not set this up in the first place.
Any ideas would be good and I should be able to provide logs soon.
Cheers
Unfortunately a Database server has stopped working. The issue appears to be that the Service will not start. When entering the SQL Management tool it tries to connect to the Server (local) and says:
'A connection could not be established to SERVER1, Â Reason: SQL Server does not exist or Access denied
When attempting to start the service it appears to start but if you refresh it will no longer be started.
Yesterday i was running some backups using backup exec and encountered some issues. It stated in the failed backup that some databases (which have not been used in years) are in restore mode. I ignored this, then last night I decided to restart the server. Since not long after that restart the logs are full (overnight) with error logs about the MSSQL.
Unfortunately i've turned this server off and are cloning it before I commence a reinstall of SQL Server 2000. I'm in a little bit of unchartered territory as i've not reinstalled SQL onto an existing broken install and I also did not set this up in the first place.
Any ideas would be good and I should be able to provide logs soon.
Cheers
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
It doesn't really answer your question..but backup your system databases. It makes life much easier when they do that. ...and yes - the 2nd time it happened to me I wondered why I didn't do it after the first time.
Have you tried restarting the service again?
Try running dbcc checkdb on your database to see if there's anything suspicious happening
Have you tried restarting the service again?
Try running dbcc checkdb on your database to see if there's anything suspicious happening
>> Named Pipes Provider, errorL
Named pipes has been a nightmare since inception. You should have a SQL configuration manager. Turn oof named pipes and then restart all SQL Services.
Named pipes has been a nightmare since inception. You should have a SQL configuration manager. Turn oof named pipes and then restart all SQL Services.
ASKER
Forgot to mention. After a few hours the speed went back to normal gradually.
All good ! :)
All good ! :)
ASKER
Managed to resolve it.
ASKER
I've reattached the databases. However still no go. Sharepoint doesn't work, has the following error: "Cannot connect to the configuration database."
IN the logs, there is repeated error messages every 30 seconds or so. the source is Windows Sharepoint Services 3. And the Error description is:
'Unknown error information from SQL Server is included below.
A connection was successfully established with the server, but then an error occuring during the login process. (provider: Named Pipes Provider, errorL 0 - No process is on the other end of the pipe.)