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

Mssql 2005

S

Sylvio74

Guest
I have a problem at the registration:

ERROR: PleskMainDBException
<b>Source:</b> Microsoft OLE DB Provider for SQL Server<br/><b>Description:</b> Fehler bei der Anmeldung für den Benutzer 'admin'.

0: C:\Program Files\Parallels\Plesk\admin\plib\common_func.php3:594
db_mssql_connection()
1: C:\Program Files\Parallels\Plesk\admin\plib\common_func.php3:623
reconnect()
2: C:\Program Files\Parallels\Plesk\admin\plib\common_func.php3:584
db_connect()
3: C:\Program Files\Parallels\Plesk\admin\auto_prepend\auth.php3:79

please help me.
 
Sounds like the admin account doesn't have privileges to MSSQL. Is there an 'admin' account on the SQL server?
 
Everything ok again now after doing nothing... anyone know why this happens?
 
Mine is doing it too. Just upgraded to 8.4 a couple of days ago and it was ok until tonight. From the error log, SQL EXPRESS is running as NETWORK SERVICE which is denied access to the data folder by the Deny ACL for the psaserv group.

There's a user with a long name who has a Permit entry ahead of the Denys. Maybe that should be the user which is running the SQL service? Maybe I got a bad install? Or maybe the reconfigurator (which I ran to fix another problem) messed up the service permissions?
 
Back
Top