Findings

• Apex One debug log (\PCCSRV\Log\ofcdebug.log) shows the following:
  Error Code [ -2147467259]
  Error Description[ ADOException: Code meaning: Unspecified error Source = Microsoft SQL Server Native Client 11.0 Description = Registry information is corrupt or missing.
• On the SQL Server Configuration Manager, SQL Native Client 11.0 Configuration for Client Protocols is empty

  

  ^{Click the image to enlarge.}

• The Registry hive HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer is missing

Resolution

1. On the Apex One Server, download the native_client_11.zip file, and extract the contents.
2. Double-click the native_client_11.reg file to import the registry hive. This will populate the empty fields under SQL Native Client 11.0 Configuration for Client Protocols.
    

   The native_client_11.reg file contains the registry entries for the directory [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer]

    
3. Restart the SQL services afterward before running the Master Service.
4. Check the SQL Server Network Configuration, and confirm if the Client Protocols are enabled.

Findings

The following can be seen on the Sqlmigration.log:

HResult 0x15, Level 16, State 1.
Encryption not supported on the client.·
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Client unable to establish connection.·
HResult 0x80090331, Level 16, State 1·
SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm.

The Apex One Server can't communicate with the SQL Server because it is using Microsoft SQL Server Native Client 10.0 which is already deprecated and not supported on SQL Server 2019.

Resolution

1. Navigate to your C:\Program Files (x86)\Trend Micro\OfficeScan\PCCSRV\Private\.
2. Open ofcserver.ini and look for the [DBServer] Section.
3. Change "ConnectionString=Provider=SQLNCLI10;" to "ConnectionString=Provider=MSOLEDBSQL;".
4. Save the INI file.
5. Try to do the installation again and check to see if the issue still occurs.