ErrorCode=(288)Attempt to release mutex not owned by caller

I keep getting Critical application Errors every night right at the start of
the scheduled NTbackup. It happens right when the SBS Backup runs @. 11PM.
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.
I installed the MS Hotfix but the errors still show up.
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
----
It seems to be related to the SBSMONITORING DB's.
Please help. I'm at a loss.
-JoeFWe had a similar problem when backing up databases. Some process had not
released the mutex tables and we ending up restating the server in order to
free it. Hopefully doing this might help you.
If this is not an option download Process Explorer from sysinternals to
see if it can pinpoint the problem. You may be able to free the process
preventing backups,
"JoeF" wrote:
> I keep getting Critical application Errors every night right at the start of
> the scheduled NTbackup. It happens right when the SBS Backup runs @. 11PM.
> 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.
> I installed the MS Hotfix but the errors still show up.
> 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.
> ----
> It seems to be related to the SBSMONITORING DB's.
> Please help. I'm at a loss.
> -JoeF