Hi All
We recently updated our system to use AES256 as we had upgraded our Windows Forest and RC4 was no longer supported.
Since doing this (last Weds), we have had a large number of errors on the server “JobServerChildCrash” resulting in failed instances of Crystal reports.
I have logged a call with our third party support (SAP Partner) and so far they have not been able to determine what is causing the issue and don’t believe it’s related to AES256 (though it seems a bit strange that its only been happening since the change!).
All our schedules are Crystal, the failures are happening at random times, to random reports with different data sources and/or destinations. There doesn’t appear to be a pattern, a report that ran fine yesterday failed today etc.
There was mention of an issue with Crystal having a default printer in the report, however removed the default printer in a report that had failed on Tuesday, it ran ok yesterday but failed this morning,
There doesn’t appear to be a memory issue on the server (in fact we increased memory from 20gb to 32gb and it’s running about 50% on both CPU and Memory.
Has anyone had this issue or can give me any ideas of where to look?
What errors appear on the failed crystal instances? Did you look for errors in event log and the BO logging folder? Are you using AD authentication and Kerberos? When creating the keytab file using ktpass you must specify the crypto parameter. I’m not sure if this must match your network encryption but may be worth looking into.
Hi
The error that appears in Instance Manager is:
“Object failed to run due to an error while processing on the Job Server.”
We have looked in the Event Log and the Logging folder, there was nothing specific we could see.
We switched the logging to HIGH and sent the results to SAP who are currently looking at it.
We are using AD Authentication (and SSO for Infoview), when the Keytab file was created we specified the parameter as AES256-CTS-HMAC-SHA1-96
(we previously used RC4)
The failures are seemingly random which is the most frustrating thing. I am being advised that the change to the encryption should not make any difference but it just seems odd to me that it’s only started happening since the change.
Our CMS database is on a different server to the application…not sure if that makes a difference?