Troubleshooting: Backup of Microsoft SQL Server 2005 (and up) and SQL Server 2005 Express (and up)
Creation Date: January 12, 2007
Revision Date: September 20, 2012
Product: DS‑Client (Windows)
Summary
This article deals with backup of Microsoft SQL Server 2005 (and up), both the Full and Express versions.
Troubleshooting / FAQ / Error Messages
Problem
If you try to backup a remote instance of Microsoft SQL Server or SQL Server Express, it may fail with the following error:
SQL server does not exist or access denied. ConnectionOpen (Connect( )).SQL:exec xp_msver ProductVersion)
Reason:
The remote SQL Server instance may not be configured for remote connections.
• By default, SQL Server Express is installed (configured) only for local connections.
• By default, Microsoft SQL Server is installed (configured) for remote connections, but this might have been changed.
Workaround:
Use the SQL Server Configuration Manager tool:
1. Start > All Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager:
• Enable TCP/IP and Named Pipes for each of the instances you want to backup.
2. Start the SQL Browser service on the remote server.
Problem
64-bit Windows DS-Client fails to create a new Microsoft SQL Server backup set (in New Backup Set Wizard) with the following popup error:
Runtime Error!
Program: c:\program files\CloudBackup\DS-Client\dsclient.exe
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.
Reason:
This is a Microsoft Bug with Microsoft SQL Server 2005. The 64-bit Microsoft SQL Server 2005 release (prior to Service Pack 1) has a problem with native 64-bit applications that use SQL-DMO (SQL Distributed Management Objects).
Solution:
The Microsoft SQL Server 2005 minimum requirement for DS-Client is Service Pack 1.
• Use 64-bit Microsoft SQL Server 2005 Service Pack 1 for the DS-Client database.
Problem
DS-Client backing up a mirrored Microsoft SQL Server 2005 database receives the following error:
BACKUP LOG WITH TRUNCATE_ONLY cannot operate on database '<database-name>' because it is configured for database mirroring.
Reason:
This is a limitation with Microsoft SQL Server 2005. Mirrored Microsoft SQL Server 2005 databases do not support the Truncate Transaction Log backup option.
Solution:
Truncate logs should not be used on backup sets connecting to a mirrored Microsoft SQL Server 2005 database. (Do not select “Truncate Transaction Log” in the New Backup Set Wizard - Set Properties Items Tab screen.)
• You can turn this option off from Backup Set Properties > Items : Truncate Transaction Log