Skip navigation Ideas Sitemap Downloads Error: 0x4005(16389) Windows 7 Error Code 0x80004005 Especially with applications you should also consult other log files like App*.log DCMAgent.log CIAgent.log CIDownloader.log Policy*.log How about the errors in these logfiles (same timeframe)? CI not found.

I have taken these into account (lessons learned in testing).

Icon Legend and Permission New Messages No New Messages Hot Topic w/ New Messages Hot Topic w/o New Messages Locked w/ New Messages Locked w/o New Messages Read Message Post New Contributor lamont-granquist commented May 22, 2015 Yeah I think we build one chef binary and ship it everywhere, so I'm pretty sure its 32-bit And it does look like this is Testimonials "RegSERVO software is simply the best. The Operating System Reported Error 2147500037 Reply Pete Simpson said on March 26, 2014 Hi, I'm not sure what you mean by applying group policy at "another level".

Buried deep in this TechNet article is a response that suggested bundling .NET 4.5 as a package instead. No appenforce.log created! Monday, May 13, 2013 6:26 PM Reply | Quote 0 Sign in to vote Yannara, in my experience, the error message that is displayed in the failure dialog is very generic. It may need to somehow call this without SysWOW64 layer getting in the way.

I started this blog for the sole purpose of sharing remedies to problems I've faced in ConfigMgr, and an occasional cool tip or trick. my computer is error free and so fast now that it is hard for me to believe it is three years old. Update its dependant CIs CIDownloader 1/29/2013 5:53:55 PM 1036 (0x040C) Unable to read Associations Policy for ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6 : 0x0 CIDownloader 1/29/2013 5:53:55 PM 1036 (0x040C) extract DCMAgent.log DCMAgentJob({00A291BD-53C0-45B7-9804-21A631B3980A}): CDCMAgentJob::QueueEvent - Queuing Buffalo, NY - USA.

Hope it Helps , Kenny Buntinx System Center Configuration Manager MVP 3 Comments » 2 Responses to ConfigMgr 2012 RTM/SP1 : Applications failed to install during OSD with error code 16389 This does work with most packages actually, but some non-msi applications seem to have an issue with it. #9 jconnor Total Posts : 57 Scores: 0 Reward points : 27170 InstallApplication 1/29/2013 5:53:53 PM 2108 (0x083C) Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6'='' InstallApplication 1/29/2013 5:53:53 PM 2108 (0x083C) Completed installation job. Hope that makes sense/helps anyone! #10 Online Bookmarks Sharing: Jump to: Jump to - - - - - - - - - - [General Tech Discussion] - - - -

The steps which install the applications are straightforward and consists of a mix of Applications and Packages which reboots in between where required. This will cause the rest of the install to fail.Error installing .NET Framework 4.0 (exit code 16389). Several functions may not work. This is a bigger issue if you do bare-metal remote deployments or send task sequence distributions through advertisements.

Please turn JavaScript back on and reload this page. I should note that when I run them on their own, they all work just fine. Tuesday, February 05, 2013 12:25 PM Reply | Quote 0 Sign in to vote Hi Vincent, We are having same kind of trouble with a task sequence which installs software via

© Copyright 2017 All rights reserved.