search cancel

Control Compliance Suite 11 - After upgrade of an 11.0 Windows agent to version 11.5; subsequent data collection jobs hang and won't finish.

book

Article ID: 163890

calendar_today

Updated On:

Products

Control Compliance Suite Windows

Issue/Introduction

Control Compliance Suite (CCS) 11 - After upgrade of an 11.0 Windows agent straight to version 11.5 or in other words, skipping the upgrade from 11.0 to 11.1 and then to 11.5, subsequent data collection jobs hang and won't finish. The Application Update (APU) Job did not trigger an error, the update of the 11.0 to 11.5 was reported as complete and successful. This is an Windows agent only issue - UNIX agents are unaffected by this issue.

 

No error message is recorded during agent upgrade from 11.0 to 11.5 nor during the data collection jobs however, the data collection jobs ran on the upgraded agent hang, they run indefinitely and won't finish.

 

Environment

Control Compliance Suite 11.5 application server and managers - various SCU versions

Windows agent 11.5 agent (after "successfully" being upgraded from 11.0)

 

Cause

Upgrading a Windows 11.0 agent to 11.1 will install and update a number of essential dll's & files on the agent, skipping the 11.1 version and upgrading from 11.0 straight to 11.5 will cause the update to be skipped and subsequent data collection jobs ran on the upgraded agent hang, they run indefinitly and won't finish as it is missing these files.

The difference between a good and "bad" CCS 11.5 agent; a bad agent will be missing or has different (older) versions of:

boost_regex-vc100-mt-1_55.dll
mfc100.dll
mfc100u.dll
msvcp100.dll
msvcr100.dll
xerces-c_3_1.dll
PocoFoundation.dll
PocoZip.dll

in the C:\Program Files (x86)\Symantec\Enterprise Security Manager\ESM\bin\dcmodules directory of the agent.

Resolution

This issue will be fixed in the upcoming Product Update of CCS, current target is CCS version 11.5.1 targeted for end of January 2017 (subject to change).

If you find yourself in this situation and broke a number of windows agents and need it fixed before the public release of the fix in January, then please contact you local technical support representative and refer to this technote. Your support representative will be able to provide a interim package to fix this issue remotely.