Critical Error: Attempt to release mutex not owned by caller

[JoeF]

I keep getting the following error events even after installing the MS Hotfix
offered by Microsoft. What else can I try?

SQLVDI
1 8/11/2007 11:00 PM 3 *
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
ErrorCode=(288)Attempt to release mutex not owned by caller. . Process=1788.
Thread=5740. Client. Instance=SBSMONITORING. VD=.

Thanks.

-JoeF

[Costas]

See the following KB article http://support.microsoft.com/kb/934396 If that
does fixes the problem see the following
http://support.microsoft.com/kb/913648

Hope that helps

Costas

"JoeF" <Jo...@discussions.microsoft.com> wrote in message
news:30DC289D-BE5E-4CF0...@microsoft.com...

[JoeF]

Thanks for the reply.

I applied that hotfix in the past but the same mesage keeps appearing. I
also tried the 2nd link you sent which was a VSS update however; my SP level
was newer than this version, so it did not install.

Any other ideas?

-JoeF

[Costas]

Unfortunately that's the only two solutions I am aware of. There were posts
with readers that solved this particular issue by applying either of these
patches but there were others like yourself that the patched didn't help. If
I come across any other solutions I'll post

Costas

"JoeF" <Jo...@discussions.microsoft.com> wrote in message

news:29F4F7C9-9D79-4B1F...@microsoft.com...

[JoeF]

It happens right when the SBS Backup runs. This is the SQL Server 2005
Workgroup edition that comes with SBS Premium. During installation, they had
me upgrade the Sharepoint Database to the 2005 version for Full-Test
searching. I went through the process w/o error. Here's all the event log
entries that appear at this exact time during backup:

Event Type: Information
Event Source: ESENT
Event Category: ShadowCopy
Event ID: 2001
Date: 8/13/2007
Time: 11:00:44 PM
User: N/A
Computer: SBSERVER1
Description:
wins (2456) Shadow copy 1 freeze started.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------------------------------------
Event Type: Information
Event Source: MSSQL$SHAREPOINT
Event Category: (2)
Event ID: 3197
Date: 8/13/2007
Time: 11:00:44 PM
User: NT AUTHORITY\SYSTEM
Computer: SBSERVER1
Description:
I/O is frozen on database model. No user action is required. However, if I/O
is not resumed promptly, you could cancel the backup.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7d 0c 00 00 0a 00 00 00 }.......
0008: 15 00 00 00 53 00 42 00 ....S.B.
0010: 53 00 45 00 52 00 56 00 S.E.R.V.
0018: 45 00 52 00 31 00 5c 00 E.R.1.\.
0020: 53 00 48 00 41 00 52 00 S.H.A.R.
0028: 45 00 50 00 4f 00 49 00 E.P.O.I.
0030: 4e 00 54 00 00 00 06 00 N.T.....
0038: 00 00 6d 00 6f 00 64 00 ..m.o.d.
0040: 65 00 6c 00 00 00 e.l...
--------------------------------------------------------------------------------------
============================================
***The above message is the same for all the db's...about 7***
============================================
Event Type: Information
Event Source: ESENT
Event Category: ShadowCopy
Event ID: 2003
Date: 8/13/2007
Time: 11:00:46 PM
User: N/A
Computer: SBSERVER1
Description:
wins (2456) Shadow copy 1 freeze stopped.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---------------------------------------------------------------------------------
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 8/13/2007
Time: 11:00:46 PM
User: N/A
Computer: SBSERVER1
Description:

SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
ErrorCode=(288)Attempt to release mutex not owned by caller.

. Process=2256. Thread=3220. Client. Instance=SBSMONITORING. VD=.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------------------------------------------------------------------

[wedor]

I changed the account that logged into the service in question and that
fixed it for me, I used the administrator account instead of the local.

"Costas" <cpstec...@gmail.com> wrote in message
news:eo7I4uc3...@TK2MSFTNGP03.phx.gbl...

[alinkns]

Run a script prior to running the backup to stop MS SQL and the Agent.

--
alinkns
------------------------------------------------------------------------
alinkns's Profile: http://forums.techarena.in/members/alinkns.htm
View this thread: http://forums.techarena.in/small-business-server/799958.htm

http://forums.techarena.in