Question

Connection attempt failed timeout error in routing

  • 21 May 2021
  • 0 replies
  • 198 views

Userlevel 2
Badge +6

We are on Apps10, update 7.  We have had an intermittent error that occurs when searching in the Routing screen that has been occurring since we went live in December.  Because it is intermittent it is very difficult to troubleshoot and extremely frustrating for the users.  Frequently users are just searching for a few records, but it hangs for a  long time, and returns this error:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

 

If you refresh your screen, the data comes in immediately.  We do not have huge routings, most are under 30 operations and  10-20 document attachments.  Our DBA has already reviewed all the timeout settings on the MWS and we feel everything is optimized but I was just wondering if any other clients had experienced this. 

 

 


This topic has been closed for comments