TYPE: DotNetNuke.Services.Cache.PurgeCache
EXCEPTION: Could not find a part of the path 'c:\windows\system32\inetsrv\Cache'.
RESCHEDULED FOR: 7/17/2011 5:31:48 PM
SOURCE: STARTED_FROM_TIMER
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 6
Server Name: xxxxxx
There is no path 'c:\windows\system32\inetsrv\Cache' on our server, do we need to add this? How do you fix this?

I suggest switching scheduler to request mode in Host Settings.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Hello,

I tried the proposition (request mode). Unfortunately, I still have the same issues:

THREAD ID: 21
TYPE: DotNetNuke.Services.Cache.PurgeCache
EXCEPTION: Could not find a part of the path 'c:\windows\system32\inetsrv\Cache'.
RESCHEDULED FOR: 9/4/2011 9:17:19 AM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 6
Server Name: GENERIC1

I asked some support to Power DNN (my hosting provider). In the past, I was very very satisfied with Power DNN and their support, but since few days, the answer are rather strange....
I had the answer that they would prefer to do the upgrade themselves, to be sure that everything is OK... Since I done it myself, they are not sure that I done it correctly, they are not sure that I did not have any error message during the upgrade, and so on. They propose two solution, one solution = roll back to V4 and they do the upgrade themselves (only core DNN and then I solve the problem which might happen), another solution is to let them do everything (it cost a lot).

Of course, none of the solution above give me satisfaction, I would rather prefer they trust me when I explain how I did the upgrade, and they try to understand the reason of this error message, instead of thinking that upgrading themselves will solve the problem (I am not alone, since I see other people having the same issue).

In addition, I do not have the lowest hosting package...

Well, let's go back to our issue, if anybody has an idea ?
DV FX