Hello,

I created an application to remove a software named "Meridium APM Framework" in our environment. The removal is successful in a few machines whereas it failed in a PC with status as "Past due - will be retried" in software center.

I tried re-running it again from the software center and it fails.

I checked the AppEnforce.log and noticed the correct command has been executed successfully and this is what I see.

<![LOG[    App enforcement environment:
 Context: User
 Command line: "RemoveMeridium.EXE" /S
 Allow user interaction: Yes
 UI mode: 1
 User token: not null
 Session Id: 1
 Content path: C:\Windows\ccmcache\82
 Working directory: ]LOG]!><time="09:46:59.644+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appcontext.cpp:85">
<![LOG[    Prepared working directory: C:\Windows\ccmcache\82]LOG]!><time="09:46:59.648+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appcontext.cpp:189">
<![LOG[    Prepared command line: "C:\Windows\ccmcache\82\RemoveMeridium.EXE" /S]LOG]!><time="09:46:59.653+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appcontext.cpp:338">
<![LOG[    Executing Command line: "C:\Windows\ccmcache\82\RemoveMeridium.EXE" /S with user context]LOG]!><time="09:46:59.655+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appexcnlib.cpp:205">
<![LOG[    Working directory C:\Windows\ccmcache\82]LOG]!><time="09:46:59.656+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appexcnlib.cpp:219">
<![LOG[    Post install behavior is BasedOnExitCode]LOG]!><time="09:46:59.664+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appcommon.cpp:1094">
<![LOG[    Waiting for process 6680 to finish.  Timeout = 120 minutes.]LOG]!><time="09:46:59.667+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appexcnlib.cpp:2015">
<![LOG[    Process 6680 terminated with exitcode: 0]LOG]!><time="09:47:02.107+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appexcnlib.cpp:2024">
<![LOG[    Looking for exit code 0 in exit codes table...]LOG]!><time="09:47:02.108+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appexcnlib.cpp:508">
<![LOG[    Matched exit code 0 to a Success entry in exit codes table.]LOG]!><time="09:47:02.109+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appexcnlib.cpp:587">
<![LOG[    Performing detection of app deployment type Remove Meridium Client(ScopeId_880F42C2-5370-4FEB-8493-F3A777B8825F/DeploymentType_0ca87e2b-62ea-4d22-9d43-365f46ec9be8, revision 7) for user.]LOG]!><time="09:47:02.116+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_880F42C2-5370-4FEB-8493-F3A777B8825F/DeploymentType_0ca87e2b-62ea-4d22-9d43-365f46ec9be8, Revision: 7]]LOG]!><time="09:47:02.136+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="localapphandler.cpp:291">
<![LOG[++++++ App enforcement completed (2 seconds) for App DT "Remove Meridium Client" [ScopeId_880F42C2-5370-4FEB-8493-F3A777B8825F/DeploymentType_0ca87e2b-62ea-4d22-9d43-365f46ec9be8], Revision: 7, User SID: S-1-5-21-73153925-784800294-903097961-1198] ++++++]LOG]!><time="09:47:02.137+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="appprovider.cpp:2448">

Please assist fixing this! I am more interested to know what is causing this failure.

"Application not discovered"

Your detection method is either not correct or is possibly not valid at the time that the exe is exiting.

• Edited by d4rkcell 18 hours 45 minutes ago

Thanks for the reply!

The same application worked on several other machines having the software which I wanted to uninstall.

Since this is a removal deployment, I didn't know how best I can set a detection method.. So I am creating a .txt file in "C:\Temp" folder at the end of the uninstall process. I am using this file to be detected under the detection rule. (I am not sure if this is a good practice)

This application is a script based installer which was packaged in SMS Installer.

• Edited by d4rkcell Thursday, July 02, 2015 1:02 PM

No, I am not using the Uninstall command line. Instead I am using the executable in the install command line which actually does the uninstall work.

Not sure if this will be of any help... The install behavior is set to run for user and this application is deployed to device collection...

Let me know if you need any more information to drill down the issue.

OK, that's backwards then but that's OK.

Have you checked to see if the txt file actually exists on the client?

No I did not.. I saw the application failed to install and the software was still present in the Programs and Features.. so I didn't even think of checking the txt file in the temp directory..

I don't have the user at office anymore to work with him, I can get the answer for your by next morning positively!

Is there anything else that we would require from the issue PC to check what went wrong?

Hi,

are your users are local admins? - with "...install behavior is set to run for user..." the exe will be started as the logged on user.

I would test the following:

- create a application for "Meridium APM Framework" including an installation command AND an uninstall command in the deployment type (installation for system)

- as detection method use something from the Software (should be removed on uninstall! e.g. uninstall registry key)

- deploy this application with action "Uninstall" to the client collection

Yes, the user is a local Administrator.

By the way, I appreciate your suggestion but this deployment has already been rolled out to production and I really can't invest time doing QA again and especially my customer will not be happy!! :( I can probably try this in my lab and would be interested in knowing how it works.

I would be grateful if you can help troubleshoot to fix the issue. Or is this something that can't be fixed at all without changing the application?

 The removal is successful in a few machines whereas it failed in a PC with status as "Past due - will be retried" in software center.

<![LOG[    App enforcement environment:
 Context: User
 Command line: "RemoveMeridium.EXE" /S

<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_880F42C2-5370-4FEB-8493-F3A777B8825F/DeploymentType_0ca87e2b-62ea-4d22-9d43-365f46ec9be8, Revision: 7]]LOG]!><time="09:47:02.136+300" date="07-01-2015" component="AppEnforce" context="" type="1" thread="14068" file="localapphandler.cpp:291">

So I am creating a .txt file in "C:\Temp" folder

Does the text file exist on that machine? Obviously not, because it says "application not discovered". 

Why did you use an install deployment to uninstall something? There are also uninstall deployments available (where there is no need to create txt files in order to detect if an uninstallation succeeded). 

I agree, and that sounds wise... I don't know how we came up with the idea to use an install script to perform an uninstallation.. May be we ran out of brain cells during the development...

So using an uninstall command line is the best approach you suggest? Isn't there any way to fix the issue for that one person?

but i am interested here to know what exactly the Software Center say's after you click on status failed under the overview section of softwa

What Torsten said is right, the file doesn't exists in the machine where the install has failed.

Just to address Raman's curiosity, this is what I see appear in Software Center when I click on "Failed"

"There was a problem applying changes to the software. You can try again. Or, if the problem continues, the information that is shown in the following section can assist your help desk in troubleshooting.

Click OK to return to Software Center.

More information:
The software change returned error code 0x087D00324 (-2016410844)"

We've gone through almost the same situation but below works for us.

https://social.technet.microsoft.com/Forums/en-US/811de038-c717-432c-b4f5-58aee3bcb54f/variation-in-package-deployment?forum=configmanagerapps

I haven't tried changing the command line for the SCCM application as mentioned in the link above, but we found that the application that we were trying to uninstall was not properly installed in the machine.

Though there was an ARP entry which we were querying to identify that the machines having "Meridium APM Framework" the installation files were not present in the PC. As a result we were unable to even manually uninstall the application from the Programs and Features as well.

May be the next time I have a similar requirement, I am going to use the uninstall command line and we have started including uninstall command line on all applications that we create. Lesson learnt. :)

Anyways I thank everyone who replied to my questions! Cheers!