Ok, the next time was sooner than I thought. Got home 4 hours later and had a message from my user that their site was down again with the same issue I posted below. Tried the DEBUG -> True then DEBUG -> false and the site came up but that is not going to be the solution that sits well with the client. When I did get back in, I went to the event viewer and it did not indicate much about that error but had 204 pages of the following errors. Related (?)
AssemblyVersion: 5.6.0
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 6783a826-2c04-45d0-a599-3b4cde819354
InnerException: String reference not set to an instance of a String. Parameter name: s
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.DateTimeParse.Parse
StackTrace:
Message: System.ArgumentNullException: String reference not set to an instance of a String. Parameter name: s at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles) at DotNetNuke.Services.ModuleCache.FileProvider.IsFileExpired(String file) at DotNetNuke.Services.ModuleCache.FileProvider.PurgeExpiredItems(Int32 portalId) at DotNetNuke.Services.ModuleCache.PurgeModuleCache.DoWork()
Source:
Server Name: P3NW8SHG105
THREAD ID: 10
TYPE: DotNetNuke.Services.ModuleCache.PurgeModuleCache
EXCEPTION: String reference not set to an instance of a String. Parameter name: s
RESCHEDULED FOR: 1/31/2011 7:35:42 PM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 5
Server Name: P3NW8SHG105
