SQL Server Performance Forum – Threads Archive
BackupFileDesc::VerifyCreatibility errorI found a following error in SQL Server Error Log: Starting up database ‘foo’.
Bypassing recovery for database ‘foo’ because it is marked IN LOAD.
Starting up database ‘foo’.
BackupFileDesc::VerifyCreatibility: Operating system error 32 (error not found) during the creation/opening of physical device F:LOGSfoo_Log.LDF. Can anybody explain to me what happens? — Rediscover the web
Error 32 is:
The process cannot access the file because it is being used by another process. Some other process like antivirus or external backup software is accessing F:LOGSfoo_Log.LDF before SQL can access it.
Operating system error 32 is caused..Because the file you are trying to write to is in use. Example, one process is trying for exclusive access on file and other process may be accessing the file at the same time. Deepak Kumar –An eye for an eye and everyone shall be blind
Download processexp and find out what’s locking the file. It’s a free download that every DBA should have anyway. [<img src=’/community/emoticons/emotion-1.gif’ alt=’‘ />]<br /><br /<a target="_blank" href=http://www.sysinternals.com/ntw2k/freeware/procexp.shtml>http://www.sysinternals.com/ntw2k/freeware/procexp.shtml</a><br /><br />MeanOldDBA<br />[email protected]<br /><br />When life gives you a lemon, fire the DBA.
I know what caused the problem – somebody tried to restore a database, while a user was connected to it. — Rediscover the web