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.
I try to run the installation executable, jdk-1_5_0_06-nb-5_0-win.exe, on our machine: Microsoft Windows XP Professional Version 2002 Service Pack 2 and I get the error pop-up: (Title bar) InstallShield Wizard could not utilize start class: com.installshield.wizard.Wizard
Other things I have tried: - I successfully installed the jdk separately, using jdk-1_5_0_06-windows-i586- p.exe and then tried to install netbeans using netbeans-5_0-windows.exe. The install of netbeans failed with the same error as when I tried to install jdk-1_5_0_06-nb-5_0-win.exe. - I then tried using the netbeans.zip file to install netbeans. I was able to unzip it and start netbeans. Then I tried to install the profiler using netbeans-profiler-5_0-win.exe. It failed with the same error as seen with the other failed installs.
Weird I used Google to search for this problem and there is http://community.installshield.com/showthread.php?s=d6690f58c081893feabf15fd45f1b399&t=151089. So question is do you any antivirus software?
Last sentence should be: Do you USE any antivirus software? Another possibility to get more detail log is to extract setup.jar using commandline option -is:extract and then run java -Dis.debug=1 -jar setu.jar. It will log more details to console.
I extracted and ran with debug flag as recommended. I'll attach an (annotated) log. In a nutshell it says that the class is not found, but I was able to find the class looking at the "EXTERNAL CLASS JAR LIST" was printed out.
Created attachment 30422 [details] Log - run Installshield w/ debug flags
My typo I meant setup.jar. Please also check MD5 checksum to be sure installer is not corrupted (small chance, just to be sure). And any Antivirus/firewall software on machine? I did not see such class loader problem with installer so far. Clean your temp dir. Do you have anything added in JDK jre/lib/ext? For clean JDK installation content is: -rw-r--r-- 1 root root 8176 Nov 10 2005 dnsns.jar -rw-r--r-- 1 root root 802394 Jan 30 10:27 localedata.jar -r--r--r-- 1 root root 153235 Nov 10 2005 sunjce_provider.jar -r--r--r-- 1 root root 175811 Nov 10 2005 sunpkcs11.jar or lib/ext? You may try to clean also C:\Program Files\Common Files\InstallShield\Universal (though from classpath it does not seem it is problem.)
By the way, there is antivirus software on the machine, but we have tried to disable it. We stopped several services that we believe were part of the antivirus stuff. Another point of information - I tried using j2re1.4.2_11 as the java for running installshield, and it came up with the same error.
Another try could be run exe with -is:tempdir <Simple path> eg. -is:tempdir "C:\Installer" (this dir must exist already so you must create dir manually if it is not yet created) or anything if Java class loader is not confused by some non ASCII char in classpath.
I re-enabled the virus detection software and rebooted the machine, and now the installer runs OK. Thanks for your help.
Ok. Closing as WORKSFORME. Please what antivirus software do you use? I suspect there is some runtime check of code loaded to memory but I have no idea how it could break loadeding classes by classloader and cause ClassNotFoundException.
One coleague also said that it can happen when temp space is on edge, installer free space check passes but loading fails. What is your free space on temp dir or try -is:tempdir <Another disk with more free space>. Especially nb+jdk bundle installer is hungry for temp space. Default temp dir is on systme disk which is C: (in most cases).
We use McAfee VirusScan Enterprise, version 7.1.0. I agree that I don't understand how/why rebooting and/or re-enabling the antivirus stuff would effect the install. As for free space - 200G free on the C: drive. I don't think that was an issue.
Yes 200GB is more than enough, problem with free space happens when it is about 200-400MB free space left.
*** Issue 77468 has been marked as a duplicate of this issue. ***
*** Issue 93836 has been marked as a duplicate of this issue. ***