E 1603

Got a problem you cannot solve? Try here.
Tommy
Posts: 27
Joined: Wed Oct 23, 2013 5:36 am

E 1603

Postby Tommy » Thu Oct 24, 2013 10:07 am

Hello All,


MSI Error code 1603 seems to be exotic different things could generate it. I could just generate this error code by calling an IA MSI blank setup project from another IA project.
However my blank setup is utterly empty, which means, zero number of code line in MSIcode !

Please take a glance on my attached log file and enlighten me what could be a problem.

Regards,
Tommy
Attachments
DICOM.txt
(167.72 KiB) Downloaded 552 times

FrancescoT
Site Admin
Posts: 5361
Joined: Sun Aug 22, 2010 4:28 am

Re: E 1603

Postby FrancescoT » Thu Oct 24, 2013 11:49 am

... let me check.

Regards
Francesco Toscano
InstallAware Software

White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE

Tommy
Posts: 27
Joined: Wed Oct 23, 2013 5:36 am

Re: E 1603

Postby Tommy » Fri Oct 25, 2013 6:34 am

This basically happens also when a blank setup project calls another blank msi file.

FrancescoT
Site Admin
Posts: 5361
Joined: Sun Aug 22, 2010 4:28 am

Re: E 1603

Postby FrancescoT » Fri Oct 25, 2013 11:37 am

Dear Tommy,

it is not relly easy to find out what exactly is causing the error from your log ... it seems a call to DLL failure ... but I can't confirm it.

Try to post a very minimal project and I'll verify it.

Regards
Francesco Toscano
InstallAware Software

White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE

Tommy
Posts: 27
Joined: Wed Oct 23, 2013 5:36 am

Re: E 1603

Postby Tommy » Mon Oct 28, 2013 8:09 am

Hello,

I will attempt to solve this problem without having an additional MSI call because (according to the documentation) "Run Program As" command should be able spawn new process with defined environment.
Regards,
Tommy

Tommy
Posts: 27
Joined: Wed Oct 23, 2013 5:36 am

Re: E 1603

Postby Tommy » Thu Nov 14, 2013 8:37 am

Hello,

I have two IA QuickSetup projects A and B, which is required by A.
I can install B by just installing it, however the following error occurs while installer A starts to install B as a runtime pre-requisite.

Action start 15:45:17: ACTEZ.
MSI (s) (C4:60) [15:45:17:799]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'ACTEZ'
MSI (s) (C4:60) [15:45:17:819]: Creating MSIHANDLE (7) of type 790542 for thread 2400
MSI (s) (C4:FC) [15:45:17:832]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI5DD5.tmp, Entrypoint: ActProc
CustomAction ACTEZ returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (C4:FC) [15:45:17:882]: Closing MSIHANDLE (7) of type 790542 for thread 2400
Action ended 15:45:17: ACTEZ. Return value 3.


Any clue ?

Regards,
Tommy

FrancescoT
Site Admin
Posts: 5361
Joined: Sun Aug 22, 2010 4:28 am

Re: E 1603

Postby FrancescoT » Thu Nov 14, 2013 11:30 am

Dear Tommy,

it is not easy to say which could be the cause of your issue without having your projects ( ... pratically impossible).

You must provide more details ... otherwise, how can I be able to have a possible idea of what really happen?

Regards
Francesco Toscano
InstallAware Software

White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE


Return to “Technical Support”

Who is online

Users browsing this forum: No registered users and 82 guests