Views:

To fix the issue, perform the steps below:

For Scenario 1:

  1. On the Apex One Server, navigate to the SQL server.
  2. Enable TCP/IP. Do the following:
    1. Open SQL Server Configuration Manager > [designated SQL Server Network Configuration for apex one] > Client Protocols > TCP/IP.
    2. Double-click TCP/IP. This will open the TCP/IP Properties window.
    3. Click on the dropdown for "Enabled", and choose Yes.
    4. Click OK.

    SQL Server Manager

  3. Restart the following services:
    • SQL Browser Service
    • SQL Service for Apex One
    • Apex One Master Service
    • Trend Micro Apex Central Service

To confirm that the issue is resolved, do the following:

  • Login to the Apex Central console, and navigate to Administration > License Management > Managed Products.
    Vulnerability protection will now be shown as successfully deployed.

    Activated Products

     
    The Activated Products column will display a number to indicate the successful license deployment for the designated product.
     
  • Redeploying the policy from Apex Central will no longer encounter any problems.
  • Vulnerability Protection service is enabled on the agent machine.

For Scenario 2:

There are two conditions in resolving this issue:

If the Apex One server website uses a 3rd party certificate (e,g, a certificate signed by corporate Certificate Authority), follow the article on Configuring Apex One to use a certificate signed by corporate Certificate Authority . In re-importing the certificate, make sure to select the option "Mark this key as exportable..."

If the Apex One server uses self-signed certificate, please follow these steps:

Renew the Apex One server web site certificate.

  1. On the OfficeScan / Apex One server, open a Command prompt and go to this location:

    \Program Files (x86)\Trend Micro\OfficeScan\PCCSRV directory
    \Program Files (x86)\Trend Micro\Apex One\PCCSRV directory

  2. Run the following command to add a new certificate to the IIS certificate store:

    svrsvcsetup –GenIISCert

  3. Confirm that the certificate is renewed.

  4. Open the IIS Manager console (inetmgr.exe).
  5. In the IIS Manager, expand the Sites folder and highlight the OfficeScan virtual site.

  6. In the Actions pane, click Bindings... to open the Site Bindings window.

  7. In the Site Bindings window, select type="https" and click Edit.... The Edit Site Binding window will appear.
  8. From the SSL Certificate section, click Select... and verify that the certificate expiration date has been extended, or select the certificate with the latest expiration date.

  9. Click OK to close the window.

Remove the old web site certificate.

  1. Open the Certificates MMC Snap-In,
  2. Navigate to Certificates (Local Computer) > 'Personal' Store

  3. Find the expired certificate. Right-click on the certificate then select Delete.
For Scenario 3:

On the Apex One server, verify that the account set in the config.properties of VP server is accurate and update it if necessary. To do this:

  1. On the Apex One server, navigate to C:\Program Files (x86)\Trend Micro\Apex One\iServiceSrv\iVP.
  2. Back up the current config.properties and drag the original file into Notepad to view the details.

    back up config.properties

  3. Ensure that configured inputs are the details you use to successfully log in to Microsoft SQL Server Management Studio.

    For this issue, we will update the database.server value from database.server=LOCALHOST\\OFFICESCAN to database.server=LOCALHOST.

    update database server

  4. We will also update the encrypted password (database.password) with plain text then restart VP Service. After that, it will automatically encrypt the password again.
  5. Restart the Apex One Master Service (ofcService.exe) and VP Service (iVPServer.exe).
  6. The VP Service should now run properly without the DB error showing in ivp_server0.log and VP license should now be deployed.
 
In case iVPServer.exe is still not running or if the VP license is not deployed, verify in ivp_server0.log for other possible issues.