The above error message comes up just before SQL Server marks the database as "Suspect" and refuses to open it. Does anyone know what the message means and how to fix it? I think it's a matter of grabbing the backup, but would be nice if it was possible to recover the data.
I've had a look at the kb article but there are no transactions to resolve.
It appears that it means your distributed transaction coordinator failed to start correctly when bringing the SQL Server online.
please refer to this ASP.NET forum post and knowledge base article
Depending on the level of logging, you should be able to take the last known backup and slowly recover the logs using point in time recovery techniques to slowly bring the database up to the point right before failure began.
run checkdb to find out why it's been marked as suspect and see if it can be recovered without any data loss (win)
Halo, just want to know, how do you solve the problem, cause I have the same problem about warning did not see LOP_CKPT_END and feeling stress cause I don't have any backup for the last 5 months and I need the data inside my database to create report that will be used in 2 days more.
I don't have enough time to input the data from the last 5 months.It's just really a huge pile of data and process..
Thanks in advance for the help