The following message appears when registering OfficeScan (OSCE) to the Control Manager (TMCM) server:
"Unable to register to the Control Manager server. Check the Control Manager Settings on the OfficeScan Web Console or your network connection status."
A different error message appears on a test connection:
"Cannot connect to the Control Manager server or the proxy server. Please check your network settings and make sure the network connection between the entity and the Control Manager server or the proxy server is available."
When checking the CMAgent debug log, a snippet is referring to a product library that cannot be loaded:
[06/26 09:10:41 4524|320][ Msg], SEnvironmentInfo::LoadL18NLibrary : wszModulePath(C:\Program Files\Trend Micro\OfficeScan\PCCSRV\CMAgent\) [GlobalInterface.cpp|636]
[06/26 09:10:41 4524|320][FnInOut], SEnvironmentInfo::MbcsToUtf8==> [GlobalInterface.cpp|711]
[06/26 09:10:41 4524|320][ Msg], SEnvironmentInfo::MbcsToUtf8 : pszSrcMbcs(ProductLibPath) before convert [GlobalInterface.cpp|714]
[06/26 09:10:41 4524|320][ Msg], SEnvironmentInfo::MbcsToUtf8 : convert to UTF-8 success [GlobalInterface.cpp|727]
[06/26 09:10:41 4524|320][FnInOut], SEnvironmentInfo::MbcsToUtf8 nReturn=(0) <== [GlobalInterface.cpp|731]
[06/26 09:10:41 4524|320][ Fail], _EnModuleInitEx failed. [En_Utility.cpp|1916]
[06/26 09:10:41 4524|320][ Fail], Cause: Cannot load product lib: ProductLibPath. The specified module could not be found. [.\GlobalInterface.cpp, 2125] [En_Utility.cpp|1917]
That log snippet refers to the ProductLibrary.dll directory path being invalid or the DLL file itself is missing or corrupted.
To resolve this issue:
- Log on to the OfficeScan server and go to the ...PCCSRV\CMAgent folder.
- Open the Agent.ini file and make sure that the following line exists:
Product_Lib_Path=C:\Program Files\Trend Micro\OfficeScan\PCCSRV\CmAgent\ProductLibrary.dllIf the machine runs on a x64-bit OS, the file is located on the Program Files (x86) folder.
- Go to the folder location of ProductLibrary.dll and make sure that the file exists.
If the file is missing, get a copy from a working OfficeScan server that runs the same version as the current OfficeScan server environment. Put it in the CmAgent folder and restart the OfficeScan Master service.
- Verify a Test Connection to the Control Manager server. If test connection is successful, proceed with the registration.