Recently we started having a problem building an InstallShield installer on some of our build machines. Yes, some of them -- this is what made it so frustrating.
The error we'd see, using the standalone build is:
ISDEV : fatal error -6199: Internal build error
Not a very informative error, and not much in terms of diagnostic information out there on the web or in Flexera's KB.
I was finally able to track down the cause: character encoding. The .ism is (typically?) supposed to use a UTF-8 encoding, but there are some caveats. If you are editing the .ism directly (e.g. Notepad), your editor /may/ be encoding it in a format that the IS standalone compiler doesn't understand, an you end up w/ a -6199. Adding to the frustration is that it may compile w/ some standalone builds, including the IDE, but will fail on others for reasons unknown.
Regardless, the simplest solution is to open the offending script in the ide and then force a save. Alternatively, you can edit the file with a binary editor and remove the leading "" from the line 1.
5 comments:
Thank you for providing this piece of information. Saved me a great deal of time and headache!
Very useful info.. thank you
Saved me a lot of time as well, thanks!
I have the same error and I had in fact manually edited the ism files so I immediately thought this would be the problem, but sadly it wasn't - instead it's more likely it's because I haven't properly installed/licensed the SAB...
Binance verification process is easy to execute and involves a lot personal information about the user. This verified account helps users in exceeding their daily limit and also, users get other benefits as well. If you don’t know how to carry forward the verification process, you can always take help from the team who is there to assist you. You can call on Binance customer care phone number which is functional all the time and users can avail all the services all the time with just one call.
Post a Comment