Код ошибки 2147024894 0x80070002

Hi

I have Excel 365 W10 HP laptop. I have an excel file with lots of Macros in it. One single macros will not work, the error is Run-time error ‘-2147024894 (80070002)’ Automation error. The system cannot find the file specified. The macros has been tried by multiple people including a different laptop I own and it works perfectly. The debug stops on this line of code 

myShell.Run FolderName & FileName

The code it to double click on a listbox in a userform to open jpg and pdf files which are in the same folder as the excel file. The entire code for the macros is 

Private Sub lstDatabase_DblClick(ByVal Cancel As MSForms.ReturnBoolean)

    Dim FolderName As String, FileName As String
    Dim myShell As WshShell
    
'change folder path to database if required
    FolderName = ThisWorkbook.Path & ""
    
    FileName = Me.lstDatabase.Value

    'On Error GoTo myerror
    
    If Not Dir(FolderName & FileName, vbNormal) = vbNullString Then
        Set myShell = New WshShell
        myShell.Run FolderName & FileName
    Else
        Err.Raise 53
    End If

'report errors
myerror:
    If Err <> 0 Then MsgBox (Error(Err)), 48, "Error"
    Set myShell = Nothing
End Sub

 Any help is appreciated.

Hi

I try to deploy via SCCM the last office 365 Update — Update client office 365 monthly channel version 1708 for edition

x86 (build 8067.2157) and it’ failed with error 0x80070002(-2147024894)

in the UpdatesHandler.log i have this error: 

State Transition — Update 53a7273d-c137-425a-b18d-bd7f6dfd7098, State = COMPLETE_FAILED

CAS failed to download update (53a7273d-c137-425a-b18d-bd7f6dfd7098). Error = 0x80070002. Releasing content request.

Bundle update (016ef8f6-a24f-48c8-8b12-1056b4233df7) received failure (0x80070002) from a child update (53a7273d-c137-425a-b18d-bd7f6dfd7098)
UpdatesHandler 19/10/2017 16:44:29
7040 (0x1B80)

Bundle update (016ef8f6-a24f-48c8-8b12-1056b4233df7) received failure (0x80070002) from a child update (53a7273d-c137-425a-b18d-bd7f6dfd7098)

Update (016ef8f6-a24f-48c8-8b12-1056b4233df7) already in failed state. No new message will be raised.

On the DP the content is OK.

I delete all the update et downloaded again but no effect.

Could you please Help me.

Thanks

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.

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.

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.

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 FilesMicrosoft Configuration ManagertoolsCMTrace.exe
  • Drive Letter:Program FilesMicrosoft Configuration Managercd.latestSMSSETUPToolsCMTrace.exe
• SCCM Client -> C:WindowsCCMCMTrace.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.

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

Check SCCM Application Deployment Log Files – Error 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:WindowsCCMLogs folder.

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.

Understanding the Errors in the Log – SCCM 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.

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

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.

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!

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.

У меня как-то раз возникли проблемы с WinRM на двух серверах.

1. SETSPN
На одном проблема была в том, что SPN записи HTTP/<имя сервера> были зарегистрирована для какой-то «левой» учётной записи пользователя.

Нашёл эти записи командой
setspn -F -Q */<имя сервера>

Затем удалил их командами
setspn -D http/<имя сервера>.<имя домена>  <имя домена><левая учётная запись>
setspn -D http/<имя сервера>  <имя домена><левая учётная запись>

Затем enable-psremoting -force выполнилась успешно.

2. LANGUAGE PACK
А на втором сервере была хитрая проблема якобы с фаерволлом Unable to check the status of the firewall, перерыл кучу сайтов, а решение обнаружил интуитивно основываясь на ответе по поводу установленного Language Pack.

WinRm QuickConfig
WinRM service is already running on this machine.
WSManFault
    Message
        ProviderFault
            WSManFault
                Message = Unable to check the status of the firewall.

Error number:  -2147024894 0x80070002
The system cannot find the file specified.

В ответе было написно, что данная ошибка лечится удалением дополнительного Language Pack.
Но я поступил иначе. У меня Английская операционка с дополнительным русским language pack. Я просто изменил язык интерфейса на Русский.
Панель управления, Язык и региональные стандарты, Языки и клавиатуры изменил язык интерфейса с англиского на русский.
Выполнил logoff и вошёл снова. Открыл PowerShell и повторил WinRm QuickConfig

PS C:Windowssystem32> winrm qc
Служба WinRM уже настроена на прием запросов на компьютере.
Служба WinRM не настроена на разрешение удаленного управления компьютером.
Необходимо внести следующие изменения:

Создайте прослушиватель WinRM на HTTP://* для приема запросов WS-Man на любом из IP-адресов этого компьютера.

Выполнить изменения [y/n]? y

Служба WinRM обновлена для удаленного управления.

Создан прослушиватель WinRM на HTTP://* для приема запросов WS-Man на любом из IP-адресов этого компьютера.

Выполнилось успешно, но всё же не достаточно.

Появилась ошибка Access Denied при попытке выполнить команды удалённо на этом сервере с другого компа.

New-PSSession : [<имя сервера>] Connecting to remote server <имя сервера> failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

Тогда я повторил Enable-PsRemoting

PS C:Windowssystem32> Enable-PsRemoting

Быстрая настройка WinRM
Запуск команды «Set-WSManQuickConfig» для включения на данном компьютере удаленного управления с помощью службы WinRM.
 Необходимые действия.
    1. Запуск или перезапуск (если уже запущена) службы WinRM.
    2. Изменение типа службы WinRM на «автозапуск».
    3. Создание прослушивателя для приема запросов на любом IP-адресе.
    4. Настройка исключений брандмауэра для трафика службы WS-Management (только для протокола http).

Продолжить?
[Y] Да — Y  [A] Да для всех — A  [N] Нет — N  [L] Нет для всех — L  [S] Приостановить — S  [?] Справка
(значением по умолчанию является «Y»):a
Служба WinRM уже настроена на прием запросов на компьютере.
Служба WinRM уже настроена на разрешение удаленного управления компьютером.

Подтверждение
Вы действительно хотите выполнить это действие?
Выполнение операции «Регистрация конфигурации сеанса» над целевым объектом «Конфигурация сеанса
«Microsoft.PowerShell32» не найдена. Будет выполнена команда «Register-PSSessionConfiguration Microsoft.PowerShell32
-processorarchitecture x86 -force» для создания конфигурации сеанса «Microsoft.PowerShell32». Служба WinRM будет
перезапущена.».
[Y] Да — Y  [A] Да для всех — A  [N] Нет — N  [L] Нет для всех — L  [S] Приостановить — S  [?] Справка
(значением по умолчанию является «Y»):a

После этого WinRM на этом сервере заработал как надо.