CF MX6.1 will not auto start after server reboot.. but will start by hand...

[Noël®]

I just moved all the stuff to a new dual Xeon Windows server 2003.

Problem with CF MX 6.1 is that it will not start after a server reboot!
I get an Application error message like this:

Event Type: Error
Event Source: ColdFusion MX Application Server
Event Category: None
Event ID: 261
Date: 2/16/2005
Time: 12:14:18 AM
User: N/A
Computer: XEON
Description:
The ColdFusion MX Application Server service could not be started within 240
seconds. Increase the server startup timeout value using
C:\CFusionMX\runtime\bin\jrunsvc.exe -starttimeout <seconds> "ColdFusion MX
Application Server".

and

Event Type: Error
Event Source: ColdFusion MX Application Server
Event Category: None
Event ID: 263
Date: 2/16/2005
Time: 12:14:18 AM
User: N/A
Computer: XEON
Description:
The ColdFusion MX Application Server service killed process with pid 1556.

In the System log I have the following error:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 2/16/2005
Time: 12:14:18 AM
User: N/A
Computer: XEON
Description:
The ColdFusion MX Application Server service terminated with
service-specific error 2 (0x2).

For more information, see Help and Support Center at
[url]http://go.microsoft.com/fwlink/events.asp[/url].


The strange thing is that when I start the ColdFusion MX Application Server
service by hand in "Services" (after the error) it will startup nice with no
problem.

Anyone here who knows of a fix for this?

Thank you..

Noel

[Tom Jordahl]

> The ColdFusion MX Application Server service could not be started

> within 240 seconds. Increase the server startup timeout value using
> C:\CFusionMX\runtime\bin\jrunsvc.exe -starttimeout <seconds>
> "ColdFusion MX Application Server".

Noel,

The error message told you how to fix it - you can increase the startup time
by changing the command that is run when the service starts up. I *think*
you can do that from the control panel, but you may have to find it in the
registry.

This is probably because your machine starts up so much 'stuff' at once that
it takes longer than 240 seconds to start CFMX. That seems strange since it
sounds like you moved to a faster machine. You might want to check to see
what is running on it.

--
Tom Jordahl
Macromedia

[Noël®]

"Tom Jordahl" <tomj@macromedia.com> wrote in message
news:cuvjvs$r9$1@forums.macromedia.com...

>> The ColdFusion MX Application Server service could not be started
>> within 240 seconds. Increase the server startup timeout value using
>> C:\CFusionMX\runtime\bin\jrunsvc.exe -starttimeout <seconds>
>> "ColdFusion MX Application Server".

>
> Noel,
>
> The error message told you how to fix it - you can increase the startup
> time
> by changing the command that is run when the service starts up. I *think*
> you can do that from the control panel, but you may have to find it in the
> registry.
>
> This is probably because your machine starts up so much 'stuff' at once
> that
> it takes longer than 240 seconds to start CFMX. That seems strange since
> it
> sounds like you moved to a faster machine. You might want to check to see
> what is running on it.
>

Hi Tom,

Thanks for your reply.

Bob (in an other group) pointed me to the following link:
[url]http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_18799[/url]


Still it's strange.. I moved from a single CPU server (1.4 GHz) to a dual
Xeon 2.8 GHz one.
The setup (servers running) are the same as it was on the "old" server.
Both systems were running Windows Server 2003 and had 1GB mem.

Only difference is that the new server is getting +60K hits a day, but this
should not effect the startup time

Noel