PurgeModuleCache may have been fixed but it appears in PurgeOutputCache in 5.5

AssemblyVersion: 5.5.0
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 3fb959b8-6cef-45eb-bff5-e6ecdfc7f65a
InnerException: Access to the path 'Cache\Pages\' is denied.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.IO.__Error.WinIOError
StackTrace:
Message: System.UnauthorizedAccessException: Access to the path 'Cache\Pages\' 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.Professional.Providers.OutputCachingProviders.FileProvider.FileProvider.GetCacheFolder(Int32 portalId) at DotNetNuke.Professional.Providers.OutputCachingProviders.FileProvider.FileProvider.PurgeExpiredItems(Int32 portalId) at DotNetNuke.Services.OutputCache.PurgeOutputCache.DoWork()
Source:
Server Name: <myserver>

---

Dwayne J. Baldwin

I'm not really sure when this started or which version upgrade caused this. I do recall disabling the scheduler sometime this year, then after upgrading to 5.5.0 PE I looked into the issue.

Since no portal id is reported I am wondering if expired or unused portal(s) may be the actual cause. I would like to delete the expired/unused portal(s) but my requirements are to keep them available if needed.


 

---

Dwayne J. Baldwin

 DNN does not write out to that path.
That is more likely to be .NET using that path
Are you by chance running 32 bit apps on a 64 bit machine?

---

Ken Grierson
DotNetNuke Corporation
Test Lead