Differences
This shows you the differences between two versions of the page.
an_error_has_occurred_while_executing_queries._timeout_expired [2019/01/27 11:28] |
an_error_has_occurred_while_executing_queries._timeout_expired [2019/01/27 11:28] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== | ||
+ | |||
+ | |||
+ | |||
+ | ===== Error Message ===== | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | ===== Explanation of Error ===== | ||
+ | |||
+ | |||
+ | |||
+ | This error can occur at almost any time, but occurs most commonly when attempting to create/ | ||
+ | |||
+ | |||
+ | |||
+ | The general cause of any " | ||
+ | |||
+ | |||
+ | |||
+ | ===== Severity ===== | ||
+ | |||
+ | **Normal**. This error may result in the loss of new data or just be an annoyance while searching for information. | ||
+ | |||
+ | |||
+ | |||
+ | ===== Possible Root Cause(s) ===== | ||
+ | |||
+ | |||
+ | |||
+ | The most common causes of " | ||
+ | - A report executed within Control (by that user or anyone else) is causing a lock to occur on the SQL tables. | ||
+ | - The system resources of your server computer (memory and hard-drive space, for instance) may have been fully consumed by other applications or services which causes a timeout to occur due to Microsoft SQL Server' | ||
+ | - The database may have reached the maximum size allowed if you are using one of the free versions of SQL Server such as MSDE or an SQL Server Express. | ||
+ | - Another user may be performing a specific task in Control which has caused the SQL database tables to enter a locked state. When these tables enter a locked state all reads and writes to those tables are unsuccessful and can result in the error message received. | ||
+ | |||
+ | |||
+ | |||
+ | ===== Resolution ===== | ||
+ | * If this is the first occurrence of the error, Check the amount of free memory by examining Task Manager. | ||
+ | * If you are encountering the error frequently, on the next occurrence ask all other users of Control to track what reports they are printing. | ||
+ | * Ensure the specifications of your server meet at least the minimum requirements. Keep in mind that the minimum requirements assume that you are using your server solely for housing the Control application. If you are using your server for additional tasks be sure the server has adequate resources (memory, cpu, hard drive space) to handle the additional tasks you require it to handle. | ||
+ | |||
+ | |||
+ | |||
+ | ===== Additional Information ===== | ||
+ | |||
+ | |||
+ | |||
+ | It is possible //in some cases// to insert the data from the SQL timeout error back into the database. For example, if the user was in the process of saying a large estimate or order and encountered this error there is a chance you can recover that information for them. __These steps are only recommended for users who have a thorough understanding of managing Microsoft SQL Server databases.__ | ||
+ | * Locate the SQLError file. The default location for any SQLError file for Control is | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | * Have all users close Control and shutdown the SSLIP. | ||
+ | * Create a backup of the SQL database for Control. | ||
+ | * Open SQL Management Studio and paste in the contents of the Control_SQLError.txt file except for the first 4 lines which contains the header information as shown below into a Query Window for the Control database. | ||
+ | * // | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | * In this example the first line you would paste into the Query Window would be | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | * Execute the query to restore the data that was lost due to the SQL Timeout error. | ||
+ | * Launch the Cyrious SSLIP and log into Control to verify your changes were properly posted. If you encounter any errors or problems related to this query you should restore the backup you created prior to starting. | ||
+ | |||
+ | |||
+ | |||
+ | ===== Version Information ===== | ||
+ | * Version(s): All versions of Control. | ||
+ | |||
+ | |||
+ | |||