November Happy Hour will be moved to Thursday December 5th.

Scheduler cant wake site

Vote:
 

My EPiServer version: 5.2.375.236

When anonymous access to a EPiServer site isn't allowed in the IIS, the scheduler cant wake the site. This happen when the sites application pool is shutdown/recycled. Default settings for the applicationpool:
Shutdown: 20
Recycle: 1740

As soon as someone browses the site and wakes it, the scheduled jobs are run.

The Scheduler log sais:

[2010-06-01 19:34:53UTC] #INF# [_LM_W3SVC_207710262_root] Site down for 10+ minutes, open http://wwwtest.orebroll.se/
[2010-06-01 19:35:53UTC] #INF# [_LM_W3SVC_207710262_root] Failed calling site (Attempting to deserialize an empty stream.)
[2010-06-01 19:36:53UTC] #INF# [_LM_W3SVC_207710262_root] Failed calling site (Attempting to deserialize an empty stream.)
etc............................................

The IIS log sais: 401 2 (when the Scheduler tries to wake it)

I want to disallow anonymous access. We have a domain account as identity for the applicationpool. Maybe I have to change the identity for the Scheduler service to this account to?

Any solution to fix this problem?

/Hans

#42032
Aug 06, 2010 10:15
Vote:
 

The scheduled job will by default execute as a non-authenticated user. You'll need to impersonate a user that has access to make it work.

#42048
Aug 06, 2010 12:35
Vote:
 

Yes, a scheduled job executes as an anonymous user, but thats not my problem. http://tedgustaf.com/en/blog/2008/8/run-a-scheduled-job-as-a-specific-episerver-user/

My job should run every nigth 3.00. At this time no one have browsed the site for a while so the applicationpool has recycled it and its not waken. The Scheduler tries to wake it to find out what jobs to run but it cant because anonymous access is not checked for the site.

/Hans

#42123
Aug 09, 2010 16:51
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.