January 8, 2003 at 9:53 am
Hi everyone , please help!!!
Since yesterday, our SQL started to thowing out this error:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/8/2003
Time: 09:31:05
User: N/A
Computer: SQLserver
Description:
17113 :
initconfig: Error 32(The process cannot access the file because it is being
used by another process.) opening 'e:\MSSQL\data\master.mdf' for
configuration information.
Data:
0000: d9 42 00 00 10 00 00 00 ÙB......
0008: 0c 00 00 00 4d 00 49 00 ....M.I.
0010: 54 00 53 00 45 00 52 00 T.S.E.R.
0018: 56 00 45 00 52 00 30 00 V.E.R.0.
0020: 36 00 00 00 00 00 00 00 6.......
When this happened, none of my applications can access the SQL server and
lock up the users that are trying to run the app. I searched Technet and
several news groups on the net, and they all pointed me to the issues with
User Connections settings. However, our server uses the default settings
which allows unlimited connections. I' lost where I should start to fix
this. Has anyone run into this error, and how have you fixed it?
Any help will be greatly appreciated.
Daniel.
January 8, 2003 at 10:17 am
First have you tried restarting the service and the server to see if the issue goes away? In addition are there any other processes that could be hung such as a backup running against master currently?
January 8, 2003 at 2:27 pm
Thanks lot, Antares686. Yes after I restarted MSSQLServer and SQLAgent, the lock went away. I have backup job running nightly to backup system databases, including Master. But I've running the job forever and never had such problem. The only change that we made recently is upgrade from SQL7 to SQL2k, but we have been running our app on it without any issues till yesterday.
Thanks.
January 8, 2003 at 2:45 pm
It may be a fluke that just occurred but check in Event Viewer and SQL Server Logs to see if any other specific event occurred around the time the problem started. Also, check job histories to see if any may have reported an issue or ran extremely long during the time of the condition.
October 9, 2012 at 7:12 pm
This happened to me running SQL2000 under VMWare, running a backup with RedGate HyperBac 5.7.0.155 as the transparent compression. The backup had hung (which has happened twice on this, our only virtual SQL Server) and when I restarted MSSQLServer, Hyperbac still had a lock on master.mdf. I had to kill Hyperbac thru taskmgr (its UI didn't kill it) and then was able to restart MSSQL.
Gary
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply