The RMI registry seems to be the problem. I can't seem to get the run_protege_server.bat script to start the rmiserver process. I tried several variants of the bat file - even hard coding the path to rmiserver.exe and still it wouldn't run. I ended up creating a seperate batch file to fire up the rm...

Normally I am pretty good with these things,but I must have missed a step? I can't fire up the Essential server for multi-user on Windows Server 2003. No local firewall running. It fails with the following stack trace. What service is it trying to connect to? The Web app is deployed w/o a hitch. -- ...