05-25-2010 11:58 PM - edited 03-09-2019 10:59 PM
Have CSA 6.0.2, many not responding workstaitions with similar event:
The agent software failed to compile the configuration sent from the central server:
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(4256): The variable CSIDL_SYSTEMX86 was not declared
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(4550): The variable CSIDL_SYSTEMX86 was not declared
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(4708): The variable ProcessName was not declared
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(4771): The variable ProcessName was not declared
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5155): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5165): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5171): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5192): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5211): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5215): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5236): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5252): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5258): parse error
C:\Program Files\Cisco\CSAgent\cfg\agent.rul(5287)
Solved! Go to Solution.
05-26-2010 03:52 AM
You are possibly encountering bug CSCtg78612. This occurs when the CSA MC is updated from an earlier version of 6.0 to 6.0.2 and managed agents have not yet been upgraded. You should be able to address the issue by scheduling agent upgrades for the affected hosts.
You can view the full bug details here:
Scott
05-26-2010 03:52 AM
You are possibly encountering bug CSCtg78612. This occurs when the CSA MC is updated from an earlier version of 6.0 to 6.0.2 and managed agents have not yet been upgraded. You should be able to address the issue by scheduling agent upgrades for the affected hosts.
You can view the full bug details here:
Scott
05-26-2010 04:03 AM
Biggest problem that systems become unresponsable, so we need to boot workstations in safe mode & reinstall agents manually
06-04-2010 01:46 PM
If you don't feel like re-installing all of your agents when you run into this bug go through are remove the references to the @systemX86 in your (220) variables. Should take care of the issue until you can get them upgraded.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: