• 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.

Delete database user failed

P

Peter Johansson

Guest
I'm using Plesk 9.3 with SQL Server 2008 web edition. Creating a blank database and database users is not an issue. Deleting newly created blank databases and database user works as well. However, after importing data to a blank database (from the older sql server 2005 using the import data wizard in SQL Server Management Studio) I can neither delete the database in plesk nor delete a database user created in Plesk. I'm receiving the following error:

Delete database user failed: Object 'rewerwer.insec_users' does not exist or is not a valid object for this operation.
---------------------- Debug Info -------------------------------
0: DatabaseManagerMSSQL.php:52
DatabaseManagerMSSQL->dropUserImpl(string 'rewerwer', string 'draft-it-db')
1: DatabaseManager.php:203
DatabaseManager->deleteUser(object of type dbUser)
2: class.DataBaseUsersList.php:145
DataBaseUsersList->remove(array)
3: db_edit.php3:101

Does anyone have a clue why this is happening? Is there a solution to this problem?

Best regards,

Peter
 
I managed to solve the issue by deleting the database in SQL Server Management Studio and then re-adding it with the same name, having SA as the database owner. Not exactly sure why the error occured, but now it works.
 
Back
Top