Hi Kevin,

I just checked the event viewer on my server. and noticed that I haven't received these messages lately. Now I'm thinking about it, I haven't restarted IIS manually in ages!

In a previous post within this thread I discussed what Ithe problems may be. And I do believe it is a performance issue and not a DNN specific software problem perse. 

Here a recap on what I believe the problem is:

The more users online -> The more data is requested -> The more queries are executed -> The more low level hardware I/O operations on the server's HDD need to be performed -> the higher the propability a requests times out, i.e. a query takes too long too execute within a set time limit because the disk is too fragmented and or the database is not indexed -> an error is produced...

I looked it up on the internet and found this relating article; Performance Tuning

So do the following with your DNN / SQL server tokeep the servers lean and mean!

• Index the SQL database often,
• Defragment the HDD often!
• And turn off the logging by IIS.

You can use maintenance plans for SQL server and scheduled batch scripts for IIS log files and defragmentation of the HDD.

Of course this doesnt mean I don't have any errors, I have some but these are a bit different and not of the cannot load type or other timeout related errors by DNN. .

Hope this helps.

Greetings, 

I had a host logon active overnight, when I clicked on the dotnetnuke site in the morning - we got this strange out of bounds error.  We are hosted on GoDaddy, so IIS access was not an option.  Your suggestion to change a character in the web.config file did the trick!!!  I've seen other reports of this problem outside of dotnetnuke, it may have to do with ASP.NET 2.0 and IIS, not sure.