Skip to main content
All CollectionsGeneralBackup
Backup Fails using SQL Server or SQL Express
Backup Fails using SQL Server or SQL Express

Backup Fails using SQL Server or SQL Express Solution

Updated over a year ago

Description

When selecting File - Backup the operation fails at STEP 1. Failed to Backup message is shown. There are three possible causes of this issue:

1. The SQL Server User does not have permissions to complete a Backup Restore - verify this with your IT Administrator.

2. Your SQL Server User or Domain User account does not have File System privileges to read/write the backup file to the selected folder path - verify this with your IT Administrator.

3. You Application or Terminal Server does not have the required SQL Server binary components to enable this feature. (This is typical if the SQL Server is operating from a Domain Controller or dedicated SQL Server box.)

The following procedure outlines steps to resolve cause 3 - make sure 1 and 2 are ruled out before completing these steps.

Detail Steps

The attached files are required for clients that have an XP or other Application Server WITHOUT SQL-SERVER INSTALLED. WITHOUT THESE COMPONENTS BACKUP for SQLSERVER will FAIL AT STEP 1 of 4.

Note

STUDIO MANAGEMENT TOOLS DOES NOT PROVIDE THESE COMPONENTS.

1. Unpack this Archive in Program Files/Datapel Systems/SqlServerOnClient.

2. Register the sqldmo.dll from the run by typing: regsvr32 “C:/program files…../sqldmo.dll”.

3. Drag and Drop the sqldmo.dll file into the command line window to ensure an accurate path.

Workflow Restrictions

  • YOU DO NOT HAVE TO DO THIS IF THE SQLDMO.DLL exists on the client system.

  • If it does exist and BACK STILL FAILS - check the DLL is registered correctly.

4. Unregister it first… regsvr32 -u “C:/program files…../sqldmo.dll”.

5. The Register it again… regsvr32 “C:/program files…../sqldmo.dll”.

6. Attempt the BackUp again - an Application / Terminal Server restart is recommended.

If it still fails, do the following:

  1. Just add the Authenticated Users in SQL under Security.

  2. Under user mapping, tick all the checkboxes except db_denydatareader and db_denydatawriter.

Related Information

None

Did this answer your question?