16389 Error Task Sequence
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home 16389 sccm task sequence Browse forums users FAQ Search related threads
16389 Error Code
Remove From My Forums Asked by: Application fails during OSD Task sequence a failure exit code of 16389 was returned with exit code 16389 (RequestContent from CAS failed. Error = 0x87d01202) System Center 2012 Configuration Manager > Configuration sccm error 16389 Manager 2012 - Operating System Deployment Question 0 Sign in to vote We experience a strange behavior when using a task sequence to deploy an OS together with .Net framework (4.5) application. Once that the step kicks in
Unmatched Exit Code (16389) Is Considered An Execution Failure
to install the application we get the following error: "The task sequence failed to install application Microsoft .NET Framework 4.5(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6) for action (Install Application .NET) in the group () with exit code 16389." Extract from CITaskMgr.log Initiating task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2 (WKS_CORP_.NET Framework 4.5_EN_64) for target: , consumer: {B351446F-8FDF-4DD9-AE75-F9E818E79D25} CITaskMgr 1/29/2013 5:53:51 PM 1036 (0x040C) Initiating content download : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload) CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) RequestContent from CAS failed. Error = 0x87d01202 CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) Binary content download failed. Error = 0x87d01202 : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload) CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) State transition to (Failure), Error(0x87d01202) : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload) CITaskMgr 1/29/2013 5:53:52 PM 1036 (0x040C) State transition to (Failu
→ Configuration Manager 2012 Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. We use cookies to let you log in, for ads and for analytics. OK Random Issue Plaguing OSD Deployments: Exit Code 16389 Started .net framework exit code 16389 by BzowK , Feb 23 2015 10:23 PM Please log in to reply 3 replies to error: 0x4005(16389) windows 10 this topic #1 BzowK BzowK Advanced Member Established Members 91 posts Gender:Male Location:Murfreesboro, TN Posted 23 February 2015 - 10:23 PM Hey Guys / Niall
Sccm 2012 R2 Exit Code 16389
- OSD task sequences have been one of the many things under my umbrella since starting my current position about 8 months ago. As with any environment, issues come and go - however - there's been one which occurs https://social.technet.microsoft.com/Forums/en-US/b5373b31-e594-4e1b-b6b9-ffecea05531e/application-fails-during-osd-task-sequence-with-exit-code-16389-requestcontent-from-cas-failed?forum=configmanagerosd randomly and cannot easily be reproduced which I cannot figure out. Our current OSD task sequence is fairly detailed and supports all models we use. Depending on choices made from a frontend created via AutoIT, it can do many things including apply Win7 OS, provision Win 8 OS, install apps, etc. The steps which install the applications are straightforward and consists of a mix of Applications and Packages which reboots in between where required. The Issue The issue is that https://www.windows-noob.com/forums/topic/12052-random-issue-plaguing-osd-deployments-exit-code-16389/ on some builds (1-2 per week), the TS will stop and throw an error due to an application which failed to install. The exit code is always 16389 and the application affected is random. We can continue the TS but must manually install whichever application threw it after the TS finishes. When imaging systems, we can do 1 - 12 at a time which are all running the same TS on the same computer model, but only one have the issue. In the past when trying to run the TS on the same system again, it works without the issue. In the past 3 weeks, it's occurred when installing CCleaner and Cisco AnyConnect client - both Applications - but in the past has affected many different ones. I unfortunately don't have log files to attach at the moment, but will soon. I wanted to go ahead and post in case this rang a bell for anyone who may have a suggestion or have heard of it before. Any ideas? Thanks Guys! Back to top #2 Ariendg Ariendg Member Established Members 10 posts Posted 26 February 2015 - 12:43 PM Same strange random problems with installing applications In OSD/Task Sequencewith ConfigMgr R2 2012 (Cu3) here also. The task sequence failed to install application
during an SCCM 2012 SP1 build and capture Task Sequence, both in Windows 7 and Windows 8.1, wherein the installer was running but the https://ardamis.com/2014/05/24/microsoft-net-framework-4-5-2-installation-fails-during-sccm-osd-task-sequence/ log files were not being created. I was using the Application http://mikesconfigmgrblog.blogspot.com/2014/07/microsoft-net-framework-45-not.html model in SCCM and executing the offline installer executable with the command line "NDP452-KB2901907-x86-x64-AllOS-ENU.exe /q /norestart" through a VBScript wrapper script. When the application failed during the task sequence, the error in smsts.log read, in part: Execution status received: 4 (Application failed to install exit code ) Installation failed. ... Install application action failed: 'Microsoft .NET Framework 4.5.2'. Error Code 0x80004005 ... Install Static Applications failed, hr=0x80004005 Process completed with exit code 2147500037 !--------------------------------------------------------------------------------------------! Failed to run the action: Microsoft .NET Framework 4.5.2. Unspecified error (Error: 80004005; Source: Windows) If I ran my installation wrapper script from the ccmcache subdirectory while logged exit code 16389 on as the local administrator account, the .NET Framework 4.5.2 installation ran successfully. According to the MSDN page .NET Framework Deployment Guide for Administrators, log files are written to "%temp%\Microsoft .NET Framework 4.5*.txt" and "%temp%\Microsoft .NET Framework 4.5*.html", but neither of these logs existed on my Windows 7 and Windows 8.1 systems after the installation failed. However, a log file at C:\Windows\Temp\dd_NDP452-KB2901907-x86-x64-AllOS-ENU_decompression_log.txt caught my eye. The contents of this decompression log read: [5/22/2014, 16:42:35] === Logging started: 2014/05/22 16:42:35 === [5/22/2014, 16:42:35] Executable: C:\Windows\ccmcache\1\NDP452-KB2901907-x86-x64-AllOS-ENU.exe v4.5.51209.34209 [5/22/2014, 16:42:35] --- logging level: standard --- [5/22/2014, 16:42:35] Successfully bound to the ClusApi.dll [5/22/2014, 16:42:35] Error 0x80070424: Failed to open the current cluster [5/22/2014, 16:42:35] Cluster drive map: '' [5/22/2014, 16:42:35] Considering drive: 'A:\'... [5/22/2014, 16:42:36] Drive 'A:\' is rejected because of the unknown or unsuitable drive type [5/22/2014, 16:42:36] Considering drive: 'C:\'... [5/22/2014, 16:42:36] Considering drive: 'D:\'... [5/22/2014, 16:42:36] Drive 'D:\' is rejected because of the unknown or unsuitable drive type [5/22/2014, 16:42:36] Drive 'C:\' has been se
was the issue, as it would take the full 120 minutes of time to run, then wouldn't install. I hit F8, ran CMTrace, then opened the AppEnforce.log file and noticed this error: Unmatched exit code (16389) is considered an execution failure. It sure is! I had bundled this as an application, and the program was running"NDP451-KB2858728-x86-x64-AllOS-ENU.exe" /q /norestart. This should work. It did not. In fact, besides the error, it ran this step pretty fast. The .NET 4.5 framework tends to take a long time to install, so this was definitely not right. Buried deep in this TechNet article is a response that suggested bundling .NET 4.5 as a package instead. So I did, and created a program inside with the same command line (minus the quotes), and it installed properly! The application that required it also installed properly. Having trouble deploying an app? Try it as a software package instead and see what happens! Posted by Mike Murray at 11:56 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: .NET, Application Deployment, ConfigMgr 2012, OSD No comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) About this blog... 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. ConfigMgr is complex, and the solutions that worked for me may not work for you. So please don't comment, "didn't work for me". Google your issue, maybe you can find the solution elsewhere. About Mike... I am in no way a ConfigMgr expert. But I have been a ConfigMgr admin since 2006. What I don't know is much more than what I do know, but occasionally I, like the blind squirrel finding a nut now and then, manage to come up with a solution to a problem. Links ConfigMgr Log Reference ConfigMgr Survival Guide ConfigMgr Version Numbers Microsoft AV Exclusions List Microsoft Updates Requiring Multiple Restarts My IT Forum TechNet Script Center TechNet Virtual Labs Blog Archive ► 2016 (2) ► September (1) ► March (1) ► 2015 (5) ► July (1) ► April (1) ► March (1) ► February (1) ► January (1) ▼ 2014 (7) ► November (1) ► October (2) ► September (1) ▼ July (3) Changing the ConfigMgr 2012 size and location Task sequence fails with 0x80004005 - error while ... Microsoft .NET Framework 4.5 not installing during... Simple template. Powered by Blogger.