Hi,
I’ve been testing the deployment of both Visio Pro 2013 and Project Pro 2013 with PSAT. While installation works fine, uninstall unfortunately fails with error code 1603.
I ran an uninstall manually to try and get more information in the log and managed to extract this from it:
<code>MSI (s) (88:44) [08:55:26:846]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI870B.tmp, Entrypoint: DcaRemoveSpawn
Action start 08:55:26: DcaRemoveSpawn.
CustomAction DcaRemoveSpawn returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)</code>
I’ve looked and looked but so far haven’t found the cause of this issue. This happens on two different machines as well, so I ruled that possibility out.
If anyone’s seen this before, I’d appreciate any pointers.
Cheers,
Dan
It fails uninstalling from Programs and Features or manually using a command line? If it’s from the command line, can you post the command. TechNet might be a better forum for this.
Hi Brian, thanks for the reply.
They both uninstall fine from Programs and Features, but using the toolkit or running the deploy-application.exe manually from cmd, they fail. I just noticed one thing in my test machine, two uninstall logs are kept for each, Project and Visio. On one, it only says it failed with code 1603, in the other it gives some more information after:
<code>MSI (s) (E8:34) [08:41:05:441]: Product: Microsoft Visio Professional 2013 -- Removal failed.
MSI (s) (E8:34) [08:41:05:441]: Windows Installer removed the product. Product Name: Microsoft Visio Professional 2013. Product Version: 15.0.4569.1506. Product Language: 0. Manufacturer: Microsoft Corporation. Removal success or error status: 1603.
MSI (s) (E8:34) [08:41:05:441]: Attempting to delete file C:\Windows\Installer\22a41366.mst
MSI (s) (E8:34) [08:41:05:443]: Deferring clean up of packages/files, if any exist
MSI (s) (E8:34) [08:41:05:443]: Attempting to delete file C:\Windows\Installer\22a41366.mst
MSI (s) (E8:34) [08:41:05:443]: Unable to delete the file outside of the engine. LastError = 2
MSI (s) (E8:34) [08:41:05:443]: MainEngineThread is returning 1603
MSI (s) (E8:5C) [08:41:05:445]: RESTART MANAGER: Session closed.
MSI (s) (E8:5C) [08:41:05:445]: No System Restore sequence number for this installation.
=== Logging stopped: 14/01/2016 08:41:05 ===
MSI (s) (E8:5C) [08:41:05:445]: User policy value 'DisableRollback' is 0
MSI (s) (E8:5C) [08:41:05:445]: Machine policy value 'DisableRollback' is 0
MSI (s) (E8:5C) [08:41:05:445]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (E8:5C) [08:41:05:445]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E8:5C) [08:41:05:446]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E8:5C) [08:41:05:446]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (E8:5C) [08:41:05:446]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (E8:5C) [08:41:05:446]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (E8:5C) [08:41:05:446]: Restoring environment variables
MSI (s) (E8:5C) [08:41:05:446]: Destroying RemoteAPI object.
MSI (s) (E8:EC) [08:41:05:446]: Custom Action Manager thread ending.
MSI (c) (0C:04) [08:41:05:447]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (0C:04) [08:41:05:448]: MainEngineThread is returning 1603
=== Verbose logging stopped: 14/01/2016 08:41:05 ===</code>
As for the toolkit uninstall command, here you go:
Visio: Execute-MSI -Action Uninstall -Path '{90150000-0051-0000-0000-0000000FF1CE}'
Project: Execute-MSI -Action Uninstall -Path '{90150000-003B-0000-0000-0000000FF1CE}'
Pretty straightforward. They toolkit window with the “Uninstalling xxxx. Please wait…” window pops up for a couple of seconds, then the uninstall fails straight away.
Thanks,
Dan
I don’t believe you can silently uninstall Office products like this.
https://technet.microsoft.com/en-us/library/cc178956.aspx#BKMK_uninstall
Here’s my recommended approach:
Execute-Process -Path “setup.exe” -Parameters “/uninstall VisPro /config <tick mark>”$dirFiles\SilentUninstallConfig.xml<tick mark>""
Note: Replace <tick mark> with the actual character
Contents of SilentUninstallConfig.xml
<pre class=“brush: xml; gutter: true; first-line: 1; highlight: []; html-script: false”>
<Configuration Product=“VisPro”>
<Display Level="None" CompletionNotice="no" SuppressModal="yes" AcceptEula="no" />
<Setting Id="SETUP_REBOOT" Value="Never" />
</Configuration>
Hi Brian, thanks for pointing that out, changing to execute-process works… up to a point. If I just do up to /uninstall VisPro
it works, though of course the user would need to click once to confirm the uninstall.
If I leave the full line and try a silent uninstall, it fails, a pop-up… pops up saying it couldn’t find a valid installation source and the log ends with error 1392, which according to MS, means “The file or directory is corrupted and unreadable.”