Application Metering sub-agent cause Altiris Agent crash
Last Updated December 12, 2009
Whilst running a standard check for machines not reporting inventory using Altiris customer noticed a massive jump in figures. Upon investigation all the agents on the machines are corrupt. Having rerun an install of Altiris onto a machine; the client again stopped on the machinie and was unable to be restarted. They are collecting information but not reporting back and NS database does not updates.
The attempt to load the AgentActivate program/service resulted in a failed remote procedure call to the agent service with error (-2147023170).
The Application Metering Solution sub-agent having problems,
If you do intend to use Application Metering you should make sure that the very latest version of the solution is installed before deploying that agent again. In the meantime I recommend you make sure the AM Agent installation policy is disabled.
Meantime, please run attached file on corrupted computers. The program runs quickly and silently. But you should see the process AeXNSAgent.exe start up if it works.
- Determines what path the Altiris Agent was installed to.
- Once it finds the path it issues the following command to that path: REGSVR32 /u %AGENT_PATH%\AexAMAgent.dll
- Then it runs the command: NET START "Altiris Agent"