Copy link to clipboard
Copied
I can't get any scheduled tasks to execute on their own. When I run the file from my browser it works fine. I've put a viable username and password (Set by the System Admin.)
The CF/Server specs are Windows 2003, IIS 6, CFMX version 7 7,0,1,116466
This server is behind a firewall and is updated continually with all the IIS security patches etc.
Has anyone had this problem or could offer any suggestions.
Thanks in advance.
Copy link to clipboard
Copied
I fogot to mention that the scheduler log reads:
Apr 19, 2009 | 11:30 PM | Information | 0 | |
[Scheduled task name] Rescheduling for :Mon Apr 20 23:30:00 EDT 2009 Now: Sun Apr 19 23:30:00 EDT 2009 | ||||
Apr 19, 2009 | 6:50 PM | Information | 0 | |
[Scheduled task name] Activating2 on Sun Apr 19 18:50:46 EDT 2009 To run on Sun Apr 19 23:30:00 EDT 2009 |
Copy link to clipboard
Copied
In the schedule task, set a file to store the response, then look at the response.
I suspect you are going to see that the response is a access denied message from IIS.
The MOST common issue for the described problem is Windows Integrated Security in IIS. When you access the page in your windows browser your windows domain username and password are passed to the windows web server and it can validate your credentials and let you access the resource.
CF does not use a windows browser to make scheduled task requests and it can not handle the IIS Windows Integrated Security response headers asking for windows domain creditionals. The user name and password fields in the scheduled task form will only work with basic web site security NOT Windows Integrated Security.
You only options are to use basic web site security OR not use security for the specific code files that you plan to run as a scheduled task. IIS does allow one to set different security options on a file by file as well as directory by directory basis. So it is usually fairily simple to set up a set of files or a directory that uses different security settings then the rest of the site; so that files in that location can be used for scheduled tasks.
Copy link to clipboard
Copied
Ian,
Thanks, this answers my problem conclusively.
However I've been informed by my Sys Admin that they can't use Basic Authentication because in Basic authentication the password is sent in clear text.
Copy link to clipboard
Copied
Spinkick69 wrote:
However I've been informed by my Sys Admin that they can't use Basic Authentication because in Basic authentication the password is sent in clear text.
That is true, but this can be mitigated by configuring SSL so that the clear text is encrypted at the TCP/IP level. But this is the nature of Web Site security. There are limitations on all possible choices.