Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, January 18, 2013 12:10 AM
Windows 7 64bit task sequence with HP 6570b.
SCCM 2012 Sp1
They hang just after the sccm client installation.
I verified we have the AD group ConfigMgr Remote Control Users
Our 32bit image seems to work fine.
From the smstslog
Waiting for CcmExec service to be fully operational TSManager 1/17/2013 3:36:50 PM 2988 (0x0BAC)
Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' TSManager 1/17/2013 3:36:51 PM 2988 (0x0BAC)
Failed to create an instance of COM progress UI object. Error code 0x80070015 TSManager 1/17/2013 3:36:51 PM 2988 (0x0BAC)
All replies (56)
Thursday, May 1, 2014 11:13 PM âś…Answered
We had a support call with Microsoft and the print spooler was determined as the cause of the ccmexec hang. In Windows 8.1 in taskmgr you can select the analyse wait chain on the process to see which process its waiting for. In our case it was the print spooler. As soon as this is stopped and disabled the builds continued successfully.
When you next get the issue try stopping/killing the spoolsv.exe and see if the build then continues.
Friday, January 18, 2013 2:34 AM
Hey Shikikami24,
What other steps are present in your task sequence? Can you please look a little more in smsts.log and see if there are any failures?
Thanks,
Moiz
Friday, January 18, 2013 4:34 PM
There are no failures that i can see.
Prior to the hang the task sequence installs Windows 7 64bit, adds to the domain, installs drivers and loads the configmgr client.
Our 32 and 64 bit task sequences are identical to this point and the 32 seems to have no issues with other models.
When installing the ConfigMgr client via task sequence with SCCM 2012 SP1 should i be using any Installation Properties such as SMSSITECODE?
We only have one site so we dont set any properties currently.
My next step is to get the 32bit drivers for this model and see if it will have the same errors.
cheers
Friday, January 18, 2013 4:40 PM
Sounds like you need to check the client's ccmsetup.log file for details, if that's where the problem occurs. Check in there to see if this hotfix applies to you http://support.microsoft.com/kb/2801987
Nick Moseley | http://t3chn1ck.wordpress.com
Friday, January 18, 2013 5:18 PM
CCMSetup.log shows client.msi installation succeeded
CCMSetup is exiting with return code 0
I did thave the MicrosoftPolicyPlatformSetup.msi issue however i fixed that yesterday by loading the hotfix and distributing the changed client.
CCM appears to install correctly is just hangs and fails to make an instance for the progress UI for no reason that I've found yet.
I'll update this post when i try 32bit drivers and if that doesnt work i may have to capture a new image which I'd rather not do.
cheers
Thursday, January 31, 2013 4:05 PM
I am having the same issue on XP x64, our Windows XP 32 bit and Windows 7 x64 task sequences however are not affected.
Anyone else having this issue or have a solution?
Thursday, January 31, 2013 6:51 PM
I never got it resolved, today we are rebuilding our Windows 7 64bit image from scratch to see if that helps.
Wednesday, February 6, 2013 5:54 PM
Update:
Making a new Windows 64bit operating system image seems to have corrected this issue.
Wednesday, March 27, 2013 2:45 PM | 1 vote
check services.msc, locate the SMS Agent Host service, if it is not running then start it, this worked for me :)
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Monday, March 31, 2014 10:28 AM
This is clearly not the answer to this question, so why have you marked it as such? MVP? I don't think so...
Anyway I wondered if anyone else has seen this issue recently? We are currently experiencing it with our Windows 8.1 64 bit OSD task sequence, but only with the MS Surface Pro 2 device!
I am loathed to re-create our WIM (as was described above) since it works fine on all other hardware.
Anyone got any ideas regarding the Surface and this issue?
thanks in advance,
Tim
Tuesday, April 1, 2014 7:14 AM
hi Tim,
thanks for your comments, can you do us all a favor and post a link to your log files (smsts*.log) so that we can troubleshoot your issue for you and hopefully figure out what is really happening here and possibly find a solution?
good man.
cheers
niall
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Tuesday, April 1, 2014 8:21 AM
Maybe one of the client pre-requirements wasn't installing correctly or was not installed correctly in your previous x64 Windows 7 image? There are quite a few of them so if it was an older image its a possibility http://technet.microsoft.com/en-us/library/gg682042.aspx#BKMK_prereqs_computers
Tuesday, April 1, 2014 9:13 AM
and as regards marking the answer, I'm happy to remove it and have requested same, however when I try to do so I get an 'unexpected error', once we know the true cause of people's failures we can mark them as the answer, but in order to get there we need more info about how images are being captured and deployed, and we need the logs referenced above.
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Tuesday, April 1, 2014 9:36 AM | 1 vote
Timft, do you usually insult people that are giving you free support, not very sporting of you is it chap.
Do you treat your team members at Deloitte with the same disrespect?
Play nicely here please.
Robert Marshall | This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs
Wednesday, April 9, 2014 5:35 PM
Hi all,
Our TechNet forums team is looking into the problem of unmarking Niall's answer. Please bear with us and Niall as we try to get this topic back on track.
Thank you.
-Adam
Wednesday, April 9, 2014 7:01 PM
I am having similar issues with the SMS Agent Host service showing as started but not being accessible. The issue comes during the first Install Package step, and it shows waiting for the service to start but it never does. Restarting SMS Agent Host fixes it. We dont see it on all builds, intermittently across the board though. No specific hardware or task sequence. All builds are Win7x64.
Failed to create instance of ISoftwareExecutionRequestMgr interface, hr=0x80070005 InstallSoftware 9/24/2013 11:57:01 PM 4084 (0x0FF4)
Waiting for ccmexec process to start InstallSoftware 9/24/2013 11:57:01 PM 4084 (0x0FF4)
Failed to create instance of ISoftwareExecutionRequestMgr interface, hr=0x80070005 InstallSoftware 9/24/2013 11:57:31 PM 4084 (0x0FF4)
Waiting for ccmexec process to start InstallSoftware 9/24/2013 11:57:31 PM 4084 (0x0FF4)
Failed to create instance of ISoftwareExecutionRequestMgr interface, hr=0x80070005 InstallSoftware 9/24/2013 11:58:01 PM 4084 (0x0FF4)
We have a premiere call open right now and are working with Microsoft on it. So far the only thing we have found is adding a pause before the first Install Package step helps, but does not resolve the issue.
I will keep everyone posted on what we find.
Daniel Ratliff | http://www.PotentEngineer.com
Wednesday, April 16, 2014 11:12 AM
Hi, I have struck this issue today while building a Windows 8.1 x64 (with update 1) Surface Pro 2. At this stage I'm using the native 8.1 wim file from the iso file just released on April 14 which contains update 1.
Our environment is SCCM 2012 R2.
The smsts.log has the "Waiting for ccmexec process to start" error over and over. Initially this was at the Install Software Updates step, but disabling this just moved the error on to the next step.
I'll try this out on other hardware to see if this is only occurring on Surface Pro 2.
Thursday, April 17, 2014 6:01 AM
and i too have got the same issue on the Surface Pro 2 also (CM12 R2 CU1), it seems the same hardware did not have the issue a week ago when it was imaged with Windows 8.1, the only difference that i can see is the addition of 'update 1'. I'll be debugging this today and if I find anything i'll post it here.
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Thursday, April 17, 2014 6:14 AM
Thanks Niall, I've tried the build on desktop hardware and it works fine.
I've also tried the pre-update1 install.wim on the surface pro 2 and I did get the same error.
Thursday, April 17, 2014 6:33 AM
checking event viewer shortly before after the problem occurs I can see that "A Service was installed in the system. Service Name: SMS Agent Host
a few moments later, (don't know if it's related or not) A Problem has occurred with one or more user-mode drivers and the hosting process has been terminated. The may temporarily interrupt your ability to access the devices.
and then shortly after that the event viewer (System) repeats the same event ID 10016 for ever, and that states "The Application-specific permission settings do not grant local launch permission for the COM Server application with CLSID {5179b48c-c9fb-4ce1-b0ea-c3bf0e68c04c}
a quick search shows me this http://www.internetsecurityzone.com/Entities/?\_{5179B48C-C9FB-4CE1-B0EA-C3BF0E68C04C} which lists ccmexec and execmgr.dll as the culprits, and that may explain why the SMS Agent Host service is stuck ini 'stopping' mode and cannot be started.
I checked the ccm client files in C:\Windows\CCM and all are dated 2013/09/11, we updated to CU1 last week so perhaps the client needs the CU1 patch installed also and this may resolve, i'll test this and post back when I find out...
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Thursday, April 17, 2014 6:49 AM
so i've added the patch statement to the Setup windows and configMgr step like so (after previously copying said patch to the specified folder below)
SMSCACHESIZE=20000 CCMLOGMAXHISTORY=5 CCMLOGMAXSIZE=5000000 PATCH="C:\Windows\Temp\CU_Hotfix\configmgr2012ac-r2-kb2938441-x64.msp"
i'll do a test installation now and see if things are looking any better.
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Thursday, April 17, 2014 6:51 AM
we aren't running the CU1 update for R2 yet so it be interesting to see if CU1 is needed for the Surface Pro 2's
Thursday, April 17, 2014 8:08 AM
from what I can see it has got beyond the point it was hanging at so this is looking promising. it;'s working with the CU1 patch in the setup windows and configmgr step !
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Thursday, April 17, 2014 8:31 AM | 1 vote
yup that resolved it and the installation continued to the end. However from one problem to another, I got a BSOD related to 'driver power state failure' and I believe that is driver related, or SEP
can you confirm if the CU1 Patch i've tried above works for you ?
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Thursday, April 17, 2014 10:10 AM
Thanks Niall, appreciate you testing this out. I'll have to upgrade our infrastructure to cu1, so cant do this straight away,
I've also raised a support request to Microsoft, so hopefully they will confirm that cu1 for R2 resolves this issue with the surface pro 2.
I'll update when I hear back.
Thursday, April 17, 2014 10:39 AM
ok this is just weird, i'm trying a second install to monitor the behaviour and now the message originally logged is back in SMSTS.LOG
Failed to create co... and it's complaining about waiting for CCMexec process to start however, the service is started and running (not stopping like before),
i'll keep monitoring it and let you know how it goes..
so right now, my earlier excitement is dashed, the patch has made a difference but the problem is not solved.
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Friday, April 18, 2014 4:55 PM
Not to make matters worse, but we aren't on R2, just SP1 CU3. Our R2 upgrade is coming soon though. Our issues are across the board, no specific models, and intermittent also. For us the service is already started.
Daniel Ratliff | http://www.PotentEngineer.com
Monday, April 21, 2014 5:26 PM
hi Daniel
what operating system are you deploying when you see the issue ?
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Monday, April 21, 2014 5:45 PM
We are deploying Win7x64. We do have some Win8x64 but it's only in pilot phases, so we do not have many deployed.
Daniel Ratliff | http://www.PotentEngineer.com
Monday, April 21, 2014 7:09 PM
and is your problem exhibiting the same symptoms as mine ?
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Monday, April 21, 2014 7:30 PM
It looks like it. Check my reply on 04/09 above with a log snippet. My issue happens on the first boot up into the full OS, right after the Setup Windows and ConfigMgr step but before the first Install Package step. The ccmexec process is started but not accessible. If I stop it and re-start it, the task sequence moves on without issue.
Daniel Ratliff | http://www.PotentEngineer.com
Tuesday, April 22, 2014 6:26 AM
thanks Daniel
do you have any updates in the captured wim ? if so how did they get in there (offline servicing or another method)
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Tuesday, April 22, 2014 12:25 PM
Yes, but they are all installed during the build & capture. No offline servicing or manual changes to the .wim. Completely automated via the build & capture. Our current image includes all non-superseded patches prior to 2014.
Daniel Ratliff | http://www.PotentEngineer.com
Wednesday, April 23, 2014 6:35 AM | 1 vote
Niall, have you tried building the Surface Pro 2 without the usb hub? The hub looks to be causing the build on the Surface to hang in our case.
Try building with the hub connected initially (with usb media and usb network adapter connected to the hub) , and then after the build applies OS image and surface drivers and reboots, remove the usb hub and connect the USB network adapter directly to the Surface.
This gets me further in the builds, although I have another separate issue now.
Wednesday, April 23, 2014 10:09 AM
thanks Carlito, i'll definitely try this as soon as my current deployment is done, this time round i've disabled the surface2 drivers steps (as a test).
cheers
niall
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Wednesday, April 23, 2014 10:23 AM
update, disabling the drivers step allowed it to continue as normal, could be a driver that's causing it, i will retest.
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Thursday, April 24, 2014 11:21 AM
I had to give the surface 2 back to the guys who need it, if I can get my hands on it again i'll continue testing.
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady
Thursday, May 1, 2014 12:00 AM
Hi, to update, the issue causing the hang on our Surface Pro's is due to the ccmexec service waiting on the Print Spooler service. To workaround this we have added a step following Setup Windows and Configmgr to stop and disable the Print Spooler service and then re-enable the service at the of the build.
Thursday, May 1, 2014 12:35 PM
How did you pinpoint this? A log of error somewhere? Our issue is intermittent, so we can add the fix but we dont be truly sure it is gone unless we can see another symptom disappear.
Daniel Ratliff | http://www.PotentEngineer.com
Thursday, May 8, 2014 9:03 PM
Unfortunately that didnt fix it for us. We had a handful of machines hang this week and we checked the print spooler on each one. Microsoft was on the line as well. What we did find though is when the service hung, the event logs started filling with DCOM CLSID errors. Microsoft is reviewing those now, I will keep everyone posted.
Daniel Ratliff | http://www.PotentEngineer.com
Tuesday, June 10, 2014 5:44 AM
I had the same problem today and it was fixed by stopping the spooler service. We are running CM 2012 R2 CU1.
Wednesday, August 27, 2014 2:41 PM
We have run into this exact scenario. Why would stopping the print spooler service fix the issue with installing the MBAM client?
BR
Wednesday, August 27, 2014 2:51 PM
Why would stopping the print spooler service fix the issue with installing the MBAM client?
Which MBAM client issue are you talking about at all?
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, August 27, 2014 3:02 PM
We have upgraded from CM 2012 SP1 to CM 2012 R2 CU2. Upgraded to MDT 2013. MBAM v 2.0.
The scenario is right after we have activated the TPM, we reboot the computer and then install the MBAM client. A gold build finishes fine but on a Windows 7 to Windows 7 refresh, the MBAM client installation freaks out the task sequence and it never finishes.
BR
Wednesday, August 27, 2014 3:06 PM
And where is the connection to ccmexec.exe hanging? You would have to examine logs why "client installation freaks out" (whatever that might mean in technical terms)
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, August 27, 2014 3:12 PM
This post says the print spooler service is causing the ccmexec.exe to hang and the fix is to stop and disable the print spooler service right after the CM client install and then enable and start at the end of the TS.
In the SMSTS.log, at the very end it is waiting for the ccmexec service to start. "Waiting for ccmexec process to start."
This seems like a bug and workaround. Is there a hotfix for this issue or maybe we should be using MBAM 2.5 client?
Thanks!
BR
Wednesday, August 27, 2014 3:23 PM
This post says the print spooler service is causing the ccmexec.exe to hang and the fix is to stop and disable the print spooler service right after the CM client install and then enable and start at the end of the TS.
In the SMSTS.log, at the very end it is waiting for the ccmexec service to start. "Waiting for ccmexec process to start."
This seems like a bug and workaround. Is there a hotfix for this issue or maybe we should be using MBAM 2.5 client?
This does still not answer the question to the connection to the MBAM client. MBAM <> ccmexec.exe!
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, August 27, 2014 3:32 PM
Correct, the MBAM 2.5 client wouldn't fix this. We looked at the eventvwr of a computer that had this issue last night and there are lots of print spooler errors so I am going to investigate what is causing the print spooler to not start. The error in eventvwr is "The print spooler failed to load a plug-in module SN0ELMON.dll, error code 0x7e"
BR
Wednesday, August 27, 2014 4:08 PM
Correct, the MBAM 2.5 client wouldn't fix this.
And why did you mention the MBAM client at all then? You even mentioned that the eventlog is showing spooler errors ...
Why don't you just try the suggested workaround that was mentioned above?
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, August 27, 2014 4:12 PM
The whole issue started when the MBAM client failed to install. I am going to test the workaround of stopping and disabling the spooler service and renabling and starting at the end. My main purpose is to try and unvail the real culprit, fix it, instead of using the workaround.
BR
Wednesday, August 27, 2014 5:19 PM
Our issue never got resolved, and we never had any issues with the spooler service. We have an archived ticket with Microsoft, but as far as we can tell, we no longer have this issue after our R2 CU1 upgrade. It has been about two weeks without a single report.
Daniel Ratliff | http://www.PotentEngineer.com
Friday, September 5, 2014 5:01 AM
I have the same issue. After frst boot up in the full OS, the ccmexec process hangs. We got the same error messages in eventlog.
But this happens only while deploying Windows Server 2008 R2 Enterprise Edition to ESX-machines. If i deploy the Enterprise Edition to Hyper-V machine or to physical server there are no Problems.
Even if i deploy the standard Edition of Windows Server 2008 R2 to ESX-machines there are no problems. Only in case of Enterprise Edition/ESX-machine.
Friday, September 5, 2014 7:25 PM
Does it happen on every build or intermittent?
We are using Win7 x64 w/SP1 Enterprise Edition, but saw it on physicals as well as VMs.
Daniel Ratliff | http://www.PotentEngineer.com
Tuesday, September 9, 2014 6:02 AM
We only have this issue with ESX-VMs if we deploy W2k8R2 Enterprise Edition or W2k12R2 (Standard Edition). It happens on every build.
No Problems with Standard-Edition for W2k8R2 on ESX-machines.
Tuesday, October 21, 2014 2:00 PM
Just an update, after the R2 CU1 upgrade, our issues never came back. It appears the upgrade resolved it for us!
Daniel Ratliff | http://www.PotentEngineer.com
Tuesday, November 11, 2014 12:32 PM
We solved our problem. In the end we got the same problem for all virtual machines. All machines (Hyper-V and VMware) have two harddisk. The second one were always a SCSI-HDD. After we changed from SCSI to IDE for 2nd HDD, it worked.
We dont know why it isnt working if the 2nd HDD is a SCSI one.