MSDE - 17207, udopen: Operating system error 32(error not found) during the creation/opening of physical

Question

MSDE - 17207, udopen: Operating system error 32(error not found) during the creation/opening of physical

SSC Veteran

Points: 287

May 25, 2004 at 10:06 am

Hi there,
I'm hoping somebody here can help with this problem.
In the Application Event Viewer we're seeing a problem. The error message is below:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 17207, udopen: Operating system error 32(error not found) during the creation/opening of physical device C:\Program Files\Microsoft SQL Server\MSSQL\Data\Demodb.mdf.
Its promptly followed by this error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 17204, FCB:pen failed: Could not open device C:\Program Files\Microsoft SQL Server\MSSQL\Data\Demodb.mdf for virtual device number (VDN) 1.
In both cases the "local computer may not have the necessary registry information" part is okay, its the rest of the error that i cant work out..
The machine is running MSDE as its SQL Server and has two DBs:
DB on D: which is 148,628kb
DB on C: which is 237,568kb
I'm pretty stuck on this one, so if anybody knows what's causing this problem, and more importantly how I can go about fixing it, it'd be most appreciated - I'm no SQL Guru and haven't been able to find a huge amount on knowledgebase searches or google searches!
Thanks in anticipation.
Steve S
stevesdmREMOVETHIS@hotmail.com

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply

Danger Mouse SSC Veteran Points: 287 More actions · Answer 1

Sorry guys, I cant work out why the text box is made so big from my text! I dont do HTML either! heh.

Maybe a Moderator could fix it?

Danger Mouse SSC Veteran Points: 287 More actions · Answer 2

I dont know if this would help anyone in helping me but the SQL error log shows the following:

2004-05-26 12:36:28.43 spid7 Starting up database 'Demodb'.

2004-05-26 12:36:53.69 spid52 Starting up database 'Demodb'.

2004-05-26 12:37:52.49 spid52 Starting up database 'Demodb'.

2004-05-26 12:38:01.08 spid52 Starting up database 'Demodb'.

2004-05-26 12:38:53.72 spid52 Starting up database 'Demodb'.

2004-05-26 12:38:53.72 spid52 udopen: Operating system error 32(error not found) during the creation/opening of physical device C:\Program Files\Microsoft SQL Server\MSSQL\Data\Demodbv.mdf.

2004-05-26 12:38:53.74 spid52 FCB:pen failed: Could not open device C:\Program Files\Microsoft SQL Server\MSSQL\Data\Demodb.mdf for virtual device number (VDN) 1.

2004-05-26 13:23:09.55 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.

The last line is MSDE being manually restarted, which resolves the problems for a day or two upon which msde then starts causing problems again.

Jeremy Bivona Grasshopper Points: 11 More actions · Answer 3

Did anyone help you with this? I am having the same problem...

clinton herring-156619 Valued Member Points: 51 More actions · Answer 4

I had the same problem and found that operating system error 32 is caused because the file you are trying to write to is in use. My problem was because I was doing a file backup that was using the file while sql was trying to write to it. The problem may be that you have some files in common with the two databases that are trying to have exclusive access to them or something else on your computer may be accessing the file at the same time.

DB Diva Mr or Mrs. 500 Points: 516 More actions · Answer 5

Hi There,

I got the exact problem. You may have a SQL Server job running at the same time there is an operating system back up running. Try changing the time that your job runs, so that it doesn't run at the same time the operating system is doing it's backup.

I hope this helps.

Jeanette

Sushil Kumar Valued Member Points: 61 More actions · Answer 6

Hi everyone,

I am having same problem. I did check if there is operating system backup job running when the job failed, no there isn't any other backup accessing target folders. The maintenance plan is backing up 2 databases, only one fail everytime the job is run.

Saladyn SSC Journeyman Points: 91 More actions · Answer 7

I had the same problem. Does anyone solve the problem????

Please write to me Saladyn_gda@mail.ru or ISQ 193642067

Thank you

P.S. Sorry for my bad English

Saladyn SSC Journeyman Points: 91 More actions · Answer 8

today is 27/03/2007. 23/03/2007 we instal in our network Secondary Domain controller. and first error was 25/03/2007 can this cause the problem?

Saladyn SSC Journeyman Points: 91 More actions · Answer 9

today is 27/03/2007. 23/03/2007 we instal in our network Secondary Domain controller. and first error was 25/03/2007 can this cause the problem?

kike_sniffonyourpantiesnow Grasshopper Points: 22 More actions · Answer 10

I had this message, and I think that could be similar...

BackupDiskFile::CreateMedia: Backup device 'M:\Respaldo Solomon\NOELAPP backup.BAK' failed to create. Operating system error 32(error not found).

So...Does anyone help me!!!???

Kun Rdgz

cranmer.mark SSChasing Mays Points: 601 More actions · Answer 11

I just came across this error and found that, in my case, it was caused when restoring the backup from one instance onto another, without altering the 'save database as' file path to a location suitable to the second instance.

mark

ramprabhakar.n Old Hand Points: 314 More actions · Answer 12

Detach and Attach the database helps to solve the problem.