• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Cannot Drop Database when calling Entity Framework DropDatabaseAlways Initializer

WebDBApps

New Pleskian
I've deployed an Asp.net MVC application to Plesk 12.5 running on Windows Server 2012 with SQL Server 2014. The database was already created through Plesk and a service account was assigned to it.

In testing the app, I'm calling the Entity Framework Seed method to initialize the database with an admin user. This method, for now, calls DropDatabaseAlways in my initializer. When I attempt to login, the message stating cannot drop database is thrown. Can the Plesk service account be given dbo privilege on the database? I did not see this in the Plesk database screens and am unsure if I can elevate the permissions in Management Studio.

How can I modify my server environment to allow for this database initialization? Thanks for your help and guidance.
 
Back
Top