Can't load database server because the default database is marked as suspect.
I start the SQL server and see it in the taskmanager.
In Enterprise Manager
I try to connect to the SQL server but receive a Connection Failed, check SQL Server egistration Properties. In SQL analyzer I cannot conect to the database.
I stopped the servce and started SQLSERVR from command prompt and noticed
spid11 Bypassing recovery for database "ListManager' because it is marked SUSPECT.
thanks
DC
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I tried to install the hotfix but I get a
The product does not have a prerequisite update installed. The installation is dependent on the prerequisite update and cannot be installed. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.
Could you make sure that all files composing the database are OK?
If they are, try to remove a suspect bit:
update sysdatabases set status = status & ~256
where name = 'the_suspected_database'
You need to enable writing to system tables.
If the database is set back to suspected, there must be some reason (like log file damaged).
Do you see any errors in this database in log files?
Are you able to restore the database from a backup?
You can try to access the database in an emergency mode:
update sysdatabases set status = status | -32768
where name = 'the_suspected_database'
and restart SQL Server
Progress:
So my work around for getting into the SQL server is starting it with sqlservr -m in command prompt
Then open another command prompt and try to update the database, but I got an error message:
C:\>osql -E -d master
1> update sysdatabases set status = status & ~256 | -32768
2> where name = "ListManager"
3> go
Msg 259, Level 16, State 2, Server S-MSSQL2K, Line 1
Ad hoc updates to system catalogs are not enabled. The system administrator
must reconfigure SQL Server to allow this.
1> sp_configure 'allow updates', 1
2> go
Ctrl C in the other window to stop sqlservr -m
Then start the service with the SQL Server Service Manager
Ran again:
C:\>osql -E -d master
1> update sysdatabases set status = status & ~256 | -32768
2> where name = "ListManager"
3> go
(1 row affected)
1> exit
Now start SQL Server Enterprise Manager
-> microsoft SQL Servers
-> SQL Server Group
-> MSSQL (Windows NT) (THIS IS WHERE IT WOULD STOP BEFORE AND NOT CONNECT TO DB)
->Databases
LM (DBO Use only Read-Only\OFFLINE)
master
.......
.......
.......
The General Information for database LM the Transaction log space is 0mb.
The physial size of the database is close to 7 gig.
In the errlog:
Bypassing recovery for database 'LM' because it is marked BYPASS.
The problem now is the database is in DBO use only \read online \ offline \ emergency mode.
The part that worked:
1> sp_configure 'allow updates', 1
2> go
C:\>osql -E -d master
1> update sysdatabases set status = status & ~256 | -32768
2> where name = "ListManager"
3> go
(1 row affected)
1> exit
1> sp_configure 'allow updates', 0
2> go
After running these commands the staus was changed to BYPASS or emergency mode and I could access the tables in read only.
I could not fix the readonly so I created another database and strated copying over the data.
thanks
DC
Business Accounts
Answer for Membership
by: NetExpert-WarszawaPosted on 2009-09-05 at 09:42:47ID: 25266849
In case of 2000 version read http://support.microsoft.c