Answered by:
SCCM 2012 OSD Apps Install

Question
-
I am trying to install app via coalesce method. It however fails with the following error:
The task sequence execution engine failed executing the action (Install Profile Application) in the group (Install Applications) with the error code 2147500037
Action output: ... the install list
Added "Microsoft Visio Standard 2013 (64Bit)" to the install list
Added "Microsoft Afrikaans Language Pack 2013" to the install list
Added "Mocha Configuration" to the install list
Added "Business Objects Enterprise XI 3.1 Client Tools 3.1" to the install list
Added "IBM DB2 Runtime Configuration" to the install list
Added "SEB Terminal Services Shortcuts" to the install list
Added "MIP Employee Benefits 11.3" to the install list
Added "QLikView Plugin 11.0" to the install list
Added "WinZip 18.0" to the install list
Adding 11 installs to steps
Setting total steps to 12
Step 1 out of 12 complete
saAppNames.size() == saAppModelNames.size(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\dainstaller.cpp,262)
Successfully cleared App model names from TS env.
daInstaller.Execute(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,260)
Could not retrieve Model names for the applications.. The operating system reported error 2147500037: Unspecified errorWednesday, September 9, 2015 8:11 AM
Answers
-
Hi,
This is a known bug, you can create a support case with Microsoft to get more information if you are using Sp1/Sp2. What you can test is to edit each appliations properties in the Admin Console. like modifying the descripton and see if they install then..
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Wednesday, September 9, 2015 8:22 AM
All replies
-
Hi,
Are you using ConfigMgr 2012 R2 Sp1?
Regards,
Jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
Wednesday, September 9, 2015 8:18 AM -
Hi,
This is a known bug, you can create a support case with Microsoft to get more information if you are using Sp1/Sp2. What you can test is to edit each appliations properties in the Admin Console. like modifying the descripton and see if they install then..
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Wednesday, September 9, 2015 8:22 AM -
That is correct. We are using SCCM 2012 R2 SP1.
So there is no fix yet? Do I need to log this at MS?
Wednesday, September 9, 2015 8:42 AM -
Hi,
If you log it there is always hope that you get a private hotfix... no there is no fix yet.
Regards,
Jörgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
Wednesday, September 9, 2015 8:52 AM -
Hi,
If you log it there is always hope that you get a private hotfix... no there is no fix yet.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Thanks a lot for your prompt response, will log a case!
Eben Fourie
Wednesday, September 9, 2015 9:01 AM -
Hi
Please reply if you do get a private hotfix, we have had the same problem since the upgrade to 2012r2 sp1.
/Björn
Wednesday, September 23, 2015 7:45 AM -
Do you see
'saAppNames.size() == saAppModelNames.size(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\dainstaller.cpp,262)'
'Could not retrieve Model names for the applications'.in the logs?
Edit: yes, you do :-) Just re-read the initial question. See if the following works (taken from a similar Microsoft case):
You should be adding two Set Task Sequence Variable tasks in between each Install Application task. The two Set Task Sequence Variable task will set the following two variables to the following values: DAIRequestedReboot = (Leave “Value” blank) RetryAppWaitingforReboot = false
Torsten Meringer | http://www.mssccmfaq.de
- Edited by TorstenMMVP Wednesday, September 23, 2015 8:10 AM
Wednesday, September 23, 2015 8:07 AM -
Do you see
'saAppNames.size() == saAppModelNames.size(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\dainstaller.cpp,262)'
'Could not retrieve Model names for the applications'.in the logs?
Edit: yes, you do :-) Just re-read the initial question. See if the following works (taken from a similar Microsoft case):
You should be adding two Set Task Sequence Variable tasks in between each Install Application task. The two Set Task Sequence Variable task will set the following two variables to the following values: DAIRequestedReboot = (Leave “Value” blank) RetryAppWaitingforReboot = false
Torsten Meringer
Unfortunately this didn´t work for us, the first install application step is successful (9 applications) every step after that fails with same error code:
"'saAppNames.size() == saAppModelNames.size(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\dainstaller.cpp,262)'
'Could not retrieve Model names for the applications'."It doesn´t matter if we change the order of the installations steps the first one always works but none of the other.
/Björn
Wednesday, September 23, 2015 2:09 PM -
You should be adding two Set Task Sequence Variable tasks in between each Install Application task. The two Set Task Sequence Variable task will set the following two variables to the following values: DAIRequestedReboot = (Leave “Value” blank) RetryAppWaitingforReboot = false
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, September 23, 2015 3:45 PM -
You should be adding two Set Task Sequence Variable tasks in between each Install Application task. The two Set Task Sequence Variable task will set the following two variables to the following values: DAIRequestedReboot = (Leave “Value” blank) RetryAppWaitingforReboot = false
Have you added that between each step?
Torsten Meringer | http://www.mssccmfaq.de
Torsten,
We just hit this error. We did NOT see it in out testing of SP1, but it does appear to happen once we added CU1 and the hotfix.
We will attempt to add these two lines and report back on results. We are also opening a case with premier support right now.
Will
Wednesday, September 23, 2015 4:13 PM -
You should be adding two Set Task Sequence Variable tasks in between each Install Application task. The two Set Task Sequence Variable task will set the following two variables to the following values: DAIRequestedReboot = (Leave “Value” blank) RetryAppWaitingforReboot = false
Have you added that between each step?
Torsten Meringer |
Hi
Yes we added it between each step. Forgot to mention that we are using ssl. Colud possibly have something to do with it, especially port=0? Below are our complete error code:
... ing resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL'
Env variable with specified basename NYAAPP and suffix '01' is found.
Initializing Dynamic install action
MP server https://*********.se and port 0. SSL=true. CRL=true
Setting authenticator.Set authenticator in transport
Initialization successful
Added "IBM WAS 6.1 x86 Eng WKS" to the install list
Added "IBM DB2 9.5.7 x86 Eng WKS" to the install list
Added "IBM Rational ClearCase 7.1.1 x86 Eng WKS" to the install list
Added "IBM Rational ClearQuest 7.1.1 x86 Eng WKS" to the install list
Adding 4 installs to steps
Setting total steps to 5
Step 1 out of 5 complete
saAppNames.size() == saAppModelNames.size(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\dainstaller.cpp,262)
Successfully cleared App model names from TS env.
daInstaller.Execute(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,260)
Could not retrieve Model names for the applications./Björn
Thursday, September 24, 2015 6:18 AM -
Torstens variable suggestion seems to be working ok after we hit the same issue (SCCM 2012 R2 SP1).
Through premier support I've requested a hot-fix. They have stated the problem will be resolved in VNext but no word on SCCM 2012 as of yet.
- Edited by Gee Dee Tuesday, September 29, 2015 4:36 AM
Tuesday, September 29, 2015 4:34 AM -
If any of your applications within a dynamic variable list installation step could potentially exit with a 3010, you may want to pay close attention. It may perform the reboot and then fail to install any applications in the list after the reboot.
You have 2 workarounds - tell the deployment type to ignore 3010s as success, or insert multiple install application steps back to back (with the above referenced task sequence variables in between)
Will
Will
Tuesday, September 29, 2015 2:27 PM -
We got word from the product team today that the fix will be included in R2 CU2.Tuesday, October 13, 2015 7:47 AM
-
Sounds good, is there a known releasedate?Tuesday, October 13, 2015 8:28 AM
-
i raised a premier support case a couple of days ago requesting a private hotfix. It has been released publically today :-). So we don't have to wait for CU2 now.
https://support.microsoft.com/en-us/kb/3089696
The description does not exactly match up with what I have seen but I will test it.
Mark.
- Edited by Mark_Thomas Saturday, October 17, 2015 11:41 AM
Saturday, October 17, 2015 11:34 AM -
Hmmm... are there multiple issues? It doesn't seem to fix the issue I have been experiencing ("could not retrieve model names for applications").
Mark.
Monday, October 19, 2015 3:25 PM -
I'm having this problem at a customer's as well. The only thing I'm not quite clear with is, if I need to apply the update during the task sequence? Is this an R2 SP1 bug or an R2 SP1 CU1 bug?
If it's a CU1 bug, why don't I just do the OSD without the CU1 patch and have the client patched after installation?
BR,
Fred
- Edited by Fred Eric S Tuesday, October 20, 2015 3:14 PM
Tuesday, October 20, 2015 1:15 PM -
Hi all,
we were facing the same issue on SCCM 2012 R2 SP1 CU1.
Error Code: 2147500037
We solved the issue by opening every app through powershell, modify it, save it, open it again, remove modification and save again. After doing so, the error disappeared.
This script was executed on the CM server itself, having for sure the newest console/sdk in place.
Hope that helps - still waiting for CU2 !
$myApps = Get-CMApplication | Where-Object {$_.IsExpired -like "False"} foreach ($myApp in $MyApps) { Write-Host $myApp.LocalizedDisplayName Write-Host `tWrite Dummy Keyword -ForegroundColor Red Set-CMApplication -Name $myApp.LocalizedDisplayName -Keyword "Dummy" Write-Host `tClean Keyword -ForegroundColor DarkGreen Set-CMApplication -Name $myApp.LocalizedDisplayName -Keyword "" }
- Proposed as answer by Sebastian Zolg Monday, November 9, 2015 7:49 PM
Monday, November 9, 2015 7:49 PM -
Hi All
We applied the latest sccm version 1511 this week, and it finally fixed this problem!
Haven´t discovered any new issues... yet.
Thursday, December 17, 2015 1:02 PM