Hi,

The MSI works fine when we install manually. When we install in system context then the application is not registered in Windows Installer database and also not listed in ARP. This is causing problem when we try to uninstall the application.

msiexec /x "Product code" /qn
or
msiexec /x "app name.msi" /qn

throwing an error 1605.

your help would be highly appreciated.

I am using /qn switch while installing and Marimba is the deployment tool.

Compared the verbose log files, everything looks good. I am not able to find the reason why it is not getting listed in ARP.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Vendor provided the recompiled MSI and now everything looks good.

I am still interested in knowing the solution if someone had similar problem...so please share if you had similar problem and got fixed by you.
Answered 10/05/2010 by: WSPPackager
Senior Purple Belt

Please log in to comment
0
my first instinct, mainly because 1605 means "this operation is only valid for products that are currently installed", is that you installed per-user, instead of per-machine. (was ALLUSERS=1?)

If you want to delve into the issue, maybe compare the old and new vendor MSIs, see what the differences are

PJ
Answered 10/05/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
Hi PJ

I did tried with Per machine option (with ALLUSERS=1) but no use. I would compare both MSIs and will see what would casued the problem.
Answered 10/06/2010 by: WSPPackager
Senior Purple Belt

Please log in to comment
0
i'm curious. do you have a property called ARPSYSTEMCOMPONENT set to 1? this will prevent the add/remove entries to be added.
Answered 10/06/2010 by: kardock
Second Degree Green Belt

Please log in to comment
0
Good call, Kards.

Actually, ARPSYSTEMCOMPONENT could be set to 'antidisestablishmentarianism' and it would have the same effect. It's a common misconception that setting it to '0' is the opposite to setting it to '1'. Whilst in mathmatical logic that might debateably be true, the property needs to be absent to have the package registered normally and for its details to appear in ARP.
Answered 10/07/2010 by: VBScab
Red Belt

Please log in to comment
0
msiexec /x "Product code" /qn
or
msiexec /x "app name.msi" /qn

throwing an error 1605.


But even if ARPSYSTEMCOMPONENT is set you should still be able to uninstall the app with the command lines above without getting the 1605 error.
Answered 10/07/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
Hi

ARPSYSTEMCOMPONENT is not sbeing set to 1. I am still trying to find the issue since I have both MSIs (bad and good).

surely will update this post once I find the reason.
Answered 10/07/2010 by: WSPPackager
Senior Purple Belt

Please log in to comment
0
Just use MSITRAN to create a transform between bad and good. Apply the transform to bad and the changes will be obvious shouldn't take long.
Answered 10/07/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
I have the exact same problem. I created a 64-bit MSI using Wise. It does not show up in ARP and cannot repair using /fpu if installed in system context.
Although registry entries do get created in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall
Stumped!
Answered 07/14/2011 by: codewarrior
Yellow Belt

Please log in to comment
0
By the way, i tried setting ALLUSERS=1 and it worked!
I dont know why it didnt work for WSPPackager.
Answered 07/14/2011 by: codewarrior
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity