Re: SQLVDI Error
- From: Duncan McC <hard@xxxxxxx>
- Date: Sun, 6 Apr 2008 13:22:40 +1200
One reason I steer clear of hotfixes (well ones that are not critically
important) is that upon SP's coming out, you may have to remove any
hotfixes that have been applied.
And this particular one, is certainly in that category for me - the
event logs and server reports are of no consequence, in the light of the
knowledge that it causes no harm.
--
Duncan
In article <eQO5mHrlIHA.464@xxxxxxxxxxxxxxxxxxxx>,
mitchgoodwin@xxxxxxxxxxx says...
Thanks to you both, I kind of stumbled across that hot fix soon after.
posting. I see that MS is indicating it is best to wait until the fix comes
out in a Service Pack. Any thoughts on that and is it best to wait, or go
ahead and get the hot fix? Any idea how long until the next service pack?
At least it sounds like, although annoying, it is not really causing any
harm.
"Paul Shapiro" <paul@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OivVjfZlIHA.3876@xxxxxxxxxxxxxxxxxxxxxxx
You might also want to verify that you have the correct hotfix. The online
hotfix request system recently sent me links to two incorrect hotfixes.
The fix for this issue was one of them. I found a copy of the hotfix file
on an older server, and installing that solved the problem. I suggest
calling tech support to get the hotfix. After you install it, verify it
according to the instructions in the KB article.
"Henrik (Hear)" <hear01@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e5e9MgXlIHA.1164@xxxxxxxxxxxxxxxxxxxxxxx
Check this link and fix out.
It can be applied on all applications that uses VDI.
FIX: Error messages and an event may be logged when you use the Virtual
Device Interface in SQL Server 2005 or in SQL Server 2000
http://support.microsoft.com/kb/934396
--
Henrik Arenblad, MCP SBS,
"GoodwinM" <mitchgoodwin@xxxxxxxxxxx> wrote in message
news:eh$x0BXlIHA.2396@xxxxxxxxxxxxxxxxxxxxxxx
Sorry to report that this solution did not change the issue at all.
Any other suggestions?
"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:AA923300-8A88-4106-BE3B-B5F46B90C30C@xxxxxxxxxxxxxxxx
Hi Goodwin,
I believe this update will resolve that error:
http://www.microsoft.com/Downloads/details.aspx?familyid=30A7365B-91C5-4C28-85A5-9AB861168C0E&displaylang=en#QuickInfoContainer
--
Les Connor [SBS MVP]
________________________
Get the SBS BPA here:
http://support.microsoft.com/kb/940439/en-us
"GoodwinM" <mitchgoodwin@xxxxxxxxxxx> wrote in message
news:OVygv7ykIHA.980@xxxxxxxxxxxxxxxxxxxxxxx
SBS 2003 R2 Standard, with SQL Server Express
I am getting the folling event logged about 15 times daily. I think
this is related to backing up as it seems to happen during that time
period and does not occur on days with no backup scheduled.
This one is from WSUS, but they also appear for Sharepoint and
Monitoring as well.
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
ErrorCode=(288)Attempt to release mutex not owned by caller. .
Process=9684. Thread=1328. Client. Instance=WSUS. VD=.
Hopefully someone here will have a solution.
- Follow-Ups:
- Re: SQLVDI Error
- From: Susan Bradley
- Re: SQLVDI Error
- References:
- Re: SQLVDI Error
- From: Les Connor [SBS MVP]
- Re: SQLVDI Error
- From: GoodwinM
- Re: SQLVDI Error
- From: Henrik \(Hear\)
- Re: SQLVDI Error
- From: Paul Shapiro
- Re: SQLVDI Error
- From: GoodwinM
- Re: SQLVDI Error
- Prev by Date: Re: SBS 2003 Standard/Fax Server Issue
- Next by Date: Re: SBS 2003 Standard/Fax Server Issue
- Previous by thread: Re: SQLVDI Error
- Next by thread: Re: SQLVDI Error
- Index(es):
Relevant Pages
|