CCS agent based RBC job shows "Error during communication with the agent" in job message.

book

Article ID: 170516

calendar_today

Updated On:

Products

Control Compliance Suite Windows

Issue/Introduction

Receiving a communication error when running a raw based data collection (RBC) on an agent(s).  However agent ping from the CCS console successfully connects and the agent configuration settings can be downloaded from the agent.  Earlier RBC jobs may have worked fine.

 

Error in console for Job Message is:   <Domain>\<Hostname>:Error during communication with the agent

 

NOTE: Windows CCS agent logs shown below.

On the target host, the agent logs (\esm\system\<hostname>\esmagent.log) show:

[#####] [YYYY/MM/DD HH:MM:SS:000] [ERROR] Agent server: Failed to get file 'c:\program files (x86)\symantec\enterprise security manager\esm\bin\dcmodules\Control\FS_Staging\<GUID>\control\windows\cache\<domain>.MDB' from the manager '<CCS Manager hostname>'

[#####] [YYYY/MM/DD HH:MM:SS:000] [ERROR] Agent server: Failed to get file 'c:\program files (x86)\symantec\enterprise security manager\esm\bin\dcmodules\Control\FS_Staging\<GUID>\control\windows\cache\<domain>.MDB' from the manager; connection closed by remote process

 

and may show:

[#####] [YYYY/MM/DD HH:MM:SS:000] [ERROR] Agent server: Failed to open file c:\program files (x86)\symantec\enterprise security manager\esm\bin\dcmodules\AgentManifestFile.xml

 

Cause

Failure to update or replace the Domain Cache file on the agent due to an issue in the AgentManifestFile.xml file.

 

Environment

Control Compliance Suite being used with agent based data collection.  All versions 11.x and 12.x.

 

Resolution

On the agent, delete the file: "<install path>\program files (x86)\symantec\enterprise security manager\esm\bin\dcmodules\AgentManifestFile.xml"

This file, among other things, keeps track of the Domain Cache version for synch purposes.  Sometimes this file is corrupted or misread for some reason.

Re-running a Data collection or CER job against the host machine will re-push the "AgentManifestFile.xml" file and the scan should subsequently succeed.