• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

Issue MSSQL restore warning in Plesk Backup Manager

Thomas Oryon

Basic Pleskian
Server operating system version
Windows server 2022
Plesk version and microupdate number
18.0.76
Hello Plesk Support,

We are receiving a warning when restoring an remote MSSQL database from Plesk Backup Manager.

Error shown:
"Script execution error during restore database 'test_13': User does not have permission to perform this action."

Failed statements:
ALTER DATABASE [test_13] SET TRUSTWORTHY OFF
ALTER DATABASE [test_13] SET HONOR_BROKER_PRIORITY OFF WITH ROLLBACK IMMEDIATE
ALTER DATABASE [test_13] SET DB_CHAINING OFF

We verified that:

  • Plesk MSSQL server is configured with sa
  • sa is sysadmin
  • database owner is sa
  • all three database options are already OFF
We also enabled:
"Grant the ALTER DATABASE permission to all Microsoft SQL Server database users"
but the same warning still occurs.

The database appears to restore successfully, but Plesk still reports this warning.

Please advise whether this is a known Plesk issue/limitation and whether this warning can be safely ignored if the restore completes successfully.

Awaiting your reply.
 

Attachments

  • plesk_logs.zip
    4.2 KB · Views: 1
  • error database.png
    error database.png
    59 KB · Views: 2
Hi, @Thomas Oryon . Could you please confirm if "Use native MS SQL backup functionality" (in Backup Manager) was enabled for the creation of the backup in question? If yes, the behavior was caused due to a Plesk bug (PPPM-14131) and it can be avoided by disabling the option during backup creations.
 
Hello Sebahat,

Thanks for your update. We have tried to disable the "Use native MS SQL backup functionality" (in Backup Manager)" but the issue still persists. The same error shows after we disable it as well. Can you please let us know how to resolve this?

If the error can be safely ignore means, can we hide the error?

Awaiting your reply.
 
Hello Sebahat,

Yes, we have disabled the settings and then take the backup and then try to restore the MSSQL database. We are receiving the same error.

Is this Plesk Bug can be fixed in the upcoming update?

Awaiting your reply.
 
The bug in question is strictly related to "Use native MS SQL backup functionality", so in your case the issue is caused by something else. If the restoration is completed successfully, such warnings could be generally ignored.
 
I cannot provide an ETA for the fix. However, it is unlikely to be fixed in the next update. I would like to again mention that since the issue reoccurs with "Use native MS SQL backup functionality" disabled - you are not affected by the bug in question.
 
Back
Top