Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

ERROR: Internal : Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Pradeep_SundarG
Level 3

‎01-05-18 02:34 PM

Hi All, We are experiencing this error while BP tries "get-next item" from queue we encounter following issue: ERROR: Internal : Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.   This is currently affecting 100+ bots dependent on queues to process information, Did anyone face this issue before ? any known resolutions?   -Pradeep Sundar
0 Likes
5 REPLIES 5

Denis__Dennehy
Level 15

‎01-05-18 06:05 PM

It sounds like either a network connectivity issue or an issue with the efficiency of your database.  Do you have an archiving policy (deleting session logs) and are your solutions deleting/cleaning up old work queue items - I have previously heard if issues with Get Next Item when a client does not have a Data and Archiving policy in place - so the database and work queue table sizes were ridiculously enourmous.
0 Likes

Pradeep_SundarG
Level 3

‎02-05-18 01:08 AM

Thanks Denis. We have started archiving and we are now less than 100GB (From 400GB last month, 180 GB yesterday )when we started having this issue. Archiving is still in progress and we are expecting to get to ~20 - ~30 GB. However, We still have timeout issues from BP Application Server to database (including a new one for ""BPDS_QueueVolumesNow"": Will you able to shed more light on the below events? A database error occurred while executing the statement: BPDS_QueueVolumesNow A database error occurred while executing the statement: usp_getnextcase   Regards Pradeep Sundar
0 Likes

Sharath_KumarP1
Level 2

‎31-07-18 09:27 PM

Hi Pradeep,   Does Archiving solved the issue ? We are facing the same issue now.  Process is running for a while and around 4 AM (after running 2 hours ) everyday , we are getting the same error. Please provide fix if you found any. 
0 Likes

Oscar_CelioAvi1
Level 2

‎25-10-19 05:53 PM

Hi, Did you solved this problem? we are facing the same error, and we don't know how to solve.


------------------------------
Oscar Celio Avila Castellanos
Ingeniero de sistemas
VASS LATAM
------------------------------
Preview file
108 KB
0 Likes

NithySuthakaran
Level 2
In response to Oscar_CelioAvi1

‎10-03-21 07:54 PM

Hello,
Did the archival work or there was another solution to this problem?


0 Likes