Submitted by Anonymous (not verified) on Thu, 05/11/2017 - 17:49


This week the ICECAP system has stopped working twice displaying the ‘Error occurred executing function.

The first time was on Monday morning when myself and three other users got this error message. Then within minutes it started to work again for us all.

Then last night at 22:00 it was reported to me it was not working, it has been OK today.

Is there anywhere on the system I can look to find any clue why this is happening?

Niels Liisberg

Mon, 05/15/2017 - 11:59


There is no errors in IceCap - or the way you are integrating with IceCap.

The reason is that "ruCntStkChk.aspx" is creating a new session each time it is called which now is the reason you have 254890 sessions in your system.

It is easy to fix. Use session stability by URL - and simply give it a session number into the url..

so instead of

insert a session number in the url prefixed by a dot. 

Here I use session zero - and notice the dot. Now Any request with /.0/ will share the same job and session.

Ultimately it will also give better performance since the job stays resident.

Best regards,

Niels Liisberg