What are the challenges you face when working across database platforms? Take the survey
Options

SQL error 3201

DanielBrittenDanielBritten Posts: 15 Bronze 2
edited October 20, 2008 3:28AM in SQL Backup Previous Versions
I am getting the following message while trying to backup a database. Any ideas?

Backing up WM07NewStore (full database) on SQL2K5 instance to:
E:\Backups\WM07NewStore\FULL_SQL2K5_WM07NewStore_20081014_103457_1.sqb
E:\Backups\WM07NewStore\FULL_SQL2K5_WM07NewStore_20081014_103457_2.sqb
E:\Backups\WM07NewStore\FULL_SQL2K5_WM07NewStore_20081014_103457_3.sqb
E:\Backups\WM07NewStore\FULL_SQL2K5_WM07NewStore_20081014_103457_4.sqb

VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role; or try increasing the value of the
VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3201: Cannot open backup device 'SQLBACKUP_7CEC1080-53B5-4411-964A-DF2186662466'. Operating system error 0x80770006(error not found).

Memory profile
Type Maximum Minimum Average Blk count Total





Commit 764936192 4096 1188690 930 1105481728
Reserve 25014763520 4096 208922862 120 25070743552
Free 6854732546048 4096 49829072337 176 8769916731392
Private 25014763520 4096 44337500 588 26070450176
Mapped 1585152 4096 154067 57 8781824
Image 33230848 4096 239489 405 96993280

Warning 300: Backup failed. Retry attempt: 1
VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role; or try increasing the value of the
VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3201: Cannot open backup device 'SQLBACKUP_974FDBEB-83D1-4239-8FC9-3FB81D82B201'. Operating system error 0x80770006(error not found).

Memory profile
Type Maximum Minimum Average Blk count Total





Commit 764936192 4096 1188690 930 1105481728
Reserve 25014763520 4096 208922862 120 25070743552
Free 6854732546048 4096 49829072337 176 8769916731392
Private 25014763520 4096 44337500 588 26070450176
Mapped 1585152 4096 154067 57 8781824
Image 33230848 4096 239489 405 96993280

Warning 300: Backup failed. Retry attempt: 2
VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role; or try increasing the value of the
VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3201: Cannot open backup device 'SQLBACKUP_81E1A349-6802-4131-A828-54555728073D'. Operating system error 0x80770006(error not found).

Memory profile
Type Maximum Minimum Average Blk count Total





Commit 764936192 4096 1184580 935 1107582976
Reserve 25014763520 4096 207196261 121 25070747648
Free 6854732546048 4096 50401808195 174 8769914626048
Private 25014763520 4096 43893191 594 26072555520
Mapped 1585152 4096 154067 57 8781824
Image 33230848 4096 239489 405 96993280

Warning 300: Backup failed. Retry attempt: 3
VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role; or try increasing the value of the
VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3201: Cannot open backup device 'SQLBACKUP_A1FFB519-D878-4E0C-B08B-B7921C445033'. Operating system error 0x80770006(error not found).

Memory profile
Type Maximum Minimum Average Blk count Total





Commit 764936192 4096 1184580 935 1107582976
Reserve 25014763520 4096 207196261 121 25070747648
Free 6854732546048 4096 50401808195 174 8769914626048
Private 25014763520 4096 43893191 594 26072555520
Mapped 1585152 4096 154067 57 8781824
Image 33230848 4096 239489 405 96993280

Warning 300: Backup failed. Retry attempt: 4
VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role; or try increasing the value of the
VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3201: Cannot open backup device 'SQLBACKUP_2B883F1F-397B-463B-A71E-EAAC099ECAB1'. Operating system error 0x80770006(error not found).

Memory profile
Type Maximum Minimum Average Blk count Total





Commit 764936192 4096 1184580 935 1107582976
Reserve 25014763520 4096 207196261 121 25070747648
Free 6854732546048 4096 50401808195 174 8769914626048
Private 25014763520 4096 43893191 594 26072555520
Mapped 1585152 4096 154067 57 8781824
Image 33230848 4096 239489 405 96993280


SQL Backup exit code: 1010
SQL error code: 3201

Comments

  • Options
    peteypetey Posts: 2,358 New member
    I would suggest checking the sqlvdi.dll file versions that's installed on your server.

    In the registry, look for the key {40700425-0080-11d2-851f-00c04fc21759} in HKEY_CLASSES_ROOT. In the subkey InprocServer32, look for the copy of sqlvdi.dll that is used. Check the version number of this file. If you are running a 64-bit system, you should find another entry in HKEY_CLASSES_ROOT\Wow6432Node\CLSID. Again, check the version number of this file and ensure it matches the 64-bit copy.

    If you are using a 64-bit SQL Server, the 32-bit and 64-bit versions of sqlvdi.dll must match.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    The x64 version was 2000.85.2004.0, but the x86 version is 2000.85.2101.0. After making a backup copy, I copied the 2101 file to the x64 folder. I am still getting the same error. Do I need to register the DLL?
  • Options
    peteypetey Posts: 2,358 New member
    You cannot just copy the 2101 to the x64 folder if it is a 32-bit executable.

    Build 2101 was released specifically for SQL Server 2000: http://support.microsoft.com/default.as ... -us;935465. However, there does not appear to be a x64 version available.

    To get the x64 version, you'll need to apply the hotfix described here: http://support.microsoft.com/default.as ... -us;934396.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    I have downloaded the HotFix that you recommended. However, it will not install.

    The status is "Not valid" and the details is "The product instance SQL2K5 has had update 3068 installed. You do not need to install this update. An update equal to or greater than 3229 should be downloaded."
  • Options
    peteypetey Posts: 2,358 New member
    I would suggest contacting Microsoft re this. Your 64-bit version of sqlvdi.dll (2000.85.2101.0) is the copy that's installed by SQL Server 2005 Service Pack 2. It looks like further updates were applied, that did not update sqlvdi.dll, but is now preventing the hotfix from being applied.

    While it may be possible to get things working by registering matching versions of sqlvdi.dll, there are so many other files involved in the hotfix, that I would discourage doing that.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.