Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsNews FeedsNews FeedsAccess to the path Access to the path '\Cache\' is denied after installing 4.1.0
Previous
 
Next
New Post
3/11/2011 6:52 PM
 
I upgraded to News Feeds 4.1.0 and following that I get a scheduler error that seems to involve background loading. Here is the log entry:

THREAD ID: 16
TYPE: DotNetNuke.Modules.News.BackgroundLoader
EXCEPTION: Access to the path '\Cache\' is denied.
RESCHEDULED FOR: 2/24/2011 5:47:01 PM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 7
Server Name: WEB4006

This error occurs in the log about every hour. It is followed withing a few seconds by another error entry:

AssemblyVersion: 5.6.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 12599828-a7cc-4065-b2d3-c7a237c61f02
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: WEB4006


The above error is then sometimes followed by this timeout error:

AssemblyVersion: 5.6.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: c6b66883-d042-43e1-8eb3-917701f9c607
InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.ReaderWriterLock.AcquireReaderLockInternal
StackTrace:
Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireReaderLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.get_ScheduleInProgress()
Source:
Server Name: WEB4006


I like the background load feature very much, but how can I eliminate these errors? There is no '\Cache\' directory. Should I create one?

Thanks.


 
New Post
3/12/2011 12:54 PM
 
I created a /Cache directory in the web root to see if the errors would go away. They did! However, two other errors appear now, although not as frequently. The two errors occur at the same time-stame, and are almost the same, except for the last line of the Message at the bottom of the error. The first is a "CoreScheduler.get_ScheduleInProgress" and the second is a "RemoveFromScheduleInProgress".

First error:

AssemblyVersion: 5.6.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 18b2b9b5-b9a8-49ed-bfa3-0b86b1b2a6c3
InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.ReaderWriterLock.AcquireReaderLockInternal
StackTrace:
Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireReaderLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.get_ScheduleInProgress()
Source:
Server Name: WEB4006

Second error:

AssemblyVersion: 5.6.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: c4cdafe9-143f-49c9-a4dc-0b90b301f018
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.RemoveFromScheduleInProgress(ScheduleItem objScheduleItem)
Source:
Server Name: WEB4006

I don't think I should have to create the \Cache directory manually, so something's not right in either the install script or the code, yes?

Any ideas? Thanks.

 
New Post
3/12/2011 1:18 PM
 
I now realize that the first new error above is not new because it is the same as the less frequent error I listed in the first message of this thread.

Also, in looking back into the log, I found another message about the Cache directory:

THREAD ID: 9
TYPE: DotNetNuke.Modules.News.BackgroundLoader
EXCEPTION: Could not find a part of the path 'C:\Cache\Feed_998.resources'.
RESCHEDULED FOR: 2/25/2011 9:25:16 PM
SOURCE: STARTED_FROM_TIMER
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 8
Server Name: WEB4006

This is really strange that it would be looking for the C: drive. A message before installing the 5.6.1 upgrade and this 4.1.0 module said this about a cache error:

InnerException: The process cannot access the file 'E:\Inetpub\Clients\sitenamehidden\wwwroot\Portals\0\Cache\Feed_583.resources' because it is being used by another process.

So, I would think that should be the path, not the C:\Cache\ path.

Check your logs. Are you getting this error too?

 
New Post
3/14/2011 3:03 PM
 
I traced the timeout errors back using the timestamps and the schedular log, and it appears that they are not related to the Background Loader of News Feeds. The times that the timeouts occurred do not match when the schedular was running the Background Loader. So that's another issue.

However, during the investigation, I noticed that the Background Loader was doing some work for another portal that was now obsolete and was just being retained for reference. Since the Load in Background option is selected by default when upgrading to this latest version, that portal got the new background loading feature. So I went into that portal and unchecked the Load in Background feature for all of the news feeds. That produced the \Cache\ error in the log again:

TYPE: DotNetNuke.Modules.News.BackgroundLoader
EXCEPTION: Access to the path '\Cache\' is denied.

This is even though the \Cache\ directory I manually created is still there. The only thing I can think of is that it is still trying to access C:\Cache\, while this site is on E: and not in the root of E:.

Also strange, is that I checked another site that I put the news feed on, on another server, and it seems to be working fine. I can't imagine how this particular upgrade could have gotten the Cache directory path wrong if the other site upgrade got it right!


 
New Post
3/17/2011 8:48 PM
 
I have now upgraded another site to DNN 5.6.1 from 5.6.0 and upgraded the News Feed module from 4.0.1 to 4.1.0. Everything works fine, except when I decided to turn off Background Download on one of the News Feed modules, I got the Cache error again, except this is a different site.
Here is the first error:

AssemblyVersion: 5.6.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: ef9e4282-bf8c-4586-95f1-c5466159cbbe
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: SERVER29

Followed by a second error:

THREAD ID: 15
TYPE: DotNetNuke.Modules.News.BackgroundLoader
EXCEPTION: Access to the path '\Cache\' is denied.
RESCHEDULED FOR: 3/16/2011 8:50:26 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: SERVER29

So, this apparently happens when you change the Background Download setting. I don't know why or how to avoid it.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsNews FeedsNews FeedsAccess to the path Access to the path '\Cache\' is denied after installing 4.1.0


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out