• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Migrating Plesk 9.2 (win 2003 / SQL 2005) to Plesk 9.3 (win 2008 R2 / SQL 2008)

D

Diamatrix

Guest
When trying to migrate a domain from:

A Windows 2003 machine connected to a remote Microsoft SQL 2005 server
TO
A Windows 2008 R2 machine connected to a remote Microsoft SQL 2008 server

I get the following error:
<message code="FailedDatabaseDeployment" severity="error">
<context>plesk::DatabaseDeployer::act</context>
<file>.\databases.cpp</file>
<line>193</line>
<text>Failed deployment of database oerf (domain xxx-xxxxx.org.za)</text>
<message code="ExecCmd::ExFailed" severity="error">
<context>plesk::ExecCmd::reportError</context>
<file>.\ExecCmd.cpp</file>
<line>65</line>
<text>Execution of "C:\Program Files (x86)\Parallels\Plesk\bin\database-registrar.exe" --get-credentials 10.10.34.25: -type mssql failed with return code 1.
Stderr is
Can not found appropriate database server in Plesk
</text>
</message>
</message>
 
Check it Plesk database with

select * from databaseservers where type='mssql';

that you haven't 0 in port field. Update it with empty filed if you have it. In such cases default mssql port will be used.
After that try migration again. I hope it will help.
 
Check it Plesk database with

select * from databaseservers where type='mssql';

that you haven't 0 in port field. Update it with empty filed if you have it. In such cases default mssql port will be used.
After that try migration again. I hope it will help.

It is currently empty on both servers:

The Plesk 9.2, Windows 2003 Server:
Code:
mysql> select * from databaseservers where type='mssql';
+----+-------------+------+-------+----------------+-------------+----------------+---------------+------------+
| id | host        | port | type  | server_version | admin_login | admin_password | parameters_id | last_error |
+----+-------------+------+-------+----------------+-------------+----------------+---------------+------------+
|  2 | 10.10.34.25 |      | mssql | 9.00.3042      | sa          | ************   |           581 | no_error   |
+----+-------------+------+-------+----------------+-------------+----------------+---------------+------------+


The Plesk 9.3, Windows 2008 R2 Server:
Code:
mysql> select * from databaseservers where type='mssql';
+----+-------------------------+------+-------+----------------+-------------+----------------+---------------+------------+
| id | host                    | port | type  | server_version | admin_login | admin_password | parameters_id | last_error |
+----+-------------------------+------+-------+----------------+-------------+----------------+---------------+------------+
|  2 | mssql08.xxxxxx.xx.xx    |      | mssql | 10.0.2531      | sa          | ************   |            19 | no_error   |
+----+-------------------------+------+-------+----------------+-------------+----------------+---------------+------------+
 
In this case I can suggest you contact Support team for more deep investigation of this problem.
 
Just to provide Feedback regarding this.

Plesk Migration Manager cannot migrate remote Microsoft SQL databases if you use different Microsoft SQL servers.

Example: if you have server01 using remote mssql-server01 and you migrate a website to server02 using remote mssql-server02, you will need to migrate the database manually.

The issue is related to the way the Plesk Migration Manager handles hostname / IP address of the SQL server.
 
Back
Top