Veritas Configuration Manager (VCM) 6.0 agent appears to be in constant Crawling state with High CPU usage

Problem

Veritas Configuration Manager (VCM) 6.0 agent appears to be in constant Crawling state with High CPU usage

Solution

VCM 6.0 has a known issue in tracking the removable media.  
This can result in the agent being in constant Crawling state with high CPU usage.

The attached zip file contains the following drivers:
emxdrv2.sys -- corrects the issue for Windows Server 2003
emxdrv.sys -- corrects the issue for Windows 2000

Steps to install the driver on a problem agent in Windows Server 2003:
----------------------------------------------------------------------------------------------------
1. Stop the VCM agent service
2. Rename VCM driver located in %WINDOWS_HOME%\system32\drivers from emxdrv2.sys to emxdrv2.old
3. Copy the enclosed emxdrv2.sys driver into the same folder
4. Reboot the system (this step is required for the new driver to load)
5. The agent service starts up on reboot, please verify the agent is listed as Connected in the UI
6. Remove the old VCM driver, emxdrv2.old


Steps to install the driver on a problem agent in Windows 2000:
----------------------------------------------------------------------------------------------------
1. Stop the VCM agent service
2. Rename VCM driver located in %WINDOWS_HOME%\system32\drivers from emxdrv.sys to emxdrv.old
3. Copy the enclosed emxdrv.sys driver into the same folder
4. Reboot the system (this step is required for the new driver to load)
5. The agent service starts up on reboot, please verify the agent is listed as Connected in the UI
6. Remove the old VCM driver, emxdrv.old



Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)