Jump to content


SCCMNoobster

OSD CCM Client causes error

Recommended Posts

Hi,

 

i have a OSD set up for my travel mate 6594 machine that currently only install Windows 8.1 32bit and the SCCM client. This works with no problems however when I try changing it to a 64bit OS ( ive tried win8.1, 8 and 7) after applying the image and when it tried to install the SCCM client it crashes saying OSDSetupHook.exe - Aplication Error the error says The instruction at *number* referenced memory at *numbers*. the memory could not be read. I have installed a 64bit os manually on this machine previously without problems.

 

My server is 2012 and SCCM is 2012 sp1 v5.07804.1400

 

Thanks

 

Mike

Share this post


Link to post
Share on other sites

You're missing some drivers, the message isn't very clear, but even ones which you might not think are relevant like AMT need to be present. I've gotten strange errors like this before and it has always been missing drivers. Go back and make sure to separate your 32 from 64 bit drivers and make sure to apply them to their own categories etc... double down on your drivers IMHO.

Share this post


Link to post
Share on other sites

Im not really installing any drivers with the OSD as windows 8.1 has all the drivers for the machine. I do however think it is something to do with the boot files after looking through the logs it doesn't seem that its the sccm client but the setting up windows part that is the issue

 

Process completed with exit code 3221225477 OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
exitCode, HRESULT=c0000005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,635) OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
Configure hook failed with error code (C0000005). OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
this->configureGina(this->sysDir), HRESULT=c0000005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,780) OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
this->installSetupHook(), HRESULT=c0000005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,452) OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
Failed to install setup hook (C0000005) OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
setup.run(), HRESULT=c0000005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1668) OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
Exiting with code 0xC0000005 OSDSetupWindows 3/27/2014 2:34:46 PM 1152 (0x0480)
Process completed with exit code 3221225477 TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
!--------------------------------------------------------------------------------------------! TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Could not find CCM install folder. Don't use ccmerrors.dll TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Failed to run the action: Setup Windows and ConfigMgr.
Unknown error (Error: C0000005; Source: Unknown) TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
MP server http://chicken.stmarks.wa.edu.au. Ports 80,443. CRL=false. TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Setting authenticator TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Set authenticator in transport TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Sending StatusMessage TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Setting message signatures. TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Setting the authenticator. TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
CLibSMSMessageWinHttpTransport::Send: URL: chicken.stmarks.wa.edu.au:80 CCM_POST /ccm_system/request TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Request was succesful. TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Set a global environment variable _SMSTSLastActionRetCode=-1073741819 TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Clear local default environment TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Let the parent group (Setup Operating System) decides whether to continue execution TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
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 3/27/2014 2:34:46 PM 1092 (0x0444)
Could not find CCM install folder. Don't use ccmerrors.dll TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
Failed to run the last action: Setup Windows and ConfigMgr. Execution of task sequence failed.
Unknown error (Error: C0000005; Source: Unknown) TSManager 3/27/2014 2:34:46 PM 1092 (0x0444)
I have 8 not 8.1 adk installed do I need to add the winpe5 boot files into a winpe4 boot image?

Share this post


Link to post
Share on other sites

I forget which ADK I'm using, but the only installation is c:\program files (x86)\Windows Kits\8.0 so I am 95% sure I have the win 8.0 ADK. And I have no problems deploying win x64 8.1. I'm suprised you aren't injecting any drivers; that's always been my issue. I would say make sure you have the "F8" option turned on and do a number of checks during your imaging, first make sure you have network connectivity i.e. from the F8 command prompt do pings. Also do diskpart and confirm that the c:\ drive is being written properly. At a minimum you should make a driver package IMHO and apply that before installing your CM client. It's typically the chipset or some inane driver that crashes the TS when I see a "memory can't be written" kind of thing.

 

Are you using a 64 bit boot disk? Are you rebooting after applying the wim "to operating system" i.e. not to the boot disk?

 

Can you post your full SMSTS.log (preferrably an attachment not inline? Also I would personally pull out your domain before posting.

 

Also your model is fairly old, it might be a matter of compatibility straight up... i.e. see below, they don't offer win 8 or 8.1 drivers. I had a lot of problems with drivers moving to 8.1 in a few cases. You can probably get the latest Chipset and AHCI drivers from the manufacturers directly though, 90% of the win7 drivers may work, but you should definetly go through and make sure when you import them they have "win 8.1" capable checked off in the "applicability" section.

post-6999-0-82755200-1396013608_thumb.png

post-6999-0-98860800-1396013880_thumb.png

Share this post


Link to post
Share on other sites

Something I have noticed, on the machines that do come up with the OSDSetupHook.exe error once i reboot after the ts fails windows has been applyed properly and it has joined the domain/setup local password etc

 

all the drivers have been found by windows and he machine works.

 

I have also tried it on 2 other 64 bit machines with the same issue. could it be something to do with my 64bit boot image? I am going to try to make another and see if that helps.

Share this post


Link to post
Share on other sites

OK I think im getting somewhere. I have followed this guide http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/ to add winpe5 to my boot image and I am no longer getting an application error. It still doesn't work but it is now working on my new 64 bit machines.

 

From reading some other forums I think what is happening is that when windows is applyed the network is dropped because it doesn't have appropriate drivers and so it cannot find the package and fails

 

he is an exert from the smsts.log

 

Failed to resolve package source "SM100003" OSDSetupHook 4/1/2014 2:48:02 PM 1620 (0x0654)
Exiting ConfigureEx: 0x80091007 OSDSetupHook 4/1/2014 2:48:02 PM 1620 (0x0654)
BaseSetupHook::configure(sWindowsDir), HRESULT=80091007 (e:\qfe\nts\sms\client\osdeployment\osdgina\osdsetuphook.cpp,292) OSDSetupHook 4/1/2014 2:48:02 PM 1620 (0x0654)
Failed to configure OSD setup hook (0x80091007) OSDSetupHook 4/1/2014 2:48:02 PM 1620 (0x0654)
Process completed with exit code 2148077575 OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
exitCode, HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,635) OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
Configure hook failed with error code (80091007). OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
this->configureGina(this->sysDir), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,780) OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
this->installSetupHook(), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,452) OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
Failed to install setup hook (80091007) OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
setup.run(), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1668) OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
Exiting with code 0x80091007 OSDSetupWindows 4/1/2014 2:48:02 PM 888 (0x0378)
Process completed with exit code 2148077575 TSManager 4/1/2014 2:48:02 PM 340 (0x0154)
I'm going to try to insert the NIC drivers to the boot image.
Does this sound like im on the right track or am I going off in a tangent?

Share this post


Link to post
Share on other sites

You should test that theory by adding "F8" command prompt to your boot image. So hit F8 and do an ipconfig and see if you can ping 4.2.2.2 etc... Go into your boot image's options and there is a check box for adding "F8 or command prompt testing" etc... very useful.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.