We have been successfully running and accesing Servoy Servor 3.5 on a Windows 2000 server platform. Recently, we uninstalled version 3.5 and put up version 4.0 on the same Windows 2000 server platform. Now, we cannot connect to the RMI start port 1099.
If we try to check out a solution on the Windows server platform using Servoy Devloper (locally or remotely) we get the following error message:
Cannot get solutions from: IPAddressOfOurWindows2000Platform
Exception creating connection to: IPAddressOfOurWindows2000Platform; nested exception is:
java.io.IOException: Connect refused: connect
The web interface to Servoy Server works (port 8080), enabling us to view its network settings. The RMI port is set to 1099 (servoy.rmiStartPort: 1099). However, if we try to telnet to this port on the server (locally or remotely), we cannot establish a connection. Other telnet connections work fine. Using the NETSTAT -a Windows command on the server, we do not see port 1099 being used at all (Servoy not listening on this port), however, we do see other ports such as 8080 and 2638 being used. We don’t have port 1099 blocked in a firewall or any other place that we know about. It should be working.
I meant “[your_installation_dir]/application_server/servoy_log.txt”.
Sry for not specifying.
In order not to paste all of it (don’t know, might be big) you can stop the server / delete the log / restart server / reproduce bug then send the contents of that file.
These are the only two lines in the ‘servoy_log.txt’ file even after I just now reproduced the error using a remote client (Servoy Developer):
STATUS | wrapper | 2008/08/20 15:28:01 | Servoy Application Server removed.
ERROR | wrapper | 2008/08/20 15:28:01 | CreateService failed - The specified service has been marked for deletion. (0x430)
The Windows server platform is running Servoy Developer locally, and there is a red-yellow-orange lighning bolt icon in the Windows System Tray. I can connect to the Servoy Server remotely using port 8080 in Internet Explorer. I thought (incorrectly?) that this meant Servoy Server was running…am I mistaken?
On the server side you must run Servoy server, not Servoy developer.
In case of 4.0, developer will/can only launch development clients (web/smart) and ony one instance of each type.
What you have to do is commit solutions that you want available on the server using the Servoy team operation from developer.
You can do this in two ways:
Using developer on the server machine with admin setting “servoy.application_server.startRepositoryAsTeamProvider=true”. This way you can commit the solutions to “localhost”.
Using developer on another machine with admin setting “servoy.application_server.startRepositoryAsTeamProvider=false”. This way you can commit solutions to your server remotely (using the ip/hostname of the server and user/password).
Tell me how it works .
BTW the red-yellow-orange lighning bolt icon in the Windows System Tray is probably the Sybase database server Servoy will connect to (the developer starts it).
I discovered that the Servoy Application Server was not running as a service, even though I checked the ‘Windows Service’ box during installation. I manually added it by entering the following command from the ‘service’ sub-folder: