Once each day, HighGear recalculates the indexes on all of its database tables, to ensure that the system performs consistently well when users are accessing it. To allow HighGear business process management software to recover if the database server is not working, it times out if the database takes more than one hour to complete the reindexing process. If the one-hour timeout is exceeded, a message is written to the server’s event log saying “There was an error while re-indexing the database. Message: Timeout Expired. The timeout period expired prior to completion of the operation or the server is not responding.”
If you get this error message, the first thing to do is to make sure that you can still log in to HighGear. If you cannot connect to HighGear BPM software, there is a problem with your database server or with HighGear’s connection to it. However, if you are able to log in to HighGear, then this error is probably happening because your server’s reindexing process is too long to complete in one hour. If you need to extend the timeout, perform the following steps:
- Open your HighGear® program directory (usually, c:\Program Files\HighGear X5)
- Open the settings.xml file in a text editor.
- Find the section called <GlobalSettings>
- In that section, find the setting called <ReIndexTimeOut>. This setting is simply the number of seconds that HighGear® should wait for the reindexing process to finish.
- Change the setting’s value to the amount of time (in seconds) that you would like HighGear® to wait before it assumes that the process has timed out. The default is 3600, or one hour.
- Save the file.
For information about the other settings in the <GlobalSettings> section, refer to How To: Change the time of day that HighGear recalculates the indexes for its database and How To: Change the time of day that HighGear sends notification emails about due and overdue jobs.