Issue Plesk Migrator Fails to Detect Subscription Databases — DB-Lib error 20002

[Rabah]

Server operating system version

Windows Server 2022

Plesk version and microupdate number

Plesk Obsidian 18.0.70 Update #3 Web Host Edition

Migration Scenario:

I'm running a migration using Plesk Migrator:

• Source Server: Windows Server 2012
• Target Server: Windows Server 2022
• Remote Database Host: Microsoft SQL Server 2012 (standalone host)

The migration fails when attempting to retrieve MSSQL database information for subscriptions that rely on the remote SQL Server.

Plesk Migrator Error:

Failed to detect databases of subscription.
Failed to execute SQL query: b'DB-Lib error message 20002, severity 9:\nAdaptive Server connection failed (IP)\nDB-Lib error message 20002, severity 9:\nAdaptive Server connection failed (IP)\n'
Query: SELECT COUNT(*) AS cnt FROM master.dbo.sysdatabases WHERE name = %(database_name)s
Arguments: {'database_name': 'plesk_migrator_11375729326611153771'}
Server: IP
User: sa
Tried to connect from: the local server

Validation and Diagnostics:

Network Layer

• SQL Server is reachable from the target Windows Server 2022.
• TcpTestSucceeded : True Using Test-NetConnection -ComputerName IP -Port 1433 -InformationLevel "Detailed"
• No intermediate firewall is blocking the connection.

SQL Server Configuration

• SQL Server 2012 instance is up.
• TCP/IP protocol is enabled.
• Mixed authentication (SQL + Windows) is enabled.
• SQL Server Browser service is running even though the instance is default (MSSQLSERVER), using standard port 1433.

Manual Connection Successful

From the target Plesk server, I can connect directly using:

sqlcmd -S IP -U sa -P [REDACTED]

Observed Behavior:

Despite successful manual connectivity, Plesk Migrator fails with DB-Lib error 20002! Could it be that Migrator uses a Python-based driver like pymssql under the hood and relies on DB-LIB potentially implemented via FreeTDS to iniate communication ? If so, might this error point to a lower-level TDS handshake or protocol compatibility issue - especially given that the standard client tools connect without issue ?

Thanks in advance for any input.
Let me know if logs or additional diagnostics would help.