This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 40255 - Could not load wizard specified in /wizard.inf (104)
Summary: Could not load wizard specified in /wizard.inf (104)
Status: RESOLVED DUPLICATE of bug 26965
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: Other Windows XP
: P3 blocker (vote)
Assignee: issues@installer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-19 00:55 UTC by sglaser
Modified: 2009-11-07 13:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sglaser 2004-02-19 00:55:08 UTC 
Produces dialog box with this error message and 
an OK button. Hitting OK exits the installation.

Installshield Wizard

The wizard cannot continue because of the 
following error: could not load wizard specified 
in /wizard.inf (104)
Comment 1 sglaser 2004-02-24 19:43:00 UTC 
It appears this bug disappeared in the latest development build of
3.6Beta (NetBeansIDE-dev-200402221900-ismp5-windows.exe downloaded a
few minutes ago).

Assuming you guys did something to fix the problem, then you should
close this report.

If you didn't change anything then the planets just changed alignments
and the bug is still out there and is currently just hiding.
Comment 2 Milan Kubec 2004-02-25 07:58:40 UTC 
Please evaluate.
Comment 3 zikmund 2004-02-25 10:37:14 UTC 
It seems like known issue #26965. It's InstallShield problem and we
can't do anything with that :-(, even it is quite often bug (detected
several times last weeks).

Workaround: rename/move "jre/lib/endorsed/sax.jat" file in your J2SDK
installation for the NetBeans installation time. Then you can
rename/move it back.

What I wonder, is why it works with last dev build.
Sglaser, are you sure, that you didn't do anything with J2SDK
installations? (install another one, have more installation, etc.)?
Thanks for your investigation.

I'll leave it NEW up to the time we will know why it works with last
dev build.
Comment 4 George Hernandez 2004-02-25 16:46:54 UTC 
Please see issue #39705 for the best description of the problem and
solution. These issues are a duplicate of issue #26965.

*** This issue has been marked as a duplicate of 26965 ***