Video Screencast Help

Faulting Application: dagent

Created: 13 Jun 2013 | 5 comments

I have a Windows 7 64-bit machine that I am trying to deploy an Altiris agent to.  Once added to Altiris, I am unable to deploy anything to the computer from Altiris, including the Altiris Agent.  Every attempt results in the Deployment Agent service shutting down.  If the service is restarted, it shuts back off within 5 to 10 seconds.  The following event is logged in the Windows logs:

Faulting application name: dagent.exe, version: 6.9.430.0, time stamp: 0x4a81fea5

Faulting module name: default.dll, version: 6.9.430.0, time stamp: 0x4a81ff53

Exception code: 0xc000000d

The firewall has been disabled, and we can communicate with the machine in multiple other ways; Remote Desktop, Administrative Share, etc.  This is the only computer on our network that I'm aware of with this problem.

Operating Systems:

Comments 5 CommentsJump to latest comment

prince_y's picture

ok can you help with the error which you are seeing in the deployment console when you try to push the job to the client machines

fabian.szalatnay's picture

 

I once had a problem, that the customer used XP and Win7. There was an XP GPO which also pointed to the Win7 machines. It broke the access rights (ACL) of the dagent directory. That way, the dagent service stopped immediatley.

So check your ACL on the altiris directories.

Fabian Szalatnay | FYRE Consulting AG | http://www.fyre-consulting.ch

HighTower's picture

I've seen this behavior on computers that have broken WMI.

BBC's picture

We recently observed something similar where the DAgent would not report to the console and the service even failed to start. This was due to the McAfee EPO agent preventing the service to start. As I'm not sure what AV software you use, it may be worth considering this and checking for an updated client on that front?

-BBC

indianaHusker's picture

Thanks for the replies.  We are using Symantec Endpoint Protection for AV.  Since this is isolated to a single machine, I doubt it's a GPO issue, but I'll certainly check that aspect anyway.  In addition, I'll check the WMI angle and get back with results there.