Hi there, I've been getting a strange problem over the last week or so where a couple of my sites have crashed with the follow error displayed when I turn off custom error messages: "Exception of type 'System.OutOfMemoryException' was thrown."
This seems to generate a cluster of exceptions is the event viewer, one of which is:
2/25/2013 12:03:18 PM Scheduler Event Failure THREAD ID: 147; TYPE: DotNetNuke.Modules.News.Background ...
THREAD ID: 147
TYPE: DotNetNuke.Modules.News.BackgroundLoader
EXCEPTION: Access to the path '\Cache\' is denied.
RESCHEDULED FOR: 25/02/2013 1:03:18 p.m.
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 1
FREE THREADS: 0
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 1
IN QUEUE: 9
Server Name: WINPLESK7
This is preceeded by:
2/25/2013 12:03:18 PM General Exception AssemblyVersion: 5.6.3; PortalID: -1; PortalName ...
AssemblyVersion: 5.6.3
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 9b7dcd5b-9d84-47fe-b8e8-3e1e81ec6dbf
InnerException: Access to the path '\Cache\' is denied.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.IO.__Error.WinIOError
StackTrace:
Message: System.UnauthorizedAccessException: Access to the path '\Cache\' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity) at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity) at DotNetNuke.Modules.News.BackgroundLoader.DoWork()
Source:
Server Name: WINPLESK7
this appears to be an permissions error but my hosting company checked the permissions and they were OK. they even reapplied them to be sure. The two sites that went down are on the same server, one running 5.6.3 and the other is running 6.2.3
The sites come back online when the app pool recycles. Also they run on different instances of SQL server.
Any advice on what could be going on would be appreciated
Andrew