April 7, 2008 at 9:05 am
SQL server 2000 build 2187 (i386) (default instance)
32bit Windows 2003 Sp2 (intel)
This morning, during some routine work, found that I could not connect to or query the master database. I checked to see if the agent jobs were still running and sure enough they were running fine. I go through the Event logs for App's and System and nothing out of the ordinary nor in the SQL log file off the disk.
So I stop the service of the instance and then try to restart it and it errors out:
17113 :
initconfig: Error 32(The process cannot access the file because it is being used by another process.) opening 'f:\MSSQL\data\master.mdf' for configuration information.
Funny since I had stopped this instance so the file shouldn't be locked. I double check the antivirus and the disk defrag software, nope they aren't locking the file but to be sure I stop all their related services, still the same error on attempting to start SQL.
I had task manager open prior to all of this and reviewed all processes and behold SQL Server is still running in memory even though the service control says it's stopped. I close and reopen both task manager and the service control window. The service is still showing a stopped state and the task manager shows the SQL server executable in memory.
I tried to end the process, nothing. Still shows in memory. Still can't start the service.
After a reboot (which took a very long time just for it to shutdown, I'm guessing to clear SQL server out of memory) the server is back up and working as normal.
So my question is:
Has anyone seen this issue before? SQL server becoming unresponsive and then when you try to stop the service the OS loses control of it and are unable to restart it?
Thanks,
-Z
April 7, 2008 at 3:48 pm
I did come across it. You may try to kill the process in the Task Manager.
I guess that it is because of memory leak in MS.
April 10, 2008 at 11:05 am
Anyone else witness stopping a service and then not being able to restart it because it never truly stopped?
April 10, 2008 at 11:25 am
Check this out - a hotfix for sp4. Seems to be what you're experiencing.
http://support.microsoft.com/kb/924664
-- You can't be late until you show up.
April 10, 2008 at 11:42 am
Thats the best lead yet, thanks!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply