As customer is reporting that their IceBreak jobs are sitting in a SIGW state and when they look in the job log they can see program signature violation message.
Do you know what is causing this and how it can be fixed ?
This happens sometimes when you have InterForm and IceBreak running at the same time: InterForm contains an extreme old version of the IceBreak OEM core which I believe is not being used in InterForm. The version conflict between InterForm and IceBreak confuses the current IceBreak which try to rebind to the current IceBreak core in the library list – which unfortunately is the old version found in InterForm.
The best way is to simply rename the service program SVC200 in InterForm to I.e. SVC200_ .. Or move InterForm under IceBreak in the library list.
Re: IceBreak SIGW and program signature violation
Hi;
This happens sometimes when you have InterForm and IceBreak running at the same time: InterForm contains an extreme old version of the IceBreak OEM core which I believe is not being used in InterForm. The version conflict between InterForm and IceBreak confuses the current IceBreak which try to rebind to the current IceBreak core in the library list – which unfortunately is the old version found in InterForm.
The best way is to simply rename the service program SVC200 in InterForm to I.e. SVC200_ .. Or move InterForm under IceBreak in the library list.
Best regards,
Niels Liisberg