Application Install Hang during OSD

[rddvls1999]

Actually, I was just looking at the AppDiscovery.log, and saw the following:

 

Performing detection of app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18)

+++ Application not discovered. [AppDT Id: ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, Revision: 3] AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18)

+++ Did not detect app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:25 AM 2584 (0x0A18)

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633" AND Revision = 3)" AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

Performing detection of app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

+++ Application not discovered. [AppDT Id: ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, Revision: 3] AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

+++ Did not detect app deployment type VLC(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633, revision 3) for system. AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_3d04b904-5578-4764-88b2-e05c8c5838e2 + Content Version: 1 for AppDT "VLC" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633], Revision - 3 AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_3d04b904-5578-4764-88b2-e05c8c5838e2 + Content Version: 1 for AppDT "VLC" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_b614fe1d-f1df-428b-909d-54657f77a633], Revision - 3 AppDiscovery 8/21/2014 10:52:26 AM 2584 (0x0A18)

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8" AND Revision = 1)" AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

Performing detection of app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

+++ MSI application not discovered [MSI Product Code: {1EF3289E-C805-11E2-8F40-0024E808B313}, MSI Product version: ] AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

+++ Did not detect app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:52:59 AM 2584 (0x0A18)

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8" AND Revision = 1)" AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

Performing detection of app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

+++ MSI application not discovered [MSI Product Code: {1EF3289E-C805-11E2-8F40-0024E808B313}, MSI Product version: ] AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

+++ Did not detect app deployment type PaperCut MF Client - Windows Installer (*.msi file)(ScopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8, revision 1) for system. AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_23c52018-ad4a-40de-8b22-e904fcfeb8d7 + Content Version: 1 for AppDT "PaperCut MF Client - Windows Installer (*.msi file)" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8], Revision - 1 AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

ActionType - Install will use Content Id: Content_23c52018-ad4a-40de-8b22-e904fcfeb8d7 + Content Version: 1 for AppDT "PaperCut MF Client - Windows Installer (*.msi file)" [scopeId_275CBFC1-259C-4F0C-82A7-9A6A703C862E/DeploymentType_6f3ab019-198d-41a8-8f04-cf1fc9a7f5e8], Revision - 1 AppDiscovery 8/21/2014 10:53:00 AM 2584 (0x0A18)

You may want to also check your "PaperCut MF Client" package and make sure that the source files are present.

[Schikitar]

Hi rddvls1999,

 

Well it's been a few days but I have had a breakthrough, of sorts. Infact, the breakthrough may have me on the path of resolving three major issues which has plagued me for MONTHS!

 

I don't quite know what I've done (scary, I know) but here's the basic breakdown;

• It occurred to me that I had been too obsessed with capturing log files whilst the 'hang' was happening. I let a machine image overnight because we had noticed that occasionally the install would timeout and then the machine would complete the TS (sans applications).
• I grabbed the log files from there and inside the smsts-XXXXXXXX-XXXXXX.log file was a sudden jump from the previous entry at 2.18pm (around the time it was imaging) to about 6 hours later at 8.18pm

 Waiting for job status notification... InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
AppMgmtSDK handler is invalid. Trying to reconnect... InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
GetAppMgmtSDKInterface successful InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Reconnecting to existing jobID '{682B9098-4ED7-4F9E-BBFE-61E30918C2F1}'.. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
spAgent->GetJob(jobId, &spAgentJob), HRESULT=87d00215 (e:\qfe\nts\sms\dcm\sdk\cisdkclass.cpp,1756) DCMAgent 25/08/2014 8:18:15 PM 2724 (0x0AA4)
spAppMgmtSDK->SetEvaluationCallback( guidJobID, spNotifyCompPtr ), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,456) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Failed to Reconnect to existing job, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Reconnect Job request failed, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
ReconnectJob(spAppMgmtSDK, spCallback, guidJobID), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,1233) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
WaitforJobCompletion(spAppMgmtSDK, m_guidAppInstallJobID, ulAppInstallTimeout, nAppInstallRetryAttempts), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,1122) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Step 2 out of 2 complete InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Install application action failed: 'Microsoft Office Professional Plus 2013 with SP1'. Error Code 0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Sending error status message InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting URL = http://SCCM-SVR.lcgs.local, Ports = 80,443, CRL = false InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting Server Certificates. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting Authenticator. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Set authenticator in transport InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
   Setting Media Certificate. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Sending StatusMessage InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Setting message signatures. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Setting the authenticator. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SVR.lcgs.local:80  CCM_POST /ccm_system/request InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Request was successful. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Install application action cannot continue. ContinueOnErrorFlag is set to false. InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
hrInstallation, HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,914) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=87d00215 (e:\qfe\nts\sms\client\osdeployment\installapplication\main.cpp,277) InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Install Static Applications failed, hr=0x87d00215 InstallApplication 25/08/2014 8:18:15 PM 2724 (0x0AA4)
Process completed with exit code 2278556181 TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
!--------------------------------------------------------------------------------------------! TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
Failed to run the action: Install Office.
Item not found (Error: 87D00215; Source: CCM) TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
MP server http://SCCM-SVR.lcgs.local. Ports 80,443. CRL=false. TSManager 25/08/2014 8:18:15 PM 2312 (0x0908)
Setting authenticator TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Set authenticator in transport TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Sending StatusMessage TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Setting message signatures. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Setting the authenticator. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM-SVR.lcgs.local:80  CCM_POST /ccm_system/request TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Request was successful. TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Set a global environment variable _SMSTSLastActionRetCode=-2016411115 TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Clear local default environment TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Let the parent group (Setup Operating System) decides whether to continue execution TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)
Failed to run the last action: Install Office. Execution of task sequence failed.
Item not found (Error: 87D00215; Source: CCM) TSManager 25/08/2014 8:18:16 PM 2312 (0x0908)

• Looking at the error codes I did a search on 0x87d00215 which turned up a few bits and pieces, but eventually a post, within a post within a post (Inception!) lead me to this article which I had to use Bing Translator to read - http://adminsccm.blogspot.com.br/2013/06/failed-to-get-dp-locations-as-expected.html
• This article goes on to describe a problem with the original CM Client installation, which is something I have had problems with for a long time. Using the steps in the article I manually created a new client package as outlined, then I ran some SQL queries to clean things up...

  • select * from ClientDeploymentSettings

    - to return the reference to the ccm client install and upgrade packages

  • update ClientDeploymentSettings set UpgradePackageID = '' where UpgradePackageID = 'LCG00003'
    - LCG00003 was an update package that was constantly showing up in distmgr.log with problems, I used this to remove it from the current client package 'LCG00002' (which also had problems)

  • update ClientDeploymentSettings set FullPackageID = 'LCG0011E' where FullPackageID = 'LCG00002'

    - to associate my new manually created package (LCG0011E) in place of the originally automatically generated package (LCG00002)

• At this point I edited the TS, added my new package to the "Setup Windows and Configuration Manager" step and set off imaging the same machine I've been using so far, then I went to lunch
• Upon returning from lunch (about 30mins) the OSD was nearly finished and shortly completed thereafter without incident. I logged in and Office was installed as was the most current version of the ccm client (5.00.7958.1303)
• I did a little dance
• Next I thought I would add all the other application installs back into the OSD TS (about 8 in total), so I went back and edited it
• This time I got an error complaining that the previous Config Manager setup package was no longer available - what the flip?
• I browse to the root of the Packages folder in the console and my manually created package has mysteriously disappeared
• In its place was a new automatically generated package (it had a new package ID as well)
• I decide to rerun the SQL query select * from ClientDeploymentSettings which returned the following;

FullPackageID	UpgradePackageID	UpgradeProgramName				UpgradeAdvertisementID 	UpgradeVersion 	EnablePeerCache
LCG0011F 	LCG00120 		Configuration Manager Client Upgrade Program 	LCG20058 		5.00.7958.1000 	1

• This is not what I had changed it to before lunch so ConfigManager has done it's own bit of magic here (obviously not happy with my manual package and tinkering)
• Okay, well I decided to then associate this newly automagically created package to the TS and set off another re-image of a machine
• Sadly, this has now resulted in the 'hang' happening in exactly the same spot as before

Whilst I'm no further ahead in terms of imaging machines I feel there is some insight to be gained here. I hope someone reading this might have a light-bulb moment, I'm not entirely sure what to do next...

[Schikitar]

Okay, here is the ccmsetup.log from a failed images machine. When I was imaging it I took note that the ccmclient started it's install at around 12.57pm, then at 1.01pm it finished and about 15 seconds later it began the Office install (which then fell over as expected.

 

Looking at this log it seems like the client is installing, then reports "An MP does not exist on this machine" followed by "No client is currently installed" and then it begins the installation again. Then right at the end it states "A Fallback Status Point has not been specified" and then it starts deleting all the ccmsetup files (which, oddly, are there and the client is installed).

 

Does this sound right/normal?? I think I need some help with rebuilding the client source files and configuring the install...

 

I have also attached the smsts-20140826-191650.log file which shows the 6 hour failover time between approximately 1pm and 7pm.

 

I hope someone can assist!

ccmsetup.log

smsts-20140826-191650.log

[killragtshirts]

Hi,

 

Did this ever get resolved/? I'm experiencing the exact same thing.

 

Thanks for all your info in the post.

[mmosley]

Hi,

 

I'm also having the same issue after upgrading to R2 SP1 CU1, has anyone had any luck in finding a resolution?

 

Thanks

[joengelhart]

I also am having this issue when applications are getting installed. Does anyone have a resolution yet?

 

Thanks!

[Epitome]

I too spent too much time trying to fix a nearly identical problem. I'm running SCCM 2012 R2 SP1 and ran into a 6 hour 'pause' during the "Install Optional Applications" step of my MDT-integrated SCCM OSD TS. It didn't matter which application was in second place on the list, it would pause at it for 6 hours, then finish the TS. I tried many different solutions for similar problems (setting high performance power settings, installing the applications while on a workgroup then joining the domain, etc). My manager agreed to let me call MS directly and their tech had a solution for me almost immediately:

Insert a "Restart Computer" command before "Install Optional Applications".

 

In my case it was between that and the previous step "Convert UDI App List". I would've thought a reboot would lose the data required to know which applications to install, but apparently not. So, once again the solution is: "Have you tried turning it off and on again?" Who woulda thunk it?

[Hamza SMAILI]

Hello , i have the same problem in my TS , but i resolved it by adding   before install application ( GPUPdate / force and  restart service CCMEXEC ) you can do a PS1 scrip : net stop ccmexec and net start ccmexec . 

Thank you 

Hamza SMAILI

[Mamejay]

On 5/5/2016 at 6:53 AM, Epitome said:

I too spent too much time trying to fix a nearly identical problem. I'm running SCCM 2012 R2 SP1 and ran into a 6 hour 'pause' during the "Install Optional Applications" step of my MDT-integrated SCCM OSD TS. It didn't matter which application was in second place on the list, it would pause at it for 6 hours, then finish the TS. I tried many different solutions for similar problems (setting high performance power settings, installing the applications while on a workgroup then joining the domain, etc). My manager agreed to let me call MS directly and their tech had a solution for me almost immediately:

Insert a "Restart Computer" command before "Install Optional Applications".

 

In my case it was between that and the previous step "Convert UDI App List". I would've thought a reboot would lose the data required to know which applications to install, but apparently not. So, once again the solution is: "Have you tried turning it off and on again?" Who woulda thunk it?

I joined just to say "THANK YOU!!"  

Super old thread but this has saved my sanity