Home → EstiMate Version 2 → Known Issues → NexusDB error: The operation could not be completed in the alloted time.

1.1. NexusDB error: The operation could not be completed in the alloted time.

Q:  I just updated EstiMate to the latest 2.2.1.19 build, and I'm getting an error after clicking on the "Open" list.  The error says:

"NexusDB: <unnamed TnxQuery instance>: Query execution failed:"

"NexusDB: The operation could not be completed in the allotted time:

How can I resolve this?


A:  Starting with the 2.2.1.19 build of EstiMate a user defined option was included in the System Settings to allow the user to manually adjust the time in seconds for a database operation to complete before the error message appears.


There are a couple of reasons a user might encounter this error. 

1.  The database is very large, and the time required to join the database tables, and display the results exceeds the currently allotted time.

2.  Network issues are delaying the retrieval of the data.


To correct this issue the user can adjust the "Query Timeout" setting in the System Setting to a higher value (in seconds).

1.  Click "Configure and Manage" > "System Settings" (If you're connected to the Multi-User Server you'll first need to have everyone close out of their copy of EstiMate, and then switch to "Single User Mode" by clicking the "blue" EstiMate icon in the upper left and selecting "Switch To Single User Mode").

2.  In the System Settings click the "Advanced" button.

3.  Under "Query Timeout (seconds)" use the up/down buttons to adjust the number of seconds, or just type in the number.

4.  Start with "30" seconds, and click the "OK" button  If you still get the error move it to "60", "90", and so fourth until the operation completes w/o error.  You only need to update this setting from one of your copies of EstiMate, and it will apply to all of them on your network.


Once you're able to get the Open list or the Archives to open you shouldn't have any further issues opening either until you restart EstiMate because once it's open EstiMate caches most of that data to allow for quicker retrieval the next time (it should open in half the time or quicker).