Jump to content


  • 0
djchow85

Task Sequencing Environment. Code 0x80220005. error

Question

Hi all,

 

I'm new to sccm 2012 but have been using and configuring it for just a month now

 

Today I had a new fleet of laptop and added drivers for the laptop that I was using which was a HP ProBook 6570b

 

Upon the imaging stage I get the following

 

Task Sequence: New computer win7 .... Code 0x80220005

 

The full log when found in the monitoring tab in SCCM is of follows

 

Description:

 

The task sequence execution engine failed executing the action (Apply Windows Settings) in the group (Install Operating System) with the error code 2149711877

Action output: entName, pszPath, pszValue ), HRESULT=80220005 (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,767)

this->SetValue( Specialize, XML::Shell::ComponentName, XML::Shell::ComputerName::Element, pszComputerName ), HRESULT=80220005 (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,883)

m_pImpl->SetComputerNameW(pszComputerName), HRESULT=80220005 (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,2183)

pAnswerFile->SetComputerNameW(sValue), HRESULT=80220005 (e:\nts_sccm_release\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,375)

ConfigureWinSettings(), HRESULT=80220005 (e:\nts_sccm_release\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,636)

Could not find CCM install folder. Don't use ccmerrors.dll

Exiting with return code 0x80220005

Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence.

Unknown error (Error: 80220005; Source: Unknown).

 

I have done the following and notes

  • product name of laptop = HP ProBook 6570b
  • WMIC query set to "SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%HP ProBook 6570b%"
  • above query works fine when testing
  • have also started from scratch, creating the driver packages and so forth

Some people have suggested to user 16 characters or lest for the naming convention but I'm unsure what they mean. Do they mean the product name of the device must be shorter, or when importing the device to SCCM and naming it shorter?

 

I'm really out of ideas and have spent quite a long time trying to figure this out. I've had success importing drivers for a HP desktop so I'm pretty stunned

 

:(

Share this post


Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0

I have now looked at the drivers for the laptop in software library and have noted that there are no CHIPSET drivers in there even though they were imported. Based on the documentation I follow, typically the files should end up in the DRIVERS tab and then I move them to the laptops/folder...

 

Wondering if this is the issue, trying to import them now as I type!

 

:(

Share this post


Link to post
Share on other sites

  • 0

In this case the task sequance fails duing the "Install Operating System" not during apply device drivers. So i would start at looking why that part fails.

 

Looks to me that you need to add the SATA Drivers for your new model into your winPE image.

Share this post


Link to post
Share on other sites

  • 0

16 characters specified in the computer name in the TS is over the limit for SCCM.

 

Command line: "osdwinsettings.exe" /config OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
Setting %SystemRoot% to "C:\WINDOWS" OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
Loading existing answer file "C:\WINDOWS\panther\unattend\unattend.xml" OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
Computer Name: MININT-XXXXXZ420 OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "amd64" OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
spItem->SetValue( var ), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\smiinterface.cpp,286) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
pSetupPass->setValue(m_spSettingsEngine, pszNamespace, pszPath, pszValue), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\smiinterface.cpp,1126) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
m_pSMIInterface->setValue( SetupPassValue[eSetupPass], pszComponentName, pszPath, pszValue ), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\xmlanswerfile.cpp,768) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
this->SetValue( Specialize, XML::Shell::ComponentName, XML::Shell::ComputerName::Element, pszComputerName ), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\xmlanswerfile.cpp,884) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
m_pImpl->SetComputerNameW(pszComputerName), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\xmlanswerfile.cpp,2184) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
pAnswerFile->SetComputerNameW(sValue), HRESULT=80220005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,376) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
ConfigureWinSettings(), HRESULT=80220005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,637) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence.
Unknown error (Error: 80220005; Source: Unknown) OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
Exiting with return code 0x80220005 OSDWinSettings 8/30/2013 5:19:11 PM 1628 (0x065C)
Process completed with exit code 2149711877 TSManager 8/30/2013 5:19:11 PM 976 (0x03D0)

 

Reduce The name and you will roll past this error.

  • Like 1

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
Answer this question...

×   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.