Ошибка 80070002 sccm

In this post, I will show you how to fix SCCM task sequence failed with error code 0x80070002. There are multiple solutions to fix the task sequence error 0x80070002.

The Task Sequence error code 0x80070002 is the most common error that you see during operating system deployment.

Whenever a task sequence fails, it fails with an error code. This error code is critical in determining why the task sequence failed and has solutions associated with it.

The SMSTS.log file plays an important role in troubleshooting the task sequence failures. For example, when a SCCM task sequence fails with error code 0x80070002, the smsts.log file contains the reasons why the task sequence failed along with additional errors.

The location of SMSTS.log file changes during the SCCM OSD. So ensure you know the location of smsts.log file during OSD. You can open the SMSTS.log file using CMTrace log file viewer or ConfigMgr log file viewer tools.

You encounter task sequence error code 0x80070002 during “Apply Operating System” step of SCCM Task Sequence. When a task sequence fails with error code 0x8007002, you see the following details.

ERROR: Task Sequence Failed with the error code 0x80070002. For more information, contact your system administrator or helpdesk operator.

The error code 0x80070002 means the system cannot find the file specified. It’s regarded as a network error during the OSD where the necessary files are not accessible by the computer where the operating system is being deployed. It can also mean that the distribution point cannot be reached by a client computer.

SCCM Task Sequence Failed with Error Code 0x80070002
SCCM Task Sequence Failed with Error Code 0x80070002

To fix the error code 0x80070002, you must define the network access account in SCCM. The Network Access account is used only for accessing the content and not for running the task sequence.

The network access account should have the minimum appropriate permissions on operating system deployment content it needs to access. This account is important because the computer receiving the operating system does not have a security context it can use to access content on the network.

To configure the Network Access Account in SCCM console :-

  1. Launch the SCCM console.
  2. Click on Administration > Overview > Site Configuration > Sites.
  3. On the top ribbon click Configure Site Components and select Software Distribution.
Task Sequence Failed with the Error Code 0x80070002

Click on the tab Network Access Account, choose Specify the account that accesses network locations (by default the option is set to Use the computer account of Configuration Manager client). Click on the orange icon and add the user account that enough permissions to access the content which is required while deploying Operating System.

Task Sequence Failed with the Error Code 0x80070002
Configure the Network Access Account in SCCM console

Avatar photo

Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.

  • Remove From My Forums
  • Вопрос

  • Добрый день,  коллеги

    Помогите решить проблему

    При развертывании WIN 7 на Wmwarе

    скрины

Ответы

  • либо нужно учетную запись обладающую правами к сайту выставить в «сайты, точка распр. прог. обеспеч.», либо разрешить анонимный доступ в настройка точки распространения.


    Идти туда, где не ждут, Атаковать там, где не подготовились.

    • Предложено в качестве ответа

      2 декабря 2013 г. 7:29

    • Помечено в качестве ответа
      Petko KrushevMicrosoft contingent staff, Moderator
      2 декабря 2013 г. 7:29

  • Remove From My Forums
  • Question

  • Hello All.

    We’re using SCCM 2012 R2 SP1. SCCM Client installation is getting failed again on a Windows 7 SP1 desktop.

    ccmsetup.log are as below:

    MSI: Setup failed due to unexpected circumstances. The error code is 80070002

    File C:\Windows\ccmsetup\{8971B736-FB0A-4D07-AE81-82D40BBCD630}\client.msi installation failed. Error text: ExitCode: 1603
    Action: CcmFixupServiceConfigInit.
    ErrorMessages: 

    Setup failed due to unexpected circumstances. The error code is 80070002

    Client.msi.log are as below:

    MSI (s) (84:10) [12:44:36:945]: Product: Configuration Manager Client — Installation operation failed.

    MSI (s) (84:10) [12:44:36:946]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

    I’ve tried rebuilding the WMI repository (as described in the article http://blogs.catapultsystems.com/javery/archive/2009/07/01/sccm-client-installation-error-80041001), but again same error.

    Please help and advise.

    Many thanks in anticipation.

    Regards,

    Hasan Bin Hasib

    • Edited by

      Tuesday, September 29, 2015 8:12 AM

Answers

  • Rebuilding WMI is not a cure all and is not harmless like a reboot; i.e., it doesn’t make sense to blindly rebuild WMI every time you have an error.

    Based on the log snippet above, the custom action CcmFixupServiceConfigInit is failing. I don’t have intimate knowledge of this custom action but based upon its name, it is attempting to manipulate some service in some way although the exact error is «Failed
    to cache service configuration». Also, error code 2 = file not found.

    Putting all of this together leads me to believe that the system is locked down or the anti-virus product in use is preventing the action. You need to review the logs for your AV product as well as the event viewer to see if you can find any correlating
    activity. ProcMon may also be helpful here in discovering what exactly is going on.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by
      Kannan CS
      Wednesday, September 30, 2015 9:02 AM
    • Marked as answer by
      Xin GuoMicrosoft contingent staff
      Thursday, October 8, 2015 6:12 AM

Let’s discuss the options to FIX SCCM App Deployment Errors 0x80070002 and 0x87d01106. Most of the SCCM app deployment errors are generic ones, and You might need to dig this deeper to find the actual issue for the error and fix it.

This post is here to help you understand how to troubleshoot the SCCM app deployment issues and find a solution or fix for the same. These are SCCM client-side errors and can be because by several issues. Each of these issues and fixes can be unique to each other.

The bottom line is to fix the issue in a supported way without impacting the end-user experience. I’ve seen the errors 0x80070002 and 0x87d01106 when I tried to deploy a command line using the SCCM package (classic) workflow.

The ConfigMgr App deployment error could also happen for SCCM application model scenarios. Both SCCM Application Model & Classic Package deployment issues should be handled separately. This means you need to look into a different set of logs for each scenario.

Patch My PC

Nitin created two excellent blog posts to give us a walkthrough of the SCCM Application Model process. The first blog post covers the server-side background process workflow of the SCCM application model, and 2nd blog post covers the client-side of the SCCM application model.

Software Center Error Unable to Make Changes to Your Software

  • The 1st step in SCCM App Deployment troubleshooting is to check the Software Center and get the error message or error code.

The software center error message “Unable to Make Changes to Your Software.” is one of the most common error messages. But it doesn’t mean that all the issues can be solved with one particular fix.

You can click on the Failed link from the software center Status to get more details of the error. Click on more information to get the actual error code. I have shared two error codes from the Status: Failed link on Software Center in this post.

The first example is the error I received is 0x642(1602). It’s very easy to troubleshoot the error 0x642(1602) and find its cause. We will see the reason for the error 0x642(1602) below.

Adaptiva

Software Center Error Unable to Make Changes to Your Software FIX SCCM App Deployment Errors 0x80070002 0x87d01106
Software Center Error Unable to Make Changes to Your Software

The second error I received upon the failure of SCCM package installation was Error 0x80070002(-2147024894). You can find more details about the issue and fix it at the bottom side of the post. However, it’s important to understand how to troubleshoot SCCM app deployment issues and fix them.

FIX SCCM App Deployment Errors 0x80070002 0x87d01106
FIX SCCM App Deployment Errors 0x80070002 0x87d01106

Translate the Error Codes using CMTrace 0x642(1602) & 0x80070002(-2147024894)

  • The 2nd step is to translate the error codes into human understandable language.

The translate SCCM app deployment error code helps you understand the error or issue much better. Some error translations are super useful and resolve the issue then and there itself. The error code 0x642(1602) is one example of this scenario.

I prefer to use CMTrace (log reader tool for SCCM) to translate the error codes. Open the CMTrace tool from any of the following locations.

  • Site Server 
    • Drive Letter:\Program Files\Microsoft Configuration Manager\tools\CMTrace.exe
    • Drive Letter:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\Tools\CMTrace.exe
  • SCCM Client -> C:\Windows\CCM\CMTrace.exe

You need to click on the Tools menu and Select Error Lookup. Enter the error code in the search box and click on the Lookup button. Always try to remove the bracket part of the error code before entering it into the search box.

For example: If the error code is 0x642(1602), try to enter only 0x642 to get better results. As per the CMTrace error database, the translation or the meaning of error 0x642 is User canceled installation. Ignore the typos in the translations.

The meaning of the error 0x642(1602) is User canceled installation. So you know the issue, and you don’t have to troubleshoot further on this issue.

Translate the Error Codes using CMTrace 0x642(1602) & 0x80070002(-2147024894)
Translate the Error Codes using CMTrace 0x642(1602) & 0x80070002(-2147024894)

Let’s translate SCCM application deployment error 0x80070002(-2147024894). As mentioned above, you need to use the first part of the error code before the brackets.

I have taken the first part of the error code 0x80070002 and searched against the CMTrace database to find some meaning full error message than just numbers. The error translates to “The system cannot find the file specified.”

Translate the Error Codes using CMTrace 0x642(1602) & 0x80070002(-2147024894)
Translate the Error Codes using CMTrace 0x642(1602) & 0x80070002(-2147024894)

Check SCCM Application Deployment Log FilesError Code 0x87d01106

  • The 3rd Step in the SCCM App deployment troubleshooting is to check the relevant SCCM App deployment-related log files.

The SCCM package deployment error 0x80070002(-2147024894) translates to “The system cannot find the file specified.” This error message didn’t point to any specific issue straightaways, and that is the reason to look at the SCCM log files.

  • Read More: SCCM Application Model Client-side log file and troubleshooting.

I used SCCM Packages (classic) workflow to create and deploy a command-line onto Windows 11 devices, and it failed with the following error 0x80070002(-2147024894). Since this is SCCM Package deployment, you need to look into the execmgr.log on SCCM Client -> C:\Windows\CCM\Logs folder.

Check SCCM Application Deployment Log Files - Error Code 0x87d01106
Check SCCM Application Deployment Log Files – Error Code 0x87d01106

As mentioned above, I have checked the log file called execmgr.log to dig more info; the issue appeared in the Software Center – Unable to Make Changes to Your Software. I have noticed 3 important error messages in from execmgr.log file.

  • Invalid executable file Winget.
  • EnterRsRuningState failed to run script Winget.
  • Fatal Error 0x87d01106. This program will not retry.

Executing program Winget Install –silent –id Adobe.Acrobat.Reader.64-bit in User context
Invalid executable file Winget
EnterRsRuningState failed to run script Winget Install –silent –id Adobe.Acrobat.Reader.64-bit 0x87d01106
Fatal error 0x87d01106 encountered for program Install Adobe Acrobat using Winget. This program will not retry.

Check SCCM Application Deployment Log Files - Error Code 0x87d01106
Check SCCM Application Deployment Log Files – Error Code 0x87d01106

Understanding the Errors in the LogSCCM App Deployment Error 0x87d01106

  • The 4th step in the troubleshooting of SCCM app deployment errors is understanding the errors in the log file.

I have highlighted some of the errors (3) from the log file, and the issue is 90% clear for me from those errors shared in the above section. As explained above, there is another error code 0x87d01106 in the log file that you need to translate using the CMTrace method.

The error code 0x87d01106 is translated as “Failed to verify the executable file is valid or construct the associated command line.” The Source of the error code is from the SCCM error database.

Understanding the Errors in the Log - SCCM App Deployment Error 0x87d01106
Understanding the Errors in the Log – SCCM App Deployment Error 0x87d01106

The error code translation and another error “Invalid executable file Winget.” from the execmgr.log confirmed that the SCCM classic package can’t run the WinGet command-line tool from user context in a hidden mode. I decided to have a look at the SCCM package program settings.

Program settings that caused SCCM App Deployment Error 0x87d01106:
• Name: Install Adobe Acrobat using Winget
• Command line: Winget Install –silent –id Adobe.Acrobat.Reader.64-bit
• Start in:
• Run: Hidden
• Run mode: Run with user’s rights
• Program can run: Only when a user is logged on
• Allow users to view and interact with the program installation
• Drive mode: Runs with UNC name

Understanding the Errors in the Log - SCCM App Deployment Error 0x87d01106
Understanding the Errors in the Log – SCCM App Deployment Error 0x87d01106

Let’s check how to FIX SCCM App Deployment Errors 0x80070002 and 0x87d01106. I decided to make a PowerShell script with the command line used in the above program. I have created a .ps1 file and distributed the content to all the required Distribution Points.

  • Read More details about .ps1 script deployment Guide -> Install Uninstall Apps From Windows Package Manager Using WinGet Tool And SCCM

The SCCM app deployment issue with error codes 0x80070002 and 0x87d01106 got fixed. The log snippets from the execmgr.log file confirmed the same. The Execution is complete for the program Install Adobe Acrobat using Winget.

  • Script for Package: MEM00056, Program: Install Adobe Acrobat using Winget succeeded with exit code 0
  • Raised Program Success Event for Ad: MEM20025, Package: MEM00056, Program: Install Adobe Acrobat using Winget
  • Execution is complete for the program Install Adobe Acrobat using Winget. The exit code is 0, the execution status is Success.
FIX SCCM App Deployment Errors 0x80070002 0x87d01106
FIX SCCM App Deployment Errors 0x80070002 0x87d01106

You can check the results in the Software Center to confirm the successful installation of the same application that is deployed using the Winget command line. The status is installed!

FIX SCCM App Deployment Errors 0x80070002 0x87d01106
FIX SCCM App Deployment Errors 0x80070002 0x87d01106

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

Развернул недавно тестовую среду, настроил OSD для тестирования моей уже ставшей «любимой» Windows XP. Начинаю загрузку по PXE на тестовой виртуалке: полился загрузочный образ Windows PE, загружается, выбираю Task Sequence и на шаге Apply operating system получаю ошибку 0x80070002.

Лезу в лог и понимаю, что оно тупо не получает доступ до контента. Иду в настройки сайт-сервера посмотреть на Network Access Account — задан ли он у меня. Вижу что не задан, задаю — все отлично, ошибка ушла.

Network Access Account нужен для доступа к контенту на Distribution Point, если машина не входит в домен (рабочая группа), либо находится в untrusted domain, а так же во время OSD.

Тут же вспоминаю, что относительно недавно сунулся на боевом SCCM и увидел, что Network Access Account не задан, хотя вроде задавал его. Еще удивился — как это доступ до контента получается. Дальше выяснилось, что в свойствах Distribution Point есть «чудо» галочка — Allow clients to connect anonymously.

Не сказать, что с помощью этой галки можно что-то испортить кулхацкерами, но все же — потенциальный изъян в безопасности. Кто угодно сможет слить контент с самой DP без каких-либо проблем. 

Вывод: галочку не юзать, добавлять Network Access Account.

Понравилась статья? Поделить с друзьями:
  • Ошибка 80070002 lost planet 2 win 10
  • Ошибка 800 l2tp vpn
  • Ошибка 80070001 при установке
  • Ошибка 8002ae04 на ps3 hen
  • Ошибка 80029946 на ps3