I just successfully upgraded from CF6 MX to CF8, but am now
having problems executing my scheduled tasks. My environment is
Windows 2003 R2 SP2 (32 bit), Access 2000 (I know), IIS6 and CF8
with cumulative hot fix 3.
Everything is working well except for my scheduled tasks. It is giving the 'Error while executing task 503 Service Unavailable' error message in the scheduler.log, and the generic list of errors on the scheduled task screen.
*The scheduled task is paused
*The URL is a redirection URL.
*The URL is protected by IIS NT Challenge/Response or Apache .htaccess password. The Username and *Password text fields for editing a scheduled task are intended to support Basic Authentication only.
*The Domain Name lookup failed. Try using the IP address of the domain whenever possible.
*The URL is an SSL site, but the SSL port was specified incorrectly.
*The Web site is not responding.
*The directory specified for published results does not exist.
These jobs were converted by the upgrader process, but I have verrified that all the jobs exist in the directory it is pointing to. I am assuming that it might bean issue with the IIS configuration, but am stumpted. Any help is greatly appreciated.
Libby
Everything is working well except for my scheduled tasks. It is giving the 'Error while executing task 503 Service Unavailable' error message in the scheduler.log, and the generic list of errors on the scheduled task screen.
*The scheduled task is paused
*The URL is a redirection URL.
*The URL is protected by IIS NT Challenge/Response or Apache .htaccess password. The Username and *Password text fields for editing a scheduled task are intended to support Basic Authentication only.
*The Domain Name lookup failed. Try using the IP address of the domain whenever possible.
*The URL is an SSL site, but the SSL port was specified incorrectly.
*The Web site is not responding.
*The directory specified for published results does not exist.
These jobs were converted by the upgrader process, but I have verrified that all the jobs exist in the directory it is pointing to. I am assuming that it might bean issue with the IIS configuration, but am stumpted. Any help is greatly appreciated.
Libby