Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Altiris Agent 7 installs with blank window

Created: 13 Jul 2010 | 3 comments
Jon Sumida's picture
0 0 Votes
Login to vote

I am deploying BESR 2010 via Symantec Managment Console using the Altiris Agent (7.0.3599).  Most of my agents have installed just fine. I've come across one that isn't working very well. At first glace it appears to have installed fine. But then I noticed that this agent doesn't run any of the tasks assigned by policies and when you open up the Agent itself, it just appears blank. Here is a shot of it:

I checked the settings and it has a Computer ID and the NS is properly identified and the intervals have changed to the 1 hour/1 day default settings. But when comparing what's installed at the bottom of the Settings page to an Agent that's working I noticed it's missing quite a few items.

The one working on my own PC has Altiris Base task Handlers, Altiris Client Task Agent, Inventory Rule Agnet, Software Management Framework Agent, etc.

I also looked into my event viewer and at the time of installation I see an event that says "The Altiris Agent servce was successfully sent a start control", then "Atiris Agent service entered the running state" and then ",,,entered the stopped state".  At the same time as these events, I had a bunch of the following events in my Application event log:

"A provider, AAProv_ClientTaskAgentStatus, has been registered in the WMI namespace, root\CIMV2, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality. "

Finally I looked in the Agent.log file and I saw a lot of repeating of these entries:

<event date='Jul 13 14:11:26' severity='2' hostName='QMCLAB20' source='CoClient(368)' module='aexnsagent.exe' process='aexnsagent.exe' pid='3164' thread='2972' tickCount='10444968' >
  <![CDATA[Object not loaded (-2147208960)]]>
</event>
<event date='Jul 13 14:11:26' severity='2' hostName='QMCLAB20' source='AgentRegistrar' module='aexnsagent.exe' process='aexnsagent.exe' pid='3164' thread='2972' tickCount='10444984' >
  <![CDATA[Error loading internal agent info: Object not loaded (-2147208960)]]>
</event>
<event date='Jul 13 14:11:26' severity='4' hostName='QMCLAB20' source='Agent' module='aexnsagent.exe' process='aexnsagent.exe' pid='3164' thread='2660' tickCount='10445000' >
  <![CDATA[Loading client object: Altiris.SWD]]>
</event>
<event date='Jul 13 14:11:26' severity='2' hostName='QMCLAB20' source='Agent' module='aexnsagent.exe' process='aexnsagent.exe' pid='3164' thread='2660' tickCount='10445000' >
  <![CDATA[Object Altiris.SWD is not installed: Invalid class string (-2147221005). This situation should be resolved once the agent rollout has been completed.]]>
</event>
<event date='Jul 13 14:11:26' severity='2' hostName='QMCLAB20' source='CoClient(368)' module='aexnsagent.exe' process='aexnsagent.exe' pid='3164' thread='2660' tickCount='10445000' >
  <![CDATA[Object not loaded (-2147208960)]]>
</event>
<event date='Jul 13 14:11:26' severity='2' hostName='QMCLAB20' source='AgentRegistrar' module='aexnsagent.exe' process='aexnsagent.exe' pid='3164' thread='2660' tickCount='10445000' >

(I've attached the full Agent.log file)

I've attempted uninstalling and re-installing  the agent. I can't think of anything else really. Any suggestions?

Comments

Andrew Bosch's picture
29
Jul
2010
0 Votes 0
Login to vote

Clean

How are you uninstalling the agent?  I would recommend using 'AexAgenUtil.exe /clean' and then re-installing the agent from there.

------------------------------------
Principal SQA Engineer
Symantec

Glenn Woodard's picture
30
Jul
2010
0 Votes 0
Login to vote

Same Issue

I have run into a dozen machines that are having the same issue.  I uninstalled using: AeXAgentUtil.exe /uninstallagents /clean, but same issue after reinstalling the CMS agent.  Any other thoughts?  Thanks.

Glenn Woodard's picture
12
Aug
2010
0 Votes 0
Login to vote

Solution Found

After working with Symantec Support we found that the machines in question had an older version of regsvr32.exe that was dated 8/8/2000.  I replaced it with one from a working machine that was dated 4/14/2008 and then uninstall/installed the agent.  This worked for all the machines that were having the issue in my environment.