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 has Terminated Unexpectedly

Updated: 22 May 2010 | 8 comments
RayGallo's picture
+1 1 Vote
Login to vote

Hello,

I have been noticing something recently that alot of computers are showing up on my No config requests in last n days report.

When I troubleshoot the issue I notice the Altiris Agent service is not started on the desktop.

When I look at the Windows event viewer (from 7 days prior) I notice the Service Control manager error for the agent.

It reads:  The Altiris Agent Has terminated Unexpectedly.  It has done this 1 time(s). 
It seems as this is occuring as different times and not neccesarily upon startup.

I have many machines doing this and it seems to only have started with the 6.0.2394 agent

As anyone else seen this?

Thanks,

Ray Gallo

Comments

jharings's picture
07
May
2009
0 Votes 0
Login to vote

What is a common factor?

Are the machines all one OS version? Do the Altiris Agent logs give any further detail?

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

RayGallo's picture
07
May
2009
0 Votes 0
Login to vote

Same type of ambiguos error

Here is a screen shot of the log...It just happened today on this machine in the event log at 9:40:39 and in the altiris log at 9:40:38.imagebrowser image

luke.s's picture
07
May
2009
0 Votes 0
Login to vote

 There are a similar issue

If the desktop are Windows Vista SP2....

There are a similar issue, that can be resolved with the latest version of Altiris Agent (6.0.2403), because official support for Vista SP2 was included only on Rollup10 of Notification Server (https://kb.altiris.com/article.asp?article=44160&p=1).

What is the OS of workstations?

Regards,

If the suggestion has helped to solve your problem, please mark the post as a solution.

Fábio Sanches
Altiris Consultant

RayGallo's picture
07
May
2009
0 Votes 0
Login to vote

Sorry

The workstation in question is Windows XP SP2. 
 And I have only noticed it on Windows XP SP2 machines.  I don't think the problem is happening in Vista.  but since we only have about 15 vista machines that may not be completely accurate.

Thanks for your help.

Ray

luke.s's picture
07
May
2009
0 Votes 0
Login to vote

 RayGallo,

 RayGallo,

There are 3 AKBs that cover similar error message "Unexpected exit C0000005", please could you verify if any of these meets your issue?
https://kb.altiris.com/article.asp?article=27084&p=1
https://kb.altiris.com/article.asp?article=30776&p=1
https://kb.altiris.com/article.asp?article=38995&p=1

Regards,

If the suggestion has helped to solve your problem, please mark the post as a solution.

Fábio Sanches
Altiris Consultant

KSchroeder's picture
07
May
2009
0 Votes 0
Login to vote

We've seen this too

We have seen this occasionally due to Application Metering policies, and in your log summary it references the AeXAMAgent.dll immediately preceding the crash.  Has anyone added/modified an existing App Metering policy in your environment lately?  The 3rd link Luke posted above may be the solution (a hotfixed version of the App Metering agent).  The problems we saw were like this but caused by "bad" settings in the AM policy, particularly if we filled in the "Known As" field.

Also, you have some warnings around the Client Task Agent; if you're not using Task Server functionality, you may want to disable the Task Server policies (or at least modify the collection to only apply to those machines which have the Agent installed).  We're not using Task here or I could provide more specific paths to the policies/collections you need to use.

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

erikw's picture
09
May
2009
0 Votes 0
Login to vote

Might help

Go to the service console and check if allow service to interact with desktop is checked. This is a error we have seen before and marking it will resolve it.

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

Matt Alexander's picture
18
May
2009
0 Votes 0
Login to vote

Solved?

Hey Ray,

Have any of the solutions posted here helped you resolve the issue you're having, or have you resolved it through other means (support call, email, etc)?

If a post answered your question, please "Mark As Solution".