Skip to main content
Participating Frequently
August 22, 2013
Question

How to keep serving web pages while server is not logged in?

  • August 22, 2013
  • 1 reply
  • 2086 views

ColdFusion 10 works just fine serving pages for our Intranet. Installed on Windows Server 2003 SP2, and previously worked fine with a trial version of ColdFusion MX 7. After the installation of Coldfusion 10, however when the server is logged off, Service is Temporarily Unavailable page is displayed.  Admin console is not available either at the same time. The Cold Fusion 10 Application Server service shows running, but doesn't serve pages. The service has to be restarted, then the pages are served again.

How can we make the application server continue to serve up the Intranet .cfm pages while not logged in to the server?

jcasey1987

    This topic has been closed for replies.

    1 reply

    Inspiring
    August 22, 2013

    Is there any error in coldfusion installation log file, which would be inside Coldfusion10 installation folder?

    Regards,

    Kaif Akbar

    Participating Frequently
    August 23, 2013

    No errors. This only happens when someone sign in on the server at the console, and then logs off.  This does not happen via RDP login/logoff. We were able to recreate the instance with multiple login accounts. Only happens at the console logoff. Remotely restarting the Cold Fusion 10 Application Server service in Windows 2003 will resolve the issue, until the next person logs in on the console of the server.

    Inspiring
    August 23, 2013

    Just to clarify - you are running CF as a service, not manually, correct?  IE, when you look at Start > Administreative Tools > Services, you seen the CF services listed there?  When you do that, what is the login for the CF service?  Is it still the default from installation (built-in service account), or have you changed it to be a user login?  if you have changed it to be a user login, is that the same login as is being used by the people who are logging in to the server?

    If, when you're having the problem of CF not serving up pages, will IIS still serve pages (ie, put an .HTML page out there and try to browse to it)?  This will help to understand where the problem is.

    What about entries in the log files at the time of the logout?  What happens to CF requests that are in progress at that time?  Try writing a CF task that will run for a while, start up PERFMON, start up the request to that long CF task, then do the logout and see if there are changes in PERFMON, or entries in the log files.

    Just some ideas to get us more info to help you out...

    reed