Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Fatal Error

Updated: 03 Sep 2010 | 8 comments
umeshbg's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi
I am creating a new project using MSI script in windows installer editor.
i created a welcome dialog, Two features & a component. If i run the program welcome dialog will appear if i click next its giving fatal error "Installation ended prematurely because of an error"
The log file is also attached.
Please any solution?
Thanks

discussion Filed Under:

Comments

EdT's picture
28
Jul
2010
0 Votes 0
Login to vote

Solution

Unless you are sure you know how to edit the dialog sequences, I would strongly recommend that you stick with the standard dialogs and just edit them to meet your needs.

Just saying "I created a welcome dialog" really gives us no information on which to advise you. The only suggestion I can offer based on what you have told us is "Fix the error in your dialog"

The logfile indicates that the problem is in your dialogs - nothing more detailed.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

umeshbg's picture
28
Jul
2010
0 Votes 0
Login to vote

Fatal Error

Hi EdT
If i run any of the file its giving fatal error. I didnt new that it is mandatory that i have to edit the dialogs. This time i created a new project & edited the welcome screen & License agreement  dialogs.
Again its giving fatal error. The log file attached.
Please give me solution.

Thanks

AttachmentSize
Install.doc 53.75 KB
VBScab's picture
28
Jul
2010
0 Votes 0
Login to vote

You've missed Ed's point

From the log, it looks like you've messed up the dialog order but, as Ed asked, why are you editing the standard dialogs? Get your project working first, back it up (or set Wise to make automatic backups), THEN start playing with dialogs.

EDIT:
>I am creating a new project using MSI script
I think this is the problem. As you seem to be a novice at this, I'd recommend using the GUI to create your project. I'd also recommend that, before you do anything further, download and digest Phil Wilson's ouevre, The Definitive Guide to Windows Installer. You'll find packaging a challenge unless you know the fundamentals, to which this tome will introduce you.

Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.

EdT's picture
28
Jul
2010
0 Votes 0
Login to vote

It is NOT mandatory that you have to edit the dialogs.
What I am saying is that you need to know what you are doing if your project needs any dialog changes from the standard dialogs.
Clearly you are doing something wrong, as the same situation persists in your latest attempt - the log just tells us you have a fault dialog sequence.
In order to check whether you have an undamaged new project template, I suggest you start a new project, leave the dialogs unchanged, add a single file to install, and test that. If it still errors out, then you have a faulty Wise template so you may need to uninstall and reinstall Wise.
On the other hand, if the install works, then make ONE change at a time, and retest. Edit the license dialog only and test. Then edit the Welcome screen and test.
When you have found exactly what is causing your problem, and you still cannot figure it out, give us the FULL description of what you are doing. Just telling us that your edited a dialog and you get a fatal error, then expecting us to diagnose what the cause is, is frankly wasting everyones time.  You might as well ring your doctor, tell him you are ill and expect him to diagnose your illness without any further information.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

umeshbg's picture
29
Jul
2010
0 Votes 0
Login to vote

Hi EdT

I tried as you said started nwe project,left the dialogs unchanged & added a single file to install & tested. Again its giving error. Means i have to uninstall & reinstall the wise.
In customaction WisePrevDlg & WiseNext Dlg the type is "6" is it the reason for that error?

Any way i will try to reinstall the Wise.

Thanks

EdT's picture
29
Jul
2010
0 Votes 0
Login to vote

A type 6 custom action means that the CA is in vbscript. The dialog handling changed to VBScript at WFWI 6, if I recall correctly, so this is probably correct.
HOWEVER, that reminds me of what might be a relevant point. If your test machine is unable to run vbscript, or your antivirus blocks vbscripts, then this may be the cause of your problem.
So if it is not too late, check if your test machine has vbscript support (ie try running a vbscript)

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

umeshbg's picture
01
Aug
2010
0 Votes 0
Login to vote

Hi EdT

I have checked running VBScript its working fine, i reinstalled the wise & OS also, again its giving a same fatal error. Is the problem that software has corrupt?

Thanks

EdT's picture
02
Aug
2010
0 Votes 0
Login to vote

Something is definitely wrong

Start with a clean O/S install and then download the eval version of WIS 7 SP2 and test that.
Do not install any antivirus or other programs. Use a local admin profile and not a domain account.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.