SQLVDI

Claus

unread,

Nov 27, 2007, 9:29:07 AM11/27/07

to

Has anybody come across a fix for this nasty SQLVDI error? KB934396 doesn't
do the trick. I have 11 boxes that I would love to clean up.

Thanks,

--
Claus

Dave Nickason [SBS MVP]

unread,

Nov 27, 2007, 12:40:29 PM11/27/07

to

Hi Claus.

That patch fixed it on my SBS (SP2, not R2, no SQL installed but using the
default instances for everything including WSUS). It did not fix it on two
member servers - one runs SQL 2005 Workgroup fully patched, and the other
runs SQL 2005 and 2 or 3 MSDE instances, also fully patched. Interestingly,
on the member server that's just running Workgroup, I get the errors for the
first few backups after a restart, and then they go away. Just restarting
SQL isn't enough to start the errors again, though - once they stop, they
only come back after I reboot the server.

The two member servers both run ShadowProtect, one version 2 and one 3.
ShadowProtect support doesn't have much on this, although they're aware of
it. Nothing to really tie it to SP - one of my member servers started doing
it weeks after the other, and one sometimes does it prior to a backup that's
initiated by a maintenance plan in addition to doing it right before the SP
backup.

There seem to be posts all over the place about this error, with no
resolution. I wouldn't mind it going away as it worries me a little about
the backups. I can mount the SP backups and see the databases as I expect,
but I haven't attempted an actual restore to check for issues. The actual
SQL logs don't indicate any problems either.

"Claus" <cjo...@nova-tech.org> wrote in message
news:uWq1iIQM...@TK2MSFTNGP04.phx.gbl...

Leythos

unread,

Nov 27, 2007, 5:24:34 PM11/27/07

to

In article <OtEHbyRM...@TK2MSFTNGP04.phx.gbl>,
gwdi...@NOSPAM.frontiernet.net says...

> Hi Claus.
>
> That patch fixed it on my SBS (SP2, not R2, no SQL installed but using the
> default instances for everything including WSUS). It did not fix it on two
> member servers - one runs SQL 2005 Workgroup fully patched, and the other
> runs SQL 2005 and 2 or 3 MSDE instances, also fully patched. Interestingly,
> on the member server that's just running Workgroup, I get the errors for the
> first few backups after a restart, and then they go away. Just restarting
> SQL isn't enough to start the errors again, though - once they stop, they
> only come back after I reboot the server.

Like the OP, I've been unable to fix it on several servers also.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam9...@rrohio.com (remove 999 for proper email address)

Claus

unread,

Nov 27, 2007, 5:23:52 PM11/27/07

to

Dave,

Thanks for the update. Yes, it seems to be very random. I have some installs
that don't show this error at all and other boxes with the same setup and
software keep between 20 and 40 errors.

I did do a test restore on one of them and didn't run into any issues. But I
still would like to get rid of those errors. One should think by now MS
would have come up with a fix.

--
Claus
"Dave Nickason [SBS MVP]" <gwdi...@NOSPAM.frontiernet.net> wrote in message
news:OtEHbyRM...@TK2MSFTNGP04.phx.gbl...

Claus

unread,

Nov 27, 2007, 6:25:27 PM11/27/07

to

Leythos,

Join the club. I wonder if some of our MVPs could express to MS that this
needs to be fixed.

--
Claus
"Leythos" <vo...@nowhere.lan> wrote in message
news:MPG.21b663292...@Adfree.usenet.com...

Leythos

unread,

Nov 27, 2007, 6:50:18 PM11/27/07

to

In article <uYQsN0UM...@TK2MSFTNGP02.phx.gbl>, cjo...@nova-tech.org
says...

> Join the club. I wonder if some of our MVPs could express to MS that this
> needs to be fixed.

I've read hundreds of articles and not seen one thing that has helped
me. The server in question is not SBS, but it was part of a Swing
Migration that went perfectly. I only mention this because the server is
not SBS, but the entire network was based around SBS.

What I've determined is that we didn't get this problem until we
installed SQL 2005 Workgroup, removed it, then installed SharePoint
(free) which has the SQL 2005 version in it.

I'm tempted to remove SharePoint and all instances of SQL 2005, reboot
the server, and see if it goes away.

I should also point out that the problem only happens when starting a
backup, not any other time.

Claus

unread,

Nov 27, 2007, 6:59:14 PM11/27/07

to

Don't go through the hassle of uninstalling SharePoint and installing
2005WG. You will most likely end up with the same problem. All my boxes are
SBS2003Premium with 2005WG and they have the error as well.

And yes, it only happens when the backup starts.

--
Claus
"Leythos" <vo...@nowhere.lan> wrote in message

news:MPG.21b67741f...@Adfree.usenet.com...

Dave Nickason [SBS MVP]

unread,

Nov 27, 2007, 7:03:33 PM11/27/07

to

My experience is the same with the backup - messages only appear when
backups start - but not with the Workgroup thing. As I said, I've seen this
on 3 servers here, and one (my SBS) doesn't even run any version of SQL 2005
other than the embedded instance that runs WSUS.

I'll shoot an e-mail to someone about this, but I think that under the
circumstances the best they'll be able to do is pass it along to the SQL
team. I'll keep you posted if I hear anything.

"Leythos" <vo...@nowhere.lan> wrote in message

news:MPG.21b67741f...@Adfree.usenet.com...

Dave Nickason [SBS MVP]

unread,

Nov 27, 2007, 7:16:36 PM11/27/07

to

I just noticed something. On the member servers where I'm still getting
this error, it's as posted in below. On the SBS, where the patch fixed it,
I had one of the error messages in the KB that Claus mentioned. They're
both SQLVDI error 1, which is why I didn't notice that the text of the error
message is different. The KB apparently fixes the errors it references, but
not this one.

Can you guys look at that to see if you're getting the error in the KB or
the one pasted in below? I'll wait to hear from you before I mention this
to MS - I should at least be able to tell him which specific error is not
fixed by the patch. Thanks.

Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 11/27/2007
Time: 1:00:19 PM
User: N/A
Computer: ADMIN
Description:
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
ErrorCode=(288)Attempt to release mutex not owned by caller.
. Process=2860. Thread=3580. Client. Instance=PACTIPS. VD=.

"Claus" <cjo...@nova-tech.org> wrote in message

news:e85kFHVM...@TK2MSFTNGP03.phx.gbl...

Claus

unread,

Nov 27, 2007, 8:06:23 PM11/27/07

to

Dave,

Thanks for taking this on. Below are samples from 2 boxes (both
SBS2003Premium). The top part is identical to your samples. The text varies
according to the instance that is generating it.