• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

SQL DB restore fails

W

wsani

Guest
We upload the database backup file, then when a restore is attempted, the following error comes up in the Plesk log:

dbbackup.DbBackupException: Unable to restore database 'cheeky_db' ---> System.ApplicationException: Unable to open connection. Error code: 0x00000520
at psacommon.RemoteWinConnection.ConnectToNetworkResource(String host, String resourceName, ConnectionParameters connParams)
at psacommon.RemoteWinConnection.ConnectToNetworkResource(String host, ConnectionParameters connParams)
at dbbackup.DbBackupManager.Restore(String database, String backupPath, String netPath, String netUser, String netPass, Boolean dropLogins)
--- End of inner exception stack trace ---
at dbbackup.DbBackupManager.Restore(String database, String backupPath, String netPath, String netUser, String netPass, Boolean dropLogins)
at dbbackup.DbBackupManager.Main(String[] args)

Suggestions?
 
This was a permission issue. Plesk is unable to pass along the username/password that is required by the remote directory properly. So, I had to remove the user ACL and rely on network ACL to secure the "shared" restore directory.

This is after paying Parallels $75 for an incident... I finally fixed it myself...
 
Back
Top