June 24, 2002 at 5:05 am
When I try to start SQL Server as a service, or when opening Enterprise Manager it fails. The Windows Application Event Log gets an entry for Error 5180, then 5172, which sound like a database is corrupt. I can't find the SQL error log (supposedly in the (sql7\logs directory) and I can't start EM.
Questions: How does one manually restore a backup (like copy and rename in Explorer) when one can't get into EM?
Can you start EM another way without loading databases? Then I could perhaps find the logs and find out for sure which database is bad.
These sure sound like obvious questions to me, but I've scoured BOL to no avail.
Thanks.
Student of SQL and Golf, Master of Neither
Student of SQL and Golf, Master of Neither
June 24, 2002 at 9:40 am
Can you connect via isql? Or Query Analyzer?
EM uses more than one connection and if you are single user mode, you cannot use this.
Steve Jones
June 24, 2002 at 11:59 am
During repeated attempts to get SQL started I found that 'opends60.dll' and a couple of other DLL files were being reported as 'file or directory is corrupt'. I tried to copy and paste from another SQL server, Windows would not cooperate, same message. I decided that my SQL install had gone bad.
Ran chkdsk, found a ton of bad files in the SQL directory and one other.
Did a full uninstall, reinstall of SQL 7 and then SP3. Found how to start in single user mode (dos prompt sqlservr -m). WAS ABLE to then go into EM in single user mode and restore the Master DB. Was not allowed to restore model and msdb because I was in single user mode (This makes no sense to me!) Restarted NT and all my databases showed up like magic. Still need to restore msdb???? to get my maintenance plans back.
Student of SQL and Golf, Master of Neither
Student of SQL and Golf, Master of Neither
June 24, 2002 at 1:28 pm
Thanks for the followup. I'd run a full checkdisk( requires a reboot) and make sure you have no low level issues.
Steve Jones
June 24, 2002 at 3:34 pm
Lot's of laughs on that one. I had started the full scan as part of the original troubleshooting efforts. After 40 minutes it reported 2% done on our 120 Gig raid array. I decided a 25 hour downtime wasn't going to cut it!
New thought - What are you using for disk monitoring / scanning/ utility software. Norton Utilities for NT?
Student of SQL and Golf, Master of Neither
Student of SQL and Golf, Master of Neither
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply