Jul 5

Written by: Chris Miller
7/5/2010 8:06 AM 

Turns out that all four exceptions were timeouts. What would be the object it is failing to lock? What is related to the RemoveFromScheduleQueue method? The error seems like a file system error but the method seems related only to the database. Would rebuilding the database resolve the problem?

7/5/2010 8:58:08 AM   General Exception

AssemblyVersion: 5.4.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: cf2e6fe3-835c-4372-8df1-53e6a23c9619
InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.ReaderWriterLock.AcquireWriterLockInternal
StackTrace:
Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireWriterLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.RemoveFromScheduleQueue(ScheduleItem objScheduleItem)
Source:
Server Name: IIS08402