KB Article administrator on-premise only
Issue
A timeout error occurs while using FactoryLogix. The error may originate from the SQL Server or the Application Server.
Resolution
Diagnose the source of the timeout
-
Collect Application, SQL, and Service logs for FactoryLogix and the affected application (FactoryLogix Office, Operations, and so on.) from FactoryLogix Server Management.
-
Locate the error in the Application log, then check the SQL log at the same timestamp to determine whether a SQL timeout error also occurred.
-
If the SQL log contains a timeout error, perform a database health check (see the database maintenance section below).
-
If the SQL log does not contain an error, the issue is likely one of the following: the Application Server does not meet minimum infrastructure requirements or there is a software defect or data issue requiring further investigation.
Perform database maintenance
Timeout errors may also be caused by a FactoryLogix database that requires maintenance. The two recommended maintenance operations are index reorganization/rebuild and statistics update.
Note
Database maintenance tasks should be performed by your organization's IT team, not by end users.
Reorganize or rebuild database indexes
Database indexes become fragmented over time as insert, update, and delete operations are performed on the underlying data. Fragmented indexes degrade SQL query performance and can cause FactoryLogix to respond slowly. Reorganizing or rebuilding affected indexes resolves fragmentation.
Update statistics
SQL Server uses statistical information about indexes and column data to determine the most efficient way to retrieve or update data. SQL Server provides two options to keep statistics current: AUTO_CREATE_STATISTICS and AUTO_UPDATE_STATISTICS. It is recommended to enable these options and incorporate them into a weekly or monthly SQL Server database maintenance plan.