470,648 Members | 1,607 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,648 developers. It's quick & easy.

'Suspect' DB won't open - OS error 32- Help!

Help! One of my main databases has been marked as suspect - the
initial problem is that my disk had no space. So I moved some files,
made some space, stopped & restarted the service, and now I get this
error in the errorlogs. There can't be anything else using the
database - I restarted the machine to kill everything that might be
touching it, including the client application.

2005-03-30 14:35:21.96 kernel udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device
c:\mssql7\data\<database>.mdf.

2005-03-30 14:35:22.01 kernel FCB::Open failed: Could not open device
c:\mssql7\data\<database>.mdf for virtual device number (VDN) 1.

2005-03-30 14:35:22.03 spid6 Device activation error. The physical
file name 'c:\mssql7\data\<database>.mdf' may be incorrect.

Jul 23 '05 #1
1 5206
(co*********@yahoo.com) writes:
Help! One of my main databases has been marked as suspect - the
initial problem is that my disk had no space. So I moved some files,
made some space, stopped & restarted the service, and now I get this
error in the errorlogs. There can't be anything else using the
database - I restarted the machine to kill everything that might be
touching it, including the client application.

2005-03-30 14:35:21.96 kernel udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device
c:\mssql7\data\<database>.mdf.

2005-03-30 14:35:22.01 kernel FCB::Open failed: Could not open device
c:\mssql7\data\<database>.mdf for virtual device number (VDN) 1.

2005-03-30 14:35:22.03 spid6 Device activation error. The physical
file name 'c:\mssql7\data\<database>.mdf' may be incorrect.


http://www.karaszi.com/SQLServer/inf...suspect_db.asp might give
some ideas.

However, you may find that it's best to restore a clean backup. If you
don't have any clean backup, and that data is dear to you, I would
recommend open a case with Microsoft.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Saiyou Anh | last post: by
4 posts views Thread by Corepaul | last post: by
4 posts views Thread by David Killian Woods | last post: by
1 post views Thread by Alpha | last post: by
reply views Thread by jeff | last post: by
4 posts views Thread by Susan Rice | last post: by
reply views Thread by jrshack | last post: by
1 post views Thread by Korara | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.