Unhandled Error

Since you can open some of the site's pages, my guess is that the timeout issue is being caused by the site's database having grown in size to the point that it cannot be accessed in a timely fashion. Most often the growth occurs in the EventLog table and possibly the SiteLog table if there are many users logging in or errors are being generated and logged.

If you have access to the database using SQL Server Management Studio, open the database and check both of those tables. If there are many rows in either, you will need to execute a Truncate Table command to clear all of its data. In addition, the SQL server log for the database may be filling up and will need to be truncated and backed up. Before truncating the EventLog table, I would also take a look at the Properties field of its recent entries to determine if errors are being logged repeatedly. Unless you are comfortable with performing those operations on the database, please seek more assistance.

Once you have corrected the timeout issue and able to log into the site as host, be sure to check the scheduled tasks (Host-->Schedule) which automatically deletes older entries to the EventLog and SiteLog tables to make sure that they are enabled and running regularly.

 

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner