Osd Error 16389
Contents |
Reading Mode Exit code 16389 using task sequencing Author Message ekottmann866 Total Posts : 2 Scores: 0 Reward points : 0 Joined: 5/29/2008 Status: offline Exit code 16389 a failure exit code of 16389 was returned. using task sequencing Thursday, May 29, 2008 10:43 AM (permalink) 0 Hi,
Sccm Error 16389
I'm using task sequencing to install a product and it's dependencies. I'm getting a number of failures returning an unmatched exit code (16389) is considered an execution failure exit code of 16389. The only discussion on this seems to be centered on OS deployments (which is what task sequencing is for),what sort of resolution has been proposed for .net framework exit code 16389 that? Would it apply to package installs too? #1 jdavis375 Total Posts : 265 Scores: 34 Reward points : 26150 Joined: 5/1/2006Location: Minneapolis, MN Status: offline RE: Exit code 16389 using task sequencing Thursday, May 29, 2008 11:28 AM (permalink) 0 Have you been able to install this product and it's dependencies with a regular program/advertisement? That is a first step...make
Sccm 2012 R2 Exit Code 16389
sure that it works that way before throwing it in the Task Sequence. Also...be aware of the limitations required when installing via a TS: The program must be able to install as Local System. The progam can not have any user interaction. (not even a next box or a status box at the end) The program can't force a reboot...it must allow the SCCM TS to manage the reboot. Hope that helps, Jarvis My Blog: The Realm of the Verbal Processor If helpful, please rate this post! #2 ekottmann866 Total Posts : 2 Scores: 0 Reward points : 0 Joined: 5/29/2008 Status: offline RE: Exit code 16389 using task sequencing Thursday, May 29, 2008 12:31 PM (permalink) 0 Thanks, for the feedback. I have taken these into account (lessons learned in testing). This advertised task sequence is actually working on about 85% of the clients. It's just that the failures are all returning a 16389 error. I was hoping someone can shed some light on where I could look. Thanks Eric #3 klong566 Total Posts : 200 Scores
Hi Guys , Just something I wanted to share with you guys around failed the operating system reported error 2147500037 application installs during OSD and High secure environments. At that .net install error 16389 specific customer all my apps failed one by one (not my packages) during OSD with error
Error: 0x4005(16389) Windows 10
16389. At first guess , you would say that your detection methods where not ok , but it worked before when they where targeted in the http://www.myitforum.com/forums/Exit-code-16389-using-task-sequencing-m179859.aspx full OS . So , why would they fail now ? The failure is very clearly visible in the status messages : The issue was also occurring on a specific HW model , a HP 8530P … Strange. Knowing this is a highly secured environment , my first guess would be policies. http://scug.be/sccm/2013/02/13/configmgr-2012-rtmsp1-applications-failed-to-install-during-osd-with-error-code-16389-and-denied-logon-for-domain-users-policy/ However I overruled this thinking strategy because normally during the OSD process , GPO’s aren't applied … However , guess again .. It was indeed a policy , but defined on another level . They deny by GPO that if a computer is not sitting in a specific AD security group , a “Domain user” is denied from logging on to any resource. On Error Resume Next strComputer = "." Set objGroup = GetObject("WinNT://" & strComputer & "/Gebruikers") For Each objUser In objGroup.Members If objUser.Name = "Everyone" or objUser.Name = "Domain Users" or objUser.Name = "Geverifieerde gebruikers" Or LCase (objUser.Name) = "interactief" Then objGroup.Remove(objUser.AdsPath) End If Next strComputer = "." Set objGroup = GetObject("WinNT://" & strComputer & "/Users") For Each objUser In objGroup.Memb
during an SCCM 2012 SP1 build and capture Task Sequence, both in Windows 7 and Windows 8.1, wherein the installer https://ardamis.com/2014/05/24/microsoft-net-framework-4-5-2-installation-fails-during-sccm-osd-task-sequence/ was running but the log files were not being created. http://mikesconfigmgrblog.blogspot.com/2014/07/microsoft-net-framework-45-not.html I was using the Application 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: exit code Execution status received: 4 (Application failed to install ) 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 exit code 16389 I ran my installation wrapper script from the ccmcache subdirectory while logged 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
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 ConfigMg