Servoy Application Server

Server doesn't start

When the Servoy Application Server will not start, there are two likely reasons for it:

...

The Servoy Application Server is very robust and is known for its stability and extreme long uptime. In the unlikely event of a crash, this is most likely caused by an out of memory exception, caused by 

Servoy Smart Client

When experiencing problems with Smart Client starting or loosing connections, the following items might offer resolution. At any time, more information can be retrieved by enabling the Java WebStart console on the client machine prior to launching the Smart Client. This will open an additional console on the client machine with a client-side log. The Java WebStart console can be enabled in the Java Control Panel > Advanced > Java Console by checking the Show console option

...

Solution issues

----------------------

Other

...

Database Connectivity

General

Servoy comes bundled with a limited set of JDBC drivers, due to licensing. For example, we are not allowed to ship JDBC drivers of Oracle or the official Microsoft SQL server JDBC driver. See the database section of the Servoy stack info for a list of the shipped JDBC drivers. If the 

Oracle

When connecting to Oracle databases, make sure to use the correct version of the Oracle JDBC driver. Each oracle database version has it's own version of a JDBC driver and when connecting to Oracle with a JDBC driver that was meant for another version of Oracle, the results can be mixed  

...

Servoy doesn't see the tables in the database

...

Most likely cause is the 'Schema' property for the connection. This property must be set to the appropriate 'Schema' in the Oracle database. The value for the 'Schema' property must be all uppercase when connecting to an Oracle Database.

SQL Server

...

Failed to establish a connection

...

In order to connect to SQL Server using JDBC, the TCP/IP option of SQL server needs to be enabled, which it isn't by default. If this is the case, a error similar to the following can be found in the log: "com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed."

MySQL