PENDING Applications show that no content is specified, but only on some clients

[bhethcote]

I have an application (.MSI) that is deployed to all WIn10 workstations n the domain. It installs successfully on most, but on some it fails because it can't find the MSI file.

Successful Install - you can see where the content that's in the ccmcache folder is identified
+++ Starting Install enforcement for App DT "Computrace - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_709A7EEC-AB5F-42C2-A373-22D2B35929E4/DeploymentType_d45e1ad8-7bff-413b-8d43-c0befa7fd60d, Revision - 2, ContentPath - C:\WINDOWS\ccmcache\c, Execution Context - System
Performing detection of app deployment type Computrace - Windows Installer (*.msi file)(ScopeId_709A7EEC-AB5F-42C2-A373-22D2B35929E4/DeploymentType_d45e1ad8-7bff-413b-8d43-c0befa7fd60d, revision 2) for system.
+++ MSI application not discovered [MSI Product Code: {B3BAEAC5-08CE-4D3E-8D5D-05E6505546CE}, MSI Product version: ]
App enforcement environment:
Context: Machine
Command line: msiexec.exe /i "Computrace.msi" /qn /l*v "%windir%\CCM\Logs\Install_Absolute_8.0.978.log"
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\WINDOWS\ccmcache\c
Working directory:
Prepared working directory: C:\WINDOWS\ccmcache\c
Found executable file msiexec.exe with complete path C:\WINDOWS\system32\msiexec.exe
Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i "Computrace.msi" /qn /l*v "C:\WINDOWS\CCM\Logs\Install_Absolute_8.0.978.log" /qn
Valid MSI Package path = C:\WINDOWS\ccmcache\c\Computrace.msi
Advertising MSI package [C:\WINDOWS\ccmcache\c\Computrace.msi] to the system.
Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /i "Computrace.msi" /qn /l*v "C:\WINDOWS\CCM\Logs\Install_Absolute_8.0.978.log" /qn with system context
Working directory C:\WINDOWS\ccmcache\c
Post install behavior is BasedOnExitCode
Waiting for process 5440 to finish. Timeout = 120 minutes.
Process 5440 terminated with exitcode: 0
Looking for exit code 0 in exit codes table...
Matched exit code 0 to a Success entry in exit codes table.

Unsuccessful Install - for some reason it's not able to identify that there is content specified and the content actually resides in the ccmcache folder and sets the working directory to C:\Windows\System32 rather than C:\Windows\ccmcache\c.

+++ Starting Install enforcement for App DT "Computrace - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_709A7EEC-AB5F-42C2-A373-22D2B35929E4/DeploymentType_d45e1ad8-7bff-413b-8d43-c0befa7fd60d, Revision - 1, ContentPath - , Execution Context - System
The content path is not specified for DeploymentType ScopeId_709A7EEC-AB5F-42C2-A373-22D2B35929E4/DeploymentType_d45e1ad8-7bff-413b-8d43-c0befa7fd60d. Content is assumed to be locally available.
Performing detection of app deployment type Computrace - Windows Installer (*.msi file)(ScopeId_709A7EEC-AB5F-42C2-A373-22D2B35929E4/DeploymentType_d45e1ad8-7bff-413b-8d43-c0befa7fd60d, revision 1) for system.
+++ MSI application not discovered [MSI Product Code: {B3BAEAC5-08CE-4D3E-8D5D-05E6505546CE}, MSI Product version: ]
App enforcement environment:
Context: Machine
Command line: msiexec.exe /i "Computrace.msi" /qn /l*v "%windir%\CCM\Logs\Install_Absolute_8.0.978.log"
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path:
Working directory:
Prepared working directory: C:\Windows\system32
Prepared command line: "C:\Windows\system32\msiexec.exe" /i "Computrace.msi" /qn /l*v "C:\Windows\CCM\Logs\Install_Absolute_8.0.978.log" /qn
Unable to locate or validate MSI package Computrace.msi
Package file in the commandline is not valid or not accessible
CMsiHandler::EnforceApp failed (0x87d01106).
AppProvider::EnforceApp - Failed to invoke EnforceApp on Application handler(0x87d01106).
CommenceEnforcement failed with error 0x87d01106.
Method CommenceEnforcement failed with error code 87D01106
++++++ Failed to enforce app. Error 0x87d01106. ++++++

I've kind of hit a brick wall here and if anyone has any ideas, I'd be happy to hear them. I've tried updating the content on the DPs - no effect.

Thanks - BH

 

[Garth]

Have you confirmed that the MSI exist on that client? Have you confirmed that the MSI is valid on that client? Have you run this exact command line on this client? Have you manually copied the MSI to this client and run the command line?

 

[bhethcote]

Have you confirmed that the MSI exist on that client? Have you confirmed that the MSI is valid on that client? Have you run this exact command line on this client? Have you manually copied the MSI to this client and run the command line?

Hey Garth,
Thanks - Yes, the MSI in the ccmcache\<x> folder.
If we execute the command line (from the deployment type) in CMD (as admin), it installs fine.
The install works fine using the local MSI, a copied MSI, etc.
It just seems like the execution does not recognize the fact that the content is in the ccmcache folder, sets the working directory to C:\Windows\System32, then can't find the MSI.

 

[FabioBrito2k]

Hello!
I'm facing the same issue, did you find out a solution or root cause?
I'm reinstalling the MECM agent as a workarround but feel that this is not the best way to fix it.

Some backgound information about my enviroment:
~80k clients WW, currently I can see ~100 devices affected (random packages)

Any suggestion would be great

 

[ADecker]

Also seeing this exact issue. Any information?

 

[Garth]

Also seeing this exact issue. Any information?

Exactly what troubleshooting have you done?

 

[ADecker]

At this point I feel like I've done anything I can think of that seems relevant; cleared the ccmcache, ran every client action, re-deployed the application to the device...

In the AppEnforce log I'm seeing a few strange things:

Content path:
Working directory:
Prepared working directory: C:\WINDOWS\system32
Adding /qn to the commandline for msi execution since it's a system dt that doesn't require user interaction.
Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i "PackageName.msi" <package switches> /qn
Unable to locate or validate MSI package PackageName.msi
Package file in the commandline is not valid or not accessible

Where for a working deployment the "Content path" points to the ccmcache folder it's been downloaded into:

Content path: C:\WINDOWS\ccmcache\1l

Additionally, instead of the "unable to locate" message, it will log:

Valid MSI Package path = C:\WINDOWS\ccmcache\1l\PackageName.msi
Advertising MSI package [C:\WINDOWS\ccmcache\1l\PackageName.msi] to the system.

 

[Garth]

Did you manually try to install the MSI from the ConfigMgr Cache? Did you validate on the device the the MSI is validate.

 

[Prajwal Desai]

Either that msi file is corrupt or the system doesn't allow it's installation. Chances are that the security software on the client doesn't allow the installation.

 

[ADecker]

Interesting! This is a new AV deployment that we are rolling out. It worked on most machines, but perhaps the MSI was damaged during the download on this particular machine.

I didn't attempt to locate and run the MSI manually from the ccmcache folder, but our security team manually ran the installer themselves which of course worked. Since this was somewhat time sensitive and the machine in question no longer has the issue I'm not able to say anything definitive, but thanks for the discussion!