If you get one of the following error messages during the setting up of SqlBak on Linux or during the execution of a backup job:
MySQL DBMS – /bin/sh: 1:/usr/bin/mysql: not found
or
MySQL DBMS – /bin/sh: 1:/usr/bin/mysqldump: not found
it means that the SqlBak app could not find the path to the MySQL executables. By default, SqlBak searches for MySQL files in the /usr/bin/mysql directory.
If you get the following error message during SqlBak set up on Linux or during a backup job:
MS SQL Server DBMS – /bin/sh: 1: /opt/mssql-tools/bin/sqlcmd
it means that SqlBak app could not find the path to the msql executables. By default, SqlBak searches for mssql files in the /opt/mssql-tools/bin/sqlcmd directory.
If during setting up of SqlBak on Linux or during a backup job one of the following errors occurs:
PostgreSQL DBMS – /bin/sh: 1: /usr/bin/psql: not found
or
PostgreSQL DBMS – /bin/sh: 1: /usr/bin/pgdump: not found
it means that SqlBak app could not find the path to postgresql executables. By default, SqlBak looks for postgresql files in the /usr/bin/psql directory.
That issue may occur if the SqlBak (SQL Server Backup) Windows Service was interrupted by an error.
Below you can find the solution of the following SQL Server error message:
Msg 3201, Level 16 Cannot open backup device. Operating system error 5(Access is denied.)
Probably you face this error when you try to make SQL Server database backup. It has to be admitted that this error message belongs to the permissions issue on the local disk and user account which is running SQL Server.
Working with SQL Server sometimes you have to restore your database and sooner or later during the restoration process you can receive the following error message:
Msg 3117, Level 16, State 1, Line 1 The log or differential backup cannot be restored because no files are ready to roll forward. Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally.
In this article, we are going to discuss how to solve the error which can occur during the restoration of a differential backup. Here is the error message:
Msg 3136, Level 16, State 1, Line 1 This differential backup cannot be restored because the database has not been restored to the correct earlier state. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally.
Here we are going to discuss how to solve the error message “Failed to update database because the database is read-only” that you can face with working with SQL Server. Below the complete text of this error:
Msg 3906, Level 16, State 1, Line 10 Failed to update database "MyData" because the database is read-only.
Of course, experience DBA can say that your database is read-only and you don’t have any way to write into it. All you need is simply mark the database as read-write. That’s it. But still, we are going to show you, how you can solve this issue using simple T-SQL Commands or SQL Server Management Studio .
In this blog post, we are going to discuss how to solve the following error “Cannot bulk load because the file could not be opened. Operating system error code 5 (Access is denied.)”. Below you will find the reason why this error happened and the way to solve it.
Let’s imagine the following situation. You have SQL Server database and you perform backups from time to time. Something went wrong and now you need to restore your SQL Server database. You start to do it with the help of SSMS (SQL Server Management Studio) but face with the following error message: “No Backupset Selected to be Restored“.