Skip to main content
Inspiring
April 9, 2008
Question

Scheduled job won't run

  • April 9, 2008
  • 4 replies
  • 570 views
I have a procedure to run once a night. Currently it runs on W2K server with MSIE 6 and CFMX7. Company wants to upgrade server to 2003 and MSIE7 CFMX7. However this scheduled job now won't run. I get a CONNECTION FAILURE everytime.
It will run locally if I browse to the file and it will run over the intranet. BUT it won't run when called from the scheduled tasks.
I ran a simple cfhttp call and rec'd the error "connection failure: Status Code Unavailable"
So is there any security settings or anything that block cfhttp calls?
    This topic has been closed for replies.

    4 replies

    Inspiring
    April 14, 2008
    Dinghus wrote:
    > What port does the scheduled task try to use by default? I'm thinking the port is blocked.

    A scheduled task is just an HTTP|HTTPS request. So the normal ports of
    80 and|or 443 unless something is unusual in your setup.

    DinghusAuthor
    Inspiring
    April 14, 2008
    What port does the scheduled task try to use by default? I'm thinking the port is blocked.
    DinghusAuthor
    Inspiring
    April 9, 2008
    Hmmm that still doesn't work. I still have the cfhttp throwing a connection failure too.
    I don't think this has anything to do with the scheduler, but instead with cfhttp security of some sort.

    Is it possible, in the security settings somewhere, to lockout a cfhttp get?
    Inspiring
    April 9, 2008
    Dinghus wrote:
    > I have a procedure to run once a night. Currently it runs on W2K server with
    > MSIE 6 and CFMX7. Company wants to upgrade server to 2003 and MSIE7 CFMX7.
    > However this scheduled job now won't run. I get a CONNECTION FAILURE everytime.
    > It will run locally if I browse to the file and it will run over the intranet.
    > BUT it won't run when called from the scheduled tasks.
    > I ran a simple cfhttp call and rec'd the error "connection failure: Status
    > Code Unavailable"
    > So is there any security settings or anything that block cfhttp calls?
    >


    Yes, eight out of ten times that you can personally browse to a resource
    that is unavailable when accessed as a schedule task or with <cfhttp...>
    is because of Windows Integrated Security.

    Your browser can pass your domain creditionals to the server, quietly
    behind the scenes if you use a Windows Browser, and the server lets you
    access the resource. The basic, built in browser ColdFusion uses to
    make schedule task and <cfhttp...> request, can not respond to Windows
    Integrated Security requests from the server and the connection fails.

    Solution: Disable Windows Integrated Security on a resource required to
    be accessed internally by ColdFusion. The Security settings in IIS can
    be configure as broadly as an entire website or as narrowly as a
    specific directory or even individual file. Thus you can disable this
    setting on the specific file without opening up the entire website.