OK Guys and Gals.

I've hit a brick wall with my clients site.

From time to time over the past two months with development of my clients site, i have seen errors from time to time. Most I am able to figure out what they are, fix and resolve. But now I've got errors that I can't resolve and can't understand.

First off, here are the server specs. The server is running at RackSpace as one of the Cloud Server options, running 4gb of ram and 190gb of HD Space. We are not using any webfams or cloud technologies though for the DNN Installation. At normal operation server is running at only 20% memory consumption and pretty much no CPU usage.

Windows Server 2008 R2
Microsoft SQL Server Express 2008
.net 4
IIS 7.5

The configuration for the connection string is <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Initial Catalog=dnn;Integrated Security=True" providerName="System.Data.SqlClient" />

It has it's own app pool with "NetworkService" as it's identity running .NET framework v4.0.30319 and integrated for its managed pipeline mode

I know some special things were done by my indoogrid developers in order to have SSMS be able to access the attached database.

The DNN Version is 05.05.01 (22) Community Edition

ANy other questions regarding the setup I am happy to give. I am getting errors regardless of whether I am using a software to load test or just browsing the site on my own. But to give a hint in a nutshell whats going on with the server I get 5.9 seconds response under a 10 per load, 7.5 seconds response under 20 person load and 4.9 under a 30 person load and under a 40 person load, the application is barely responding, however cpu for SQL server does not seem too high during this. Now note that this site is supposed to be getting traffic over 4,000 people at a time during peak usage every couple weeks. So if it can't handle 10-40 users at a time, I dont know how it's supposed to handle more then even a few hundred.

Now onto the errors. Unfortunately I had cleared the log of the first set of errors hoping that I had resolved them and when I ran some more load tests to see if I would get anymore, i got more, and allot of new ones. I am getting errors though even under normal usage though right now.

The first error if I remember correctly had to do with there not being an Open space in the application pool. but the second round of tests did not show this error. Also I removed all the modules on the front page except the standard DNN HTML text module to narrow out what might be causing the errors. Also note that I had purged users online, the site log, history, log buffer,  cache, and module cache to make sure it wasn't one of these items. Also note site Log is disable on the site.

Here are verbatim errors from the log.

Two errors of

11/15/2010 11:39:14 PM   Scheduler Exception       AssemblyVersion: 5.5.1; PortalID: -1; PortalName ...

AssemblyVersion: 5.5.1 PortalID: -1 PortalName:  UserID: -1 UserName:  ActiveTabID: -1 ActiveTabName:  RawURL:  AbsoluteURL:  AbsoluteURLReferrer:  UserAgent:  DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID:  InnerException: Collection index must be in the range 1 to the size of the collection. FileName:  FileLineNumber: 0 FileColumnNumber: 0 Method: Microsoft.VisualBasic.Collection.IndexCheck StackTrace:  Message: System.IndexOutOfRangeException: Collection index must be in the range 1 to the size of the collection. at Microsoft.VisualBasic.Collection.IndexCheck(Int32 Index) at Microsoft.VisualBasic.Collection.get_Item(Int32 Index) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.ScheduleInProgressContains(ScheduleHistoryItem objScheduleHistoryItem) in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\Providers\SchedulingProviders\DNNScheduler\Scheduler.vb:line 323 at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleInProgress(ScheduleHistoryItem objScheduleHistoryItem) in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\Providers\SchedulingProviders\DNNScheduler\Scheduler.vb:line 208 at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.WorkStarted(SchedulerClient& objSchedulerClient) in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\Providers\SchedulingProviders\DNNScheduler\Scheduler.vb:line 1235 Source:

And about 100 of these

11/15/2010 11:46:48 PM   General Exception       AssemblyVersion: 5.5.1; PortalID: -1; PortalName ...

AssemblyVersion: 5.5.1 PortalID: -1 PortalName:  UserID: -1 UserName:  ActiveTabID: -1 ActiveTabName:  RawURL:  AbsoluteURL:  AbsoluteURLReferrer:  UserAgent:  DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID:  InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) FileName:  FileLineNumber: 0 FileColumnNumber: 0 Method: System.Threading.ReaderWriterLock.AcquireReaderLockInternal StackTrace:  Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireReaderLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.get_ScheduleInProgress() in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\Providers\SchedulingProviders\DNNScheduler\Scheduler.vb:line 116 Source:

Now, I know I am getting a couple other errors when I have DNN Article module running on the front page, but that I have the feeling will need to be resolved with DNNArrticle ZLDNN. The issues above are issues from a core standpoint.

Let me know what your guys thoughts are, my clients have spent a lot of money on this site and now I have been loosing money several weeks. I am really hoping that choosing DotNetNuke is not going to ruin my business. Site is to go live on December 1st so I'm in a world of hurt if I don't get this resolved soon.

This site will be an awesome showcase of DNN if i ever just get the damn kinks out of it.

Regards,

John M

I have tried disabling schedule tasks one by one, but I still get the errors. The errors come up every time someone views a page now.

John

The same error is being reported in multiple forum threads. Have you tried to recycle the application pool? Does it help?