Control Manager Integration Problems

It takes a while to test the connection between OfficeScan and Control Manager, and the connection fails.

Solution:

  1. Check the Control Manager IP address and port.

  2. Run https://{TMCM_Server}:{Port}/ControlManager/ClientCGI/cgiDelegate.dll to verify the connection between OfficeScan and Control Manager.

  3. If the connection is successful, the "8-15205" page displays. If the connection fails, the "Page not found" page displays.

  4. Check the error code in the Product.ini file in the \OfficeScan\PCCSRV\CmAgent folder.

After upgrading, the MCP agent cannot register to Control Manager version 3.5 with patch 2.

Solution: Check if the Control Manager port number is 80 or 443. If not, un-register the MCP agent, change the port number to the correct one, and register again.

After upgrading OfficeScan, the MCP agent is unable to register even if the MCP agent service has been launched already. The error code in the product.ini file is -1046.

Solutions:

  1. Stop the MCP agent service.

  2. Change the agent build number in the Agent.ini file in the \OfficeScan\PCCSRV\CmAgent folder.

[Common]

Agent_BuildNumber=100x (larger than 1000)

  1. Restart MCP agent service. This should register the MCP agent.

The product summary pages do not display when choosing OfficeScan on the Control Manager product directory tree.

Solution:

  1. Check if the OfficeScan master service and MCP agent service are running.

  2. If the MCP agent fails to upload the product profile, check if the Control Manager port number is 80 or 443. If not, un-register the MCP agent, change the port number to the correct one, and register again.

  3. In the OfficeScan Web console, go to Administration > Control Manager Settings and check if the proxy settings and two-way communication port forwarding settings are correct.

  4. Verify if the Control Manager database is corrupted. If corrupted, reinstall Control Manager.

OfficeScan does not register to Control Manager when using HTTPS and proxy authentication is configured.

Solution: Change the protocol to HTTP.

OfficeScan does not register to Control Manager installed on Windows Server 2003.

The debug log contains the following:

[04/16 15:54:17 4360|628][    Msg], DoConnect: aHttp.Perform() return (23) description=(failed writing received data to disk/application, Error while processing content unencoding: unknown compression method) [ConnectToWebServer.cpp|120]

Solution:

  1. Open Control Panel and go to Administrative Tools > Computer Management.

  2. Click Services and Applications > Internet Information Services.

  3. Right-click Web Sites and click Properties.

  4. Click the Service tab. Under HTTP compression, unmark Compress application files.

  5. Restart IIS Admin Service on the Windows services screen.