Error: Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
While attempting to load your site in a browser the site does not respond for some time and you eventually receive the error above.
There are a number of possible causes for this error, the most common cause is due to your DotNetNuke Site Scheduler being set to Request Method, which causes every enabled scheduled task to run before the site loads every time someone attempts to access your site through their browser.
The scheduler mode on your site must be changed from Request Method to Timer Method to run the tasks at specific time instead of every time your site is requested. You may disable the Scheduler completely to troubleshoot any scheduled task that may be configured incorrectly. Because you are unable to access the site, these changes must be made directly in your site's database. You may do this by following the steps below, which are valid for all versions of DotNetNuke.
If you are not comfortable performing these steps, please contact the support staff for assistance.
These steps require you to have Microsoft SQL Server Management Studio installed on your computer. If you do not have this installed please follow the steps outlined in the following article: How To Connect To Your MS SQL Database.
Always back up the website before making any changes to the database . Shared hosting customers can do this through the Control Panel. Refer to Back Up Your Website Using Plesk. Dedicated server customers can back up the site either through the Control Panel, or through the Control Suite. Refer to How to Back Up a Domain Using Control Suite.
- Open Microsoft SQL Server Management Studio and connect to your database.
- Expand Tables.
- Scroll through the list of tables and right click on dbo.HostSettings.
- In the SettingName column find the Scheduler Mode entry. Change the value in the SettingValue column for this row to one of the following:
- 0 = Disabled
- 1 = Timer Method
- Click out of this row to save the change.
Once the change has been made you will need to restart the application pool of your site for the changes to take effect. If you're unsure of how to do this please refer to How to Recycle the Application Pool Of a Website