Backup Database is terminating abnormally

Question

Backup Database is terminating abnormally

Ransford Graham 1

When I run the backup script from SSMS Query window it completes successfully.

If I call the procedure from FoxPro SQL Pass Through SQLEXEC function I get the message: Backup Database is terminating abnormally.

Why is this happening?

Olaf Helper 47,436 Reputation points

2022-11-02T05:55:45.377+00:00

Please avoid double posts:
https://learn.microsoft.com/en-us/answers/questions/1070104/backup-database-is-terminating-abnormally.html

2 answers

Your answer

Olaf Helper 47,436 Reputation points

2022-11-02T05:55:45.377+00:00

Please avoid double posts:
https://learn.microsoft.com/en-us/answers/questions/1070104/backup-database-is-terminating-abnormally.html

Answer 1

Peter Groft 106

Step 1. Download Launch SQL BAK File Repair Tool
Step 2. Open and Browse to load the .bak file
Step 3. Select the version of the SQL Server backup file
Step 4. Click on the Multiple Backup File Options to recover and restore multiple .bak files
Step 5. Click on the Recover option and once the recovery process is done, the tool displays a preview of all recovered data items
Step 6. Now, click on the Export option to restore .bak in SQL Server Database
Step 7. Choose the Export option between Export to SQL Server Database and SQL Server Compatible Scripts. After that fill in all the required details
Step 8. If you want to restore the SQL BAK file to the new database, then select Create New Database option. Otherwise, select the Export to Existing Database option
Step 9. Choose Export with only schema or Export with schema & data option as per your requirement
Step 10. Click on the Export button to start the process of restoring the SQL Server database from the BAK file.

Hope You Find This Useful,
Peter

Ransford Graham 1 Reputation point

2022-11-02T22:32:38.783+00:00

The backup works ok when you run the stored procedure in SSMS Query window. It fails (Backup Database is terminating abnormally) when the stored procedure is called from FoxPro SQL passthrough function SQLEXEC()
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2022-11-02T22:44:26.337+00:00

Yes, we know that by now. But you need to find out why it fails. And I have given you suggestions for how you can find the accompanying error message that SQL Server produces. Without that error message, this discussion will get nowhere.

Answer 2

Bjoern Peters 8,921

Hi @Ransford Graham

Are you aware of the different techniques that are used by FoxPro to execute a SQL statement on a SQL Server?

As Erland and Cathy already stated in the other thread... this issue is not related to SQL Server; it is more related to FoxPro and how it handles SQL statements to a SQL Server.
Maybe it is running in a (connection) timeout and kills the command, or maybe the user that holds the connects has not had the correct permissions.

Maybe you have more details on the error message; in SQL Server, there should be at least (as Erland stated) two lines of error messages in the SQL Server log about this error.
And maybe it is also interesting to know, when this error happens... is it immediately after executing the statement or after a few moments that the command is stuck in the middle of a backup?

Maybe you can give us more information on this error?!

Thank you

Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2022-11-02T22:30:18.397+00:00

Actually, I did not say that it was directly related to FoxPro. The error apparently occurs in SQL Server. But FoxPro appears to drop one of the error messages on the floor. In my post in the other thread, I gave suggests for how to find the actual error message.
Ransford Graham 1 Reputation point

2022-11-02T22:55:26.987+00:00

The error message comes up immediately. I think it has to do with permissions. The Application Role is user. So far the other calls to procedures accessing the database in the Server from the Application works ok.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2022-11-02T22:58:49.96+00:00

Application Role? Yeah that could explain something. When you have assumed an application role you are a bit locked down to the current database.

But again, you need to get hold of the first error message from BACKUP! (And my post in your other thread has the information for how to do this.)

Share via

Backup Database is terminating abnormally

2 answers

Your answer