Antigen deployment Agent error
-
Monday, May 14, 2012 8:12 AM
Hi All,
I am facing issue on one of my Bridhead servers with details as:
Event Type: Error
Event Source: DeploymentAgent
Event Category: None
Event ID: 100
Date: 14/05/2012
Time: 08:48:13
Description:
Mon May 14 08:48:13 2012 ERROR CoCreateInstanceEx failedEvent Type: Error
Event Source: DeploymentAgent
Event Category: None
Event ID: 100
Date: 14/05/2012
Time: 08:48:13
Description:
Mon May 14 08:48:13 2012 ERROR Error "Access is denied." (0x80070005) creating notifier on "DTC-STJ-INF-03"can any one plesae help me how to get this issue fixed ASAP.
Jatin kakkar
Jatin kakkar
All Replies
-
Monday, May 14, 2012 8:34 AM
Hi,
check the following article:
http://support.microsoft.com/kb/934007/en-us and search in it for "Access is denied." (0x80070005) creating notifier".
Greetings
Christian
Christian Groebner MVP Forefront
-
Monday, May 14, 2012 2:27 PM
Thank you Christian for the update, I had followed all information as per MS article but still I am stck with above mentioned errors saying:
Event Type: Error
Event Source: DeploymentAgent
Event Category: None
Event ID: 100
Date: 14/05/2012
Time: 08:48:13
Description:
Mon May 14 08:48:13 2012 ERROR CoCreateInstanceEx failedEvent Type: Error
Event Source: DeploymentAgent
Event Category: None
Event ID: 100
Date: 14/05/2012
Time: 08:48:13
Description:
Mon May 14 08:48:13 2012 ERROR Error "Access is denied." (0x80070005) creating notifier on "DTC-STJ-INF-03"any thing else i can do to fix this issue ?
Jatin kakkar
-
Tuesday, May 15, 2012 2:38 AMModerator
Hi,
Thank you for the post.
Have you tried to install the latest version SP2 rollup4? Is it the same issue as the kb that there is “GetEngineFromHTTP” error before this error? If not, do you receive any other error message?
Regards,
Nick Gu - MSFT
-
Thursday, August 30, 2012 2:06 PM
Hi Jatin,
Normally the error you are seeing relates to DCOM permissions issue. The easiest way to address this, in this case, is probably to uninstall the FSSMC agent (add/remove programs on the affected server) and redeploy the FSSMC agent to this machine.
Please try this and let me know if this resolves your issue or not.
Alex
Alex

