Two error sources are possible:
1. If you are using PostgreSQL the following procedure should fix the problem. There are two relevant configuration files in the directory "data" of the PostgreSQL home directory (for example C:\Programme\PostgreSQL\8.1\data or /etc/postgresql/8.1/main/): pg_hba.conf and postgresql.conf.
In the pg_hba.conf should be the entries of the IP addresses for the Tomcat server and the PostgreSQL server itself under "# IPv4 local connections:", for example:
host all all 192.168.1.1/32 md5
In the postgresql.conf the entry "listen_adresses" should look like the following:
listen_addresses = '*'
After a restart of PostgreSQL everything should work fine.
2. It should be checked, if the WebStart applications are configured correctly. You can find the applications in the "webapps" directory of your Tomcat installation. For the two WebStart applications pragma::tims (directory pragma-tims) and pragma::admin (directory pragma-admin), there could be an error in the associated jnlp-file (tims.jnlp or admin.jnlp). There should be an entry like the following:
<application-descmain-class="com.mceti.tims.sc.TimsLoginDialog">
<argument>192.168.1.1:8080/pragma-tims/</argument>
<argument>192.168.1.1:5432</argument>
<argument>pragma_tims</argument>
<argument>postgres</argument>
</application-desc>
This is the example for pragma::tims. Important are the IP addresses and ports within the <argument>-tags. The first "argument" is the tomcat IP address. The second one is the IP address of the database. Please correct these entries, if needed.
In case the pragma::tims c3 is used the configuration for it can be checked in a similar way. The concerning file is located in <Tomcat-HOME>\webapps\pragma-tims-c3\WEB-INF\web.xml.
Relevant is the entry:
<context-param>
<param-name>server.url</param-name>
<param-value>192.168.1.1:5432</param-value>
</context-param>
The IP address should correspond to the address of the database server.
In case any changes have been made, the Tomcat server should be restarted.