Chodyra & Company

Information Technology Solutions

Blog

DotNetNukGeneral Exception - AcquireWriterLockInternal Timeout

by Peter Chodyra on Thursday, January 13, 2011 3:27 PM

Have you been seeing this ERROR in your DotNetNuke 5.4+ EventLogs?

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: IIS201101


If you think you tried everything from TRUNCATING your log tables, fixing the SupportedFeature field in the DesktopModules table then try this:

Go to the file system and every portal folder of your website and manually delete the contents of Cache and Modules folders. It seems the cache is not cleared properly and leave rogue references.

Let me know if it worked for you too?

As usual do this at your own risk - best way is to test on a copy of your portal.

Author
Peter Chodyra

With over 20 years of IT Experience I still come across solutions that are not widely known or published. I hope to be able to bring them to the IT community through this blog. Your comments and suggestions are welcome.

Archive

  Go