AI OnAI Off
This is probably beacause one or more sites on the server have not registered with the scheduler service correctly. How many sites are on the server? According to the logfile there are 2 active sites on the server, are there more?
Not exactly helpful and I havent heard from them since 2nd march. So I have no clue and yet another open ticket to add to the growing list...
maybe if we post our circumstances here we might spot something?
my setup(s):
Machine: win 2000
Site1: upgraded from 3.5, currently running 4.30.
Site2: clean install of 4.30
Site3: clean install of 4.40
Machine: win 2003
Site1: upgraded from 3.5, currently running 4.30
Site2: upgraded from 3.5, currently running 4.30
Both servers have the schedular error in the logfile. The win 2000 machine has the perfmon error(s) even tho I thought I had fixed it.
/John
The EPiServer Scheduler Service does not appear to be active, it may have been stopped. Next job "Publish delayed pages" should have been executed 12.09.2005 04:08:14
Our server is running on Windows 2000 Server SP4.
We have three different episerver sites:
- 4.31
- 4.40
- 4.50
The error mentioned above appears only on jobs on the 4.31 and the 4.40 site, NOT on the 4.50 site.
Also, the following entry can be found in the event log on the server:
Cannot get SchedulerService. Make sure it's started on the localsystem. [Server encountered an internal error. For more information, turn on customErrors in the server's .config file.]
The only way to make it work again, is to restart the EPiServer Scheduler Service.
I have to say this kind of error is quite critical, since the Scheduler is indeed running, but the jobs won't run. This way there is no way of catching the error before actually seeing the error message in admin.
Hope you can help me out.
Frank :)
Cannot get SchedulerService. Make sure it's started on the localsystem. [Server encountered an internal error. For more information, turn on customErrors in the server's .config file.]
This error message appears several times over the last week. But the service was started last time on september 22nd, and has been running since. Also, the Event Log is full of the following entry:10s warning - due time is 23. september 2004 03:00:00
This one seems to be written to the log each time the scheduler is supposed to run, but has failed for some reason. Help, anyone? Frank :)