Back to website >

Timeout for SQL commands

There are two large areas for timeout error messages. In principle, timeouts are useful, since operations that take considerably longer than planned can be terminated as a result. Whenever a process has to wait for another process, the timeout is the possibility to log out of the wait. Usually EULANDA® is the main process and the SQL server is the process that is usually waited for. However, there are situations in which the timeout unexpectedly comes too early and the process is not completed as a result.

  • Timeout Due to an operation that is too complex (command timeout)
  • Timeout for normal processes (connection timeout)

Timeout Due to an operation that is too complex

If a timeout occurs during complex operations, such as importing or converting large data sets, it can be assumed that the SQL server is too weak. Above all, a sufficiently large main memory in the server is important. The minimum size is 4GB, but the expansion may require 8GB or more, depending on the number of workstations and the volume of data. EULANDA® has set the command timeout to several minutes for this special timeout problem, especially for very complex operations. If the error occurs in statistics, etc., the server should be extended.

Timeout for normal processes

A timeout error occurs when accessing the data, starting the program or printing. This is a connection timeout.

EULANDA® establishes a new SQL connection to the server for different operations, but this does not respond to the request of a new connection.

The cause is to be found here in the operating system and the installed components. By default, the TCP/IP protocol is used for communication between workstation and server. Some programs, such as Fritz! or Ken! from AVM, also use the protocol. In connection with this, requests from other programs can be reset, so that a timeout error occurs.


We recommend switching to Windows® 10, as various measures have been taken to avoid such conflicts.

If this is not possible, another network protocol should be set up in addition to TCP/IP, e.g. "Named Pipes" or, if necessary, "NETBEUI" or "IPX", depending on what is offered alternatively and technically possible.

The SQL server should then no longer be configured to TCP/IP, but to the new protocols. The program for configuring the SQL Server can be called up directly from the EULANDA® Start menu via the point "Administration" with the right mouse button. This only works if EULANDA® is executed on the PC that is also executing the SQL server.

Remove the TCP/IP protocol and add the new protocol.

All workstations must also be reconfigured. To do this, set the new protocol (NETBEUI or IPX) in the network environment and switch the client connection in the respective EULANDA® in the start menu to the protocol used in the server and remove the TCP/IP protocol.

If no connection to the SQL server is established after the conversion, check the UDL file of the database connection on the workstation side. To do this, right-click on the client entry in the green start menu and select "UDL file".

After making the changes on the "Connection" tab and the "Test connection" button there, check whether a connection to the SQL server can be established without errors.

If you have made changes to the UDL file, EULANDA® must be restarted so that these changes can be taken into account.