SEPM replication failure between SQL server and SQL expresss database sites.
Article ID: 282549
Updated On:
Products
Issue/Introduction
Replication environment, the SEPM systems are operating smoothly, configuration of replication partners applies without
issues but after that there are failures in functioning of the replication process.
Environment
SEPM replication setup were at least one SEPM use external SQL database.
Cause
ReplicationLocal logs gives similar information:
2024-03-28 11:03:27.644 THREAD 1806 INFO: SemLaunchService> parseServiceReturnText>> return text: returnCode=1;retMessage=SQLState = 08001, NativeError = 21
Error = [Microsoft][ODBC Driver 11 for SQL Server]Encryption not supported on the client.
SQLState = 08001, NativeError = 21
Error = [Microsoft][ODBC Driver 11 for SQL Server]Client unable to establish connection
SQLState = 08001, NativeError = -2146893007
Error = [Microsoft][ODBC Driver 11 for SQL Server]SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm.
SQLState = 08001, NativeError = -2146893007
Error = [Microsoft][ODBC Driver 11 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
2024-03-28 11:03:27.644 THREAD 1806 WARNING: SemLaunchService> parseServiceReturnText>> launch service return code: 1
2024-03-28 11:03:27.644 THREAD 1806 INFO: SemLaunchService> execute>> Task name: BcpForReplication, result: 1, retry: #2
2024-03-28 11:03:27.644 THREAD 1806 WARNING: Return code: 1; Message: SQLState = 08001, NativeError = 21
Error = [Microsoft][ODBC Driver 11 for SQL Server]Encryption not supported on the client.
SQLState = 08001, NativeError = 21
Error = [Microsoft][ODBC Driver 11 for SQL Server]Client unable to establish connection
SQLState = 08001, NativeError = -2146893007
Error = [Microsoft][ODBC Driver 11 for SQL Server]SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm.
SQLState = 08001, NativeError = -2146893007
Error = [Microsoft][ODBC Driver 11 for SQL Server]A network-related or instance-specific error has occurAdd while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
2024-03-28 11:03:27.649 THREAD 1806 FINE: TableMerger>> dropTable TMP_786EF40A0A64764E401484627386411A cost mile seconds:4
2024-03-28 11:03:27.651 THREAD 1806 FINE: TableMerger>> dropProcedure P_TMP_786EF40A0A64764E401484627386411A cost mile seconds:1
2024-03-28 11:03:27.651 THREAD 1806 FINE: calling close on connection.
2024-03-28 11:03:27.651 THREAD 1806 FINE: Return connection to pool.
2024-03-28 11:03:27.769 THREAD 1806 WARNING: ReplicationTask>> replicate: Exception...
2024-03-28 11:03:27.769 THREAD 1806 WARNING: java.sql.SQLException: Failed to load data. If packet size is not too large, please modify it by scm.bcp.packet.size. Detailed message
: SQLState = 08001, NativeError = 21
Verify the ODBC drives user, if driver is version 11 newer version needs to be installed.
Resolution
Install ODBC 17, run Management Server Configuration Wizard (MSCW) do not use backup file in this and point the path to newer ODBC (170).
Additional Information
NOTE: Since you will not be using backup you need to know the password for the external SQL server database that you setup during the initial installation of SEPM.
Feedback
