"Installer User Interface Mode Not Supported" when adding sqljdbc4.jar as dependency
I was wondering if there are any known issues (or if anyone has experienced anything similar) with InstallAnywhere 2010 and SQL Server (specifically, with the Microsoft driver sqljdbc4.jar). I downloaded the driver from http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a737000d-68d0-4531-b65d-da0f2a735707. When I add it as a dependency to my custom action, the installer builds with no error, but when I try to run the generated exe, I get a pop-up with the message “Installer User Interface Mode Not Supported”. I click OK and the installer closes. The console has the following message:
Couldn’t find the InstallScript to run the installer from! Unable to load the script. ========================================== Installer User Interface Mode Not Supported Unable to load and to prepare the installer in GUI mode. ==========================================
If I remove the dependency on this jar, then the installer is able to start fine. So a few things...
1) What does the error "Couldn’t find the InstallScript to run the installer from!" mean? How would I go about fixing it?
2) Has anyone run into an issue like this before? Either with this specific jar or any other jars?
3) Can someone shed some light on how adding a jar as a dependency can cause the installer to throw this error?
4) The installer has not even started yet, so the installer should not even have hit the custom code that uses this jar. Is there something that happens behind the scenes when the installer starts up that references all the bundled jars?
I'm afraid you've stumbled into a very old issue which still stands: if I'm not mistaken, the .jar you've downloaded is signed, and IA doesn't support signed jars: http://community.flexerasoftware.com/showthread.php?t=178483&highlight=signed+jar (I'm sorry for the broken links, unfortunately the old community forums (at the time IA was made by ZeroG) are definitely down.
