[wpkg-users] Installshield msi exit code 1603

[Paul McGrath]

Hi Pete,
  Hope everything is well with you down in Brighton.
It isn't already installed, no registry keys, no folders.  This happens on a completely new imaged system as well.  From researching on itninja is is something to do with ' LaunchingUser versus InteractiveUser' and some DCOM setting.  I've created a transform with ISSETUPDRIVEN=1 which was one suggested fix but that didn't work.
  I've also been reading about dcom vbs fix which you are supposed to inject into the MST but I can't work out how.  I think I will just try and repackage the software.
  I hate installshield.
Paul

-----Original Message-----
From: wpkg-users-bounces at lists.wpkg.org [mailto:wpkg-users-bounces at lists.wpkg.org] On Behalf Of Pete Boyd
Sent: 01 May 2013 12:46
To: wpkg-users at lists.wpkg.org
Subject: Re: [wpkg-users] Installshield msi exit code 1603

Hi Paul. 1603, "This software has already been installed on your computer. Would you like to reinstall it?", has in my experience been caused by the system thinking the app is already installed. It might be worth forcing an uninstall before you do the reinstall; or (I'm not as sure on this one) set the WPKG package to accept 1603 as an allowed error code? I have it set as allowed in my packaging of .NET Framework
3.5 SP1.


--
Pete Boyd

thegoldenear.org
openplanit.co.uk

-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users