Superseding application does not install after uninstall of superseded application

Hi,

we created a new application for Reader DC and used supersedence to configure that old Reader X should be uninstalled before.
The Client detects that the old Version is installed, and also start uninstall, but shows in SoftwareCenter that the Update failed.

I already checked the logs, but it seems, that the Client did not try to start the Installation after successful uninstallation. When I retry Update, it runs without any error.

This is what AppEnforce.log says when Update starts:

+++ Starting Uninstall enforcement for App DT "Adobe Reader XI  MUI - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_a5c30492-9f84-4add-ba2c-a3bdda2573ae, Revision - 13, ContentPath - C:\WINDOWS\ccmcache\k, Execution Context - System AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    A user is logged on to the system. AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Performing detection of app deployment type Adobe Reader XI  MUI - Windows Installer (*.msi file)(ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_a5c30492-9f84-4add-ba2c-a3bdda2573ae, revision 13) for system. AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
+++ Discovered application [AppDT Id: ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_a5c30492-9f84-4add-ba2c-a3bdda2573ae, Revision: 13] AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    App enforcement environment:
 Context: Machine
 Command line: uninstall.vbs
 Allow user interaction: Yes
 UI mode: 1
 User token: null
 Session Id: 4294967295
 Content path: C:\WINDOWS\ccmcache\k
 Working directory:  AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Prepared working directory: C:\WINDOWS\ccmcache\k AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Prepared command line: "C:\WINDOWS\System32\wscript.exe" "C:\WINDOWS\ccmcache\k\uninstall.vbs" AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Executing Command line: "C:\WINDOWS\System32\wscript.exe" "C:\WINDOWS\ccmcache\k\uninstall.vbs" with user context AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Working directory C:\WINDOWS\ccmcache\k AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Post install behavior is BasedOnExitCode AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Waiting for process 2456 to finish.  Timeout = 90 minutes. AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Process 2456 terminated with exitcode: 0 AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Looking for exit code 0 in exit codes table... AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Matched exit code 0 to a Success entry in exit codes table. AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
    Performing detection of app deployment type Adobe Reader XI  MUI - Windows Installer (*.msi file)(ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_a5c30492-9f84-4add-ba2c-a3bdda2573ae, revision 13) for system. AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
+++ Discovered application [AppDT Id: ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_a5c30492-9f84-4add-ba2c-a3bdda2573ae, Revision: 13] AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
++++++ App enforcement completed (0 seconds) for App DT "Adobe Reader XI  MUI - Windows Installer (*.msi file)" [ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_a5c30492-9f84-4add-ba2c-a3bdda2573ae], Revision: 13, User SID: ] ++++++ AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)

When I retry Update, this is shown AppEnforce.log:

+++ Starting Install enforcement for App DT "Adobe Acrobat Reader DC MUI - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_8e351314-8f41-4f5c-be71-77cbc8b1b9ef, Revision - 18, ContentPath - C:\WINDOWS\ccmcache\l, Execution Context - System AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
    A user is logged on to the system. AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
    Performing detection of app deployment type Adobe Acrobat Reader DC MUI - Windows Installer (*.msi file)(ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_8e351314-8f41-4f5c-be71-77cbc8b1b9ef, revision 18) for system. AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
+++ Application not discovered. [AppDT Id: ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_8e351314-8f41-4f5c-be71-77cbc8b1b9ef, Revision: 18] AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
    App enforcement environment:
 Context: Machine
 Command line: msiexec /i AcroRead.msi TRANSFORMS=AcroRead.mst /q
 Allow user interaction: No
 UI mode: 1
 User token: null
 Session Id: 1
 Content path: C:\WINDOWS\ccmcache\l
 Working directory:  AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
    Prepared working directory: C:\WINDOWS\ccmcache\l AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
Found executable file msiexec with complete path C:\WINDOWS\system32\msiexec.exe AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
    Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i AcroRead.msi TRANSFORMS=AcroRead.mst /q /qn AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
Valid MSI Package path = C:\WINDOWS\ccmcache\l\AcroRead.msi AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
    Advertising MSI package [C:\WINDOWS\ccmcache\l\AcroRead.msi] to the system. AppEnforce 29.06.2015 15:23:44 4076 (0x0FEC)
    Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /i AcroRead.msi TRANSFORMS=AcroRead.mst /q /qn with user context AppEnforce 29.06.2015 15:23:45 4076 (0x0FEC)
    Working directory C:\WINDOWS\ccmcache\l AppEnforce 29.06.2015 15:23:45 4076 (0x0FEC)
    Post install behavior is BasedOnExitCode AppEnforce 29.06.2015 15:23:45 4076 (0x0FEC)
    Waiting for process 1216 to finish.  Timeout = 45 minutes. AppEnforce 29.06.2015 15:23:45 4076 (0x0FEC)
    Process 1216 terminated with exitcode: 0 AppEnforce 29.06.2015 15:24:46 4076 (0x0FEC)
    Looking for exit code 0 in exit codes table... AppEnforce 29.06.2015 15:24:46 4076 (0x0FEC)
    Matched exit code 0 to a Success entry in exit codes table. AppEnforce 29.06.2015 15:24:46 4076 (0x0FEC)
    Performing detection of app deployment type Adobe Acrobat Reader DC MUI - Windows Installer (*.msi file)(ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_8e351314-8f41-4f5c-be71-77cbc8b1b9ef, revision 18) for system. AppEnforce 29.06.2015 15:24:46 4076 (0x0FEC)
+++ Discovered application [AppDT Id: ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_8e351314-8f41-4f5c-be71-77cbc8b1b9ef, Revision: 18] AppEnforce 29.06.2015 15:24:46 4076 (0x0FEC)
++++++ App enforcement completed (61 seconds) for App DT "Adobe Acrobat Reader DC MUI - Windows Installer (*.msi file)" [ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_8e351314-8f41-4f5c-be71-77cbc8b1b9ef], Revision: 18, User SID: ] ++++++ AppEnforce 29.06.2015 15:24:46 4076 (0x0FEC)

What could be the reason that the update does not complete successfully at the first run?
We are using the supersedence Feature for many months now, but never had this problem before, and we do not have this problem with other applications.

Thanks.

June 29th, 2015 10:04am


    Prepared command line: "C:\WINDOWS\System32\wscript.exe" "C:\WINDOWS\ccmcache\k\uninstall.vbs" AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)
[...]
+++ Discovered application [AppDT Id: ScopeId_B69641AE-2270-4071-A8C1-26D98F176663/DeploymentType_a5c30492-9f84-4add-ba2c-a3bdda2573ae, Revision: 13] AppEnforce 29.06.2015 15:18:47 1240 (0x04D8)

The problem is that the uninstallation did not work as expected, because the application still is detected then. 
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 10:28am

Okay, I saw this, too. But why does it install when I retry? And when I run Application Deployment Eval. Cycle it also detects that the old Version is not installed.

I originally used the MSI code for detection, now I also tried to additionally query the registry, but without success.

June 29th, 2015 10:55am

It might be possible that uninstall.vbs does kickk things off asynchronous. 
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 10:58am

Yes you are right ... the vbs script runs the uninstall command but does not wait to complete. That's why SCCM also logs starting and finishing the script all within 1 second. I changed it, and now it works.
July 7th, 2015 11:29am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics