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

Issue Problem when create database

jaberz

New Pleskian
Hello

when my users want create mssql database the see this error:

Error: Get database server version failed: mssqlmng failed: Invalid authorization specification
at (VADOConnection::eek:pen line 48)
at Unable to ADO conect with connection string: Provider=SQLOLEDB.1;Initial Catalog=master;Data Source=(VADODatabaseProvider::connect line 182)
at execute console command --get-server-version(vconsoleapp::start line 100)
at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mssqlmng.exe" --get-server-version "--server=" "--login=" --password(vconsoleapp::run line 117)
(Error code 1)

but admin can create database without any problem
i follow this article:
https://kb.plesk.com/en/120053
but noting happend

please help me to solve this problems

Thank you
 
@IgorG, I actually ran into this myself today when trying to migrate to a brand new Plesk Onyx v17.0.17 Update #17 server. I found that for some reason the "plesksa" MSSQL user keeps getting locked out when the Migration & Transfer Manager attempts to copy/create a database. Within MSSQL, I had to uncheck "Enforce password policy" and then unlock the user for it to work properly again.

There is no external MSSQL access to the new Plesk Onyx server, so I believe something that the Migration agent is doing is causing the MSSQL user to get locked out.
 
Back
Top