Server will not start but portal still works

[Former Member]

We have an EP6 SP2 system with the dispatcher and a single server set up to run as Windows Services (Win 2003). Starting the Dispatcher works fine, but starting the Server starts and immediately stops with a nothing to do message.

But the portal works!

Looking at the task list we have dispatcher.exe and java.exe running quite happily.

Anybody any idea why this is happening the way it is? It's running the 6.20 J2EE and I've corrected a few settings since getting access (path etc). Apart from a trex glitch displaying index properties and only indexing title and description everything works quite happily for 80% of the time.

This is the first time I've been stuck trying to work out why something is working instead of where it's broke

-Richard

[Former Member]

D'oh! Of course. Should have known that.

Thanks Marty & Boris

-R

[MartyMcCormick]

Richard,

This has been happening because the dispatcher has the R3Startup service set to Automatic. The R3startup service automatically starts the server node (hence why you cant start the server via the Services).

To change this, go into configtool and under dispatcher services, change the r3startup service to manual.

Then you will be able to start both services independent of each other.

Regards,

Marty

[boris_tsirulnik]

The dispacher is configured by default to start the server (using r3startup service).So you don' need to start the server by yourself.

When you try to start the server manually you probably see this error message:

Loading: ClusterManager ...

[ClusterManager]: ID000460: Can't open port 50020

Loading: ClusterManager returned false!

Kernel not loaded. System halted.

This means that the server is already running.