Uninstalling Application

Hi,

I am currently creating an application to uninstall a program called Philips iSite Enterprise 3.6.114.1.  I am having a difficult time understand why it will not work.

Command I am using: MsiExec.exe /X{3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7} /qn

When scheduled through SCCM I am getting the following information in the AppEnforce log.

+++ Starting Uninstall enforcement for App DT "iSite Enterprise" ApplicationDeliveryType - ScopeId_1197784C-0394-4848-A90A-D754E44BFCD6/DeploymentType_0d4a8f75-8130-4ab7-805f-c2f367f03045, Revision - 15, ContentPath - C:\Windows\ccmcache\8b, Execution Context - System AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    A user is logged on to the system. AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Performing detection of app deployment type iSite Enterprise(ScopeId_1197784C-0394-4848-A90A-D754E44BFCD6/DeploymentType_0d4a8f75-8130-4ab7-805f-c2f367f03045, revision 15) for system. AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
+++ Discovered application [AppDT Id: ScopeId_1197784C-0394-4848-A90A-D754E44BFCD6/DeploymentType_0d4a8f75-8130-4ab7-805f-c2f367f03045, Revision: 15] AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    App enforcement environment:
 Context: Machine
 Command line: MsiExec.exe /X{3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7}
 Allow user interaction: No
 UI mode: 0
 User token: null
 Session Id: 4294967295
 Content path: C:\Windows\ccmcache\8b
 Working directory:  AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Prepared working directory: C:\Windows\ccmcache\8b AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
Found executable file MsiExec.exe with complete path C:\windows\system32\MsiExec.exe AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Prepared command line: "C:\windows\system32\msiexec.exe" /X{3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7} /qn AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Executing Command line: "C:\windows\system32\msiexec.exe" /X{3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7} /qn with system context AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Working directory C:\Windows\ccmcache\8b AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Post install behavior is BasedOnExitCode AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Waiting for process 5700 to finish.  Timeout = 120 minutes. AppEnforce 7/27/2015 9:13:11 AM 5228 (0x146C)
    Process 5700 terminated with exitcode: 1603 AppEnforce 7/27/2015 9:13:17 AM 5228 (0x146C)
    Looking for exit code 1603 in exit codes table... AppEnforce 7/27/2015 9:13:17 AM 5228 (0x146C)
    Unmatched exit code (1603) is considered an execution failure. AppEnforce 7/27/2015 9:13:17 AM 5228 (0x146C)
++++++ App enforcement completed (5 seconds) for App DT "iSite Enterprise" [ScopeId_1197784C-0394-4848-A90A-D754E44BFCD6/DeploymentType_0d4a8f75-8130-4ab7-805f-c2f367f03045], Revision: 15, User SID: ] ++++++ AppEnforce 7/27/2015 9:13:17 AM 5228 (0x146C)

As you can see I am getting exit code 1603.  When I look at the iSiteEnterprise log it is stating that I am not running the .msi silently...which I am with the /qn switch.  The thing I don't understand is if I open Software Center on the endpoint that I am pushing to and hit the "RETRY" button the uninstall works perfectly fine.  Also, if I run the command locally through command prompt it also works perfectly fine.  The content downloads fine to the ccmcache so I don't think that is the issue.

I tried this command too: wmic product where name="iSiteEnterprise 3.6.114.1" call uninstall

I get the same scenario as post above.  If you need more information please let me know.

Thanks,

Kevin

July 27th, 2015 9:39am

Try adding logging to your command line then get the msi log that is created. Maybe it will have more clues.

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 10:21am

Also try running the same command outside of ConfigMgr and see if the uninstall happens to narrow down if this really is Configmgr related issue or to do with the msi.
July 27th, 2015 10:29am

I will try running the following command: MsiExec.exe /X{3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7} /qn /l*v! "c:\iSiteEnterprise.log"

Does that command look right?  I think I was running this command before and the log wasn't giving me much more information then exit code 1603 and saying I wasn't running the .msi silently.  I will try it again.

Thanks,

Kevin

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 10:31am

I will try running the following command: MsiExec.exe /X{3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7} /qn /l*v! "c:\iSiteEnterprise.log"


Change it to
MsiExec.exe /X {3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7} /qn /l*v! "c:\iSiteEnterprise.log"
July 27th, 2015 10:41am

If I run the command outside of ConfigMgr is works perfectly.  The application uninstalls.  Also, if I hit the "RETRY" button in Software Center is works perfectly too.  That is why I am having difficulty understanding the problem.

Thanks,
Kevin

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 10:49am

Ok, I changed the command to: MsiExec.exe /X {3a3a86d2-041e-4c2a-a6fd-61e7d38ce4a7} /qn /l*v! "c:\iSiteEnterprise.log"

When I pushed the uninstall again to my targeted test machines and checked the log I get some of the following errors.

1: ISMsiServerStartup Failure, Failed to Open the shutdown event, Error = 0x36b7
1: MsiServerStartup failed. Abort installation.
CustomAction ISStartup returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
CustomAction ISMsiServerStartup returned actual error code 1603 but will be translated to success due to continue marking

MSI (s) (38:B8) [10:44:08:534]: Product: iSiteEnterprise -- Removal failed.
MSI (s) (38:B8) [10:44:08:546]: Windows Installer removed the product. Product Name: iSiteEnterprise. Product Version: 3.6.114.1. Product Language: 1033. Manufacturer: Philips Medical Systems. Removal success or error status: 1603.

Property(S): ERR_MSG_DONT_DOUBLE_CLICK = This installer is intended for silent installation by an IT administrator. It must be run from the command line using specific parameters. Please contact your PACS administrator or your IT administrator for proper installation of iSite PACS clients.
Property(S): ErrorDialog = SetupError

I highlighted in bold what I think the issue is but I am obviously running it silently.  Like I said in a comment earlier. If I run the command outside of ConfigMgr is works perfectly.  The application uninstalls.  Also, if I hit the "RETRY" button in Software Center is works perfectly too.  That is why I am having difficulty understanding the problem.

Thanks,

Kevin

July 27th, 2015 10:53am

Can you try using the MSI for your uninstall directly and no the MISCODE

msiexec.exe /X "c:\locationofinstall\iSite.msi" /qn /l*v! "c:\iSiteEnterprise.log"

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 11:00am

That's simply the value of a property (thus the prefix "Property" on that line) and is not in any way indicative of what happened during the MSIs execution.

To find issues in MSI logs, you need to search for the string "return code 3" and then go up line by line until you find the issue.

July 27th, 2015 11:06am

The install directory is: C:\Program Files\Philips\iSiteEnterprise\4.1

The .msi doesn't live there after the application is installed, so I don't think that will work?

Thanks,

Kevin

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 11:07am

1: Failed to extract _IsUser.dll, Ignore it.
1: Failed to extract IGdi.dll, Ignore it.
MSI (s) (74!C8) [10:44:25:128]: Note: 1: 2732 2: 0
MSI (s) (74!C8) [10:44:25:143]: Note: 1: 2732 2: 0
1: Ev63190808
1: ISMsiServerStartup Failure, Failed to Open the shutdown event, Error = 0x36b7
1: MsiServerStartup failed. Abort installation.
CustomAction ISMsiServerStartup returned actual error code 1603 but will be translated to success due to continue marking
CustomAction ISStartup returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 10:44:25: ISMsiServerStartup. Return value 1603.
Action ended 10:44:25: ISStartup. Return value 3.

I think this is where it is failing.  Could it be because SCCM is using a system account and this .msi doesn't like it?  That's the only explanation I can think of since it works when running the command locally on the endpoint.

Thanks,

Kevin

July 27th, 2015 11:43am

That looks to be an InstallShield custom action in the MSI that is failing. If you search for that custom action's name on the web, you'll get a handful of hits. Some seem to indicate it may be a context issue; remember that ConfigMgr uses the local System account to execute command-lines and this may be root of the issue.
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 11:51am

A found a couple posts with similar errors pointing to DCOM permissions for the account running the action. Try running it from a cmd that has been started as local system and do not make it totally silent.

July 27th, 2015 11:57am

I am assuming I can create a task sequence and run the command and that will fix my issue.  You can run the command line with a specific user account.

Thanks,

Kevin

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 12:00pm

That may work or it may cause other issues.
July 27th, 2015 12:04pm

Hi,

you can also try to use  /qb-!  instead of  /qn.

Some custom actions will fail with no ui or missing some actions from the UI sequence.

Stefan

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 4:11pm

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

Other recent topics Other recent topics