Link to home
Start Free TrialLog in
Avatar of scablifter
scablifter

asked on

SQLVDI.DLL - Which Version to Use and Where is it?

I have a site running SQL 2005 SP2 on a Windows 2003 R2 STD box being backed up by BackupExec Remote Agent v12

I am getting the error :
Event Type:      Error
Event Source:   SQLVDI
Event Category:            None
Event ID:          1
Date:                5/11/2008
Time:                9:32:00 AM
User:                N/A
Computer:        
Description:
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release mutex not owned by caller.
. Process=2152. Thread=5224. Client. Instance=. VD=

Investigations indicate that the SQLVDI.DLL needs to be updated from the version installed of 2000.085.2004.0 to 2000.85.2102.0.

Microsoft article KB934396 (http://support.microsoft.com/default.aspx/kb/934396/en-us)  indicates that the above problem can be fixed by downloading and installing HotFix KB936305, the only problem is that this hotfix does not contain the stated DLL (of either version).

Have also installed the Microsoft SQL 2005 Backward Compatibility patch as well.

I can find the DLL version 2000.85.2102.0 in the SQL 2000 SP4 patch, but do not wish to register this DLL as there may be some Library issues.

Can aybody assist with where I can get the correct verion for SQL 2005 to fix this problem?
Avatar of EugeneZ
EugeneZ
Flag of United States of America image

check for the patch
 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 
Avatar of scablifter
scablifter

ASKER

Thanks EugeneZ for that, however having unpacked this hotfix before and looked at the contents, it does not contain the stated files as per below:
Microsoft article KB934396 (http://support.microsoft.com/default.aspx/kb/934396/en-us)  indicates that the above problem can be fixed by downloading and installing HotFix KB936305, the only problem is that this hotfix does not contain the stated DLL (of either version).
Any other thoughts?.
Thanks again for your help.
-- did you run the "fix" ? did it help?
---

hmm: about the file:  it is strange - as per link it is there...

Note
The file version of the Sqlvdi.dll file in this hotfix is 2000.85.2102.0. The file version of the Sqlvdi.dll file in hotfix 935465 is 2000.85.2101.0. However, these files are the same. The file in hotfix 935465 is designed for SQL Server 2000. The file in this hotfix is designed for SQL Server 2005 backward-compatibility components.This issue is resolved in the update for the backward compatibility component of SQL Server 2005 (SQLServer2005_BC.msi). The name of the update is SQLCompat2005_SP2_Hotfix_2102.

Important
 Cumulative update packages for SQL Server 2005 Service Pack 2 (SP2) do not contain updates for the backward compatibility component of SQL Server 2005. Even if the version of the Sqlvdi.dll file in Cumulative Update 2 for SQL Server 2005 SP2 or later versions is higher than 2000.85.2102.0, this hotfix is not contained in cumulative update packages for SQL Server 2005 SP2.
G'Day EueneZ
We have applied the patch and unfortunately the DLL has not changed.  The DLL version is still the same.
Anybody got any other ideas?
SOLUTION
Avatar of EugeneZ
EugeneZ
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hello, sorry for the delay, had to wait for an outage window before re-applying the patch.
The new patch was installed; however the DLL was not updated.  Am going to uninstall the Compatibility patch and attempt a re-install tonight as I have another outage scheduled.  Will advise on outcome.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Unfortunatly there has been no resolution to this problem.  We are unable to find a way forward at this stage.  Closing issue