August 15, 2010 at 10:20 pm
When we are taking ntbackup from OS level I am observing this in application log.
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release mutex not owned by caller.
. Process=236. Thread=5824. Client. Instance=. VD=.
When i had gone through Microsoft site i found that there is on hotfix to avoid.
Is there any impact due to this error.Is it sql server error or application error.Kindly let me know.
Before this error occuring i am geeting information in log is like...............
10:49:03 AM I/O is frozen on database distribution. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
10:49:03 AM I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
10:49:04 AM I/O was resumed on database distribution. No user action is required.
10:49:04 AM I/O was resumed on database msdb. No user action is required.
10:49:04 AM Database backed up. Database: master, creation date(time): 2010/08/08(15:33:06), pages dumped: 1, first LSN: 374:16:50, last LSN: 374:96:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{A8742C98-3563-47D8-80D5-1E63F2818B3A}1'}). This is an informational message only. No user action is required.
10:49:04 AM SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release mutex not owned by caller.
. Process=4124. Thread=312. Client. Instance=SQLSERVERVIEW. VD=.
August 16, 2010 at 11:19 pm
This error may affect other applications using SQL VDI. You may use Process Explorer to find out which process is using the mutex.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
August 18, 2010 at 10:22 pm
i had the same error. After installing SP3, everything goes normal
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply