• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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