Hi Tebogo,

I just tried to replicate the issue in V12 P29 with sigma GTEST active and did not get the same error, I can not see if anyone has reported this issue. It will be best if you log it with your Sage support provider so it can be investigated fully. Are you able to log it to your support provider?

Kind Regards

Vish

Hi Vish

Thanks for the reply, I have tested the same on my side on Patch 29 & could not replicate. I was hoping there is anyone who might have an idea on what causes this issue on the client's environment as I have 2 clients who logged  similar issue on Patch 29 & one on Patch 27 but seems to be data related.

Hi Tebogo,

Yes, some of these jenkinsslave messages are environment related but can be investigated, if this issue continues please log it with your Sage Support team, such cases are being investigated case by case bases as they all are unique, it will require a debug log file from your customer's environment and Sage R&D can investigate further.

Kind Regards

Vish

Hi Tebogo,

Yes, some of these jenkinsslave messages are environment related but can be investigated, if this issue continues please log it with your Sage Support team, such cases are being investigated case by case bases as they all are unique, it will require a debug log file from your customer's environment and Sage R&D can investigate further.

Kind Regards

Vish

Thanks for your guidance Vish.