- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Getting ISDEV : fatal error -6199: Internal build error during Jenkins pipeline build
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Getting ISDEV : fatal error -6199: Internal build error during Jenkins pipeline build
Hi,
I am trying to build .ism files using jenkine pipeline build an encounter the followingspProject->Open Failed
ISDEV : fatal error -6199: Internal build error
Unspecified error
However, when trying to build .ism manually it does succeeded !!As well as project file was set to XML.
Can someone advice??
Hi adirisr,
Please make sure your jenkins agent run as same user as who installed installed shield, like if user X is installed installshield in machine1 then your jenkins agent also login with same user x credentails and then try build and see it works or not.
Kind Regards,
Thanks for replying,
Is it possible to change the installeshield credentials while it is already installed or i must uninstall and reinstall??
Tried that ...and issue persist :((
Please check the project related files and ism files are not opening in visual studio or any other tools, make sure you close all the files and projects and the tools and try building
Even after doing that if still fails then please Pass an additional parameter -v to the IsCmdBld.exe when it is failing. This will provide some more information about the failure.
-v parameter will help you get details verbose build log and check logs for failure cause
https://docs.revenera.com/installshield21helplib/helplibrary/ISCmdBldParam.htm
Are you using full IS version or SAB Installshield to build project using Jenkins?
Please share the complete installation log, did you check the files are not opened in any tool
Thanks for reply..
Yes we checked and the files not opened via VS or any other app.
Is there any way to share the log with you in secure manner??
else you can go ahead and raise a support case.
I disabled AV as well as windows defender and still no luck..
Issue persist..is there any other support member that can help me resolve it???