Views:

To resolve this issue:

  1. Verify SQL Schema version in the Database if it is the same version with the Critical Patch Build version of the Apex One server.

    1. Check Apex One Build and Version from the console. Go to Help > About.
    2. Check DB Schema Version of the Apex One database.
    3. Log in to the database using Microsoft SQL Server Management Studio.
    4. Execute SQL Query: select * from TBL_OSCEDB_INFO.
    5. Database Schema Version is shown under the KEYVALUE column. The following are samples from a working environment:

      • Query Database Schema Version:

        Database Schema

      • Apex One Build and Version:

        Database Schema

  2. If the Apex One DB schema is different from its Build number, perform the following:

    1. Ensure that the DB server is SQL 2012 or above, as SQL 2008 is not supported.
    2. Ensure that the following configurations from Apex One DB are disabled:

      • SQL Cluster
      • Mirroring
      • Apex One DB is in the availability group
      • SQLAlwaysOn
    3. Perform the following to manually upgrade the Apex One DB schema:

      1. Access CMD and run as administrator and navigate to C:\Program Files (x86)\Trend Micro\Apex One\PCCSRV\Admin\Utility\SQL.
      2. Type the UpgradeSQLSchema.bat and press Enter.
      3. Verify the SqlMigration.log for a successful command execution.

      Sample of successful logs:

      Publishing to database 'ApexOne01' on server ‘SQL_SERVER’.
      Initializing deployment (Start)
      Initializing deployment (Complete)
      Analyzing deployment plan (Start)
      Analyzing deployment plan (Complete)
      Updating database (Start)
      Processed 14336 pages for database 'ApexOne01', file 'ApexOne01' on file 1.
      Processed 7 pages for database 'ApexOne01', file 'ApexOne01_log' on file 1.
      BACKUP DATABASE successfully processed 14343 pages in 2.045 seconds (54.793 MB/sec).
      Altering [dbo].[ofn_ConvertEngVerStr2Int]...
      Altering [dbo].[ofn_VersionCompare3DotString]...
      Altering [dbo].[osp_cb_dbQueryPolicyTrackingClientInfoData]...
      Altering [dbo].[osp_cb_dbSetScanConfig]...
      Altering [dbo].[osp_cb_dbUpdateAffectedClientStatLog]...
      Altering [dbo].[osp_cb_dbUpdateAllLogsToStatLogs]...
      Refreshing [dbo].[osp_cb_dbGetOutDateAgentCount]...
      Refreshing [dbo].[osp_cb_dbComputeClientUpdateStatus]...
      Update complete.
      Updating database (Complete)
      Successfully published database.
      
    4. If the issue persists, run CDT simultaneously from the affected Apex One Server and Agent while performing an “Update Now” in the affected machine. Provide the gathered logs and screenshot error with timestamp to Trend Micro Technical Support for further assistance.