E-CR: Crystal Reports Stay In Initiated Status After Receiving Error: "Process Timed Out : Increase Authentication Timeout in PSPRCS.CFG"
(Doc ID 1271020.1)
Last updated on APRIL 19, 2018
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.50 and later
Information in this document applies to any platform.
On 8.50 version, Crystal Reports
Crystal Processes remain in Initiated status, showing the following error in the CRW*.Log:
"Process Timed Out : Increase Authentication Timeout in PSPRCS.CFG"
Setting Authentication Timeout = 240 does not resolve the issue.
The issue is sporadic and often occurs when multiple GLC7501- reports are submitted, but can be also be replicated in customer environments with multiple XRFWIN reports.
The issue can seemingly only be resolved temporarily by putting all queued Crystals on Hold, rebooting the machine, and restarting the scheduler, then releasing the Hold processes one-by-one.
The problem environment does not have numerous instances of "TCP Reconnect" in the Microsoft Process Monitor utility output, as summarized in Doc ID 1209313.1.
Expect Crystal processes to go from Initiated to Processing to Success, according to the Max Concurrent process definitions and constraints of the process scheduler Server definition.
The issue can be reproduced at will with the following steps:
1. Go to PeopleTools > Process Scheduler > System Process Requests.
2. Run sample process XRFWIN (Cross Reference Windows Listing). Output Type = Web, Format=PDF
3. Crystal process stays in Initiated status and never changes.
The issue has the following business impact:
Due to this issue, users are down completely because all Crystal processing stops. In order to workaround the server, the physical host must be rebooted.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!