If you should receive an error message please pay attention to the chapter error codes.

 

Problem: Server does not start or the service can not be started

Solution: Check in the licence overview if the licence information is available and still valid. Make sure that you have not accidentally installed the licence of the client. If you should have filed the licence file on a network share, copy it to an off line directory. Afterwards reload the licence file and start the server.

 

Problem: No access to the databases (Windows XP SP 1)

Solution: If the server runs under Windows XP SP 1, databases that lie on a network share can possibly not be recognized. Update to the Windows XP Servicepack 3.

 

Problem: No access to the databases

Solution: If a connection with the database is not possible, it could be possible that the firewall has not been configured yet. Please check the database firewall or deactivate it if necessary.

 

Problem: No access to databases in the network share

Solution: Check the file and unblocking rights for the directory and for the database file. The service that accesses the database files will be run as a "off line system account" which has got no right to network resources. To be able to use databases from a network share, you have to accordingly configure the service (login). Make sure that the registered user has got enough rights (start and stop services), as well as writing access to the network share directory. Furthermore you should make sure that the database files are not "write-protected" or "hidden". Please also note that only a Windows network share is supported. Linux network shares are not supported..

 

Problem: No connection from client to server possible

Solution: Make sure that your Firewall admits of the connection, that the ports are not used already and that the server is accessible. The protocol is based on UDP. So please unlock port 12008 for TCP in the Firewall. Furthermore you should check if the parameters have been entered correctly to exclude typing errors. With some networks the "host" can not be unlocked if it is used as the server name. Use the same descriptions at the server "host" and at the client "server IP".

 

Problem: No connection to the server

Solution: Check the connection settings, especially the server ID. These have to match exactly.

 

Problem: Clients crash sporadically

With very restrictive Firewalls it is suggestive to deactivate the option "PingClients". You can find this option under "edit" -> "server options" -> "connection parameter".

 

Problem: The configuration user interface reports an error "gdiplus.dll not available"

Solution: Under Windows Server 2000 the file "gdiplus.dll" has to be installed again possibly, provided that it is not available. You can receive the file directly from Microsoft or also via google search.

 

Problem: No connection is possible after the software update

Solution: Please check the service (login). After the reinstallation/update of the server the services will be reset to the standard login (off line system account). Therefore there is no access to databases which are filed in a network share.

 

Problem: The server password is no longer accepted

Solution: If the hardware of the server is changed (for example a second CPU is assigned to a virtualized server) all passwords (client server connection password, database password, etc.) have to be set again. Furthermore we also suggest to set the passwords again at the backup and task service. Afterwards please check if the backup is created free from errors after the change of hardware.

 

Problem: Why is error code 17 displayed when I access the database?

Solution: The error code 17 says that no communication between client and server is possible. Check your network firewall and configure it in a way that the server port (by default 12008 TCP) is activated. You can find further information in the chapter error codes

 

Problem: The backups do not run, error code 17 is displayed, however, the clients can connect. How can this be?

Solution: Check in the server parameters if the IP address of the server is entered properly.

 

Problem: Despite the fact that obviously everything is configured properly, the client cannot log on at the database and receives the error code 17. How can this be?

Solution: In this case probably a local multiuser database runs on the accordant client which blockst he server port. Close this database or change the server port at the server.

 

Problem: When I acitvate the database firewall no login is possible and the error code 23 is displayed. What can I do?

Solution: Check if the accessing computers have been adapted in the firewall rules. You can find further information in the chapter firewall

 

Problem: Why do backups with error code 23 abort?

Solution: Check if the IP address of the server is activated in the firewall rules.