Skip to main content
Version: 5.4

Database connections

Not all database systems can be handled here. But maybe one or the other clue will come up with the solution for “your” system.

Connection does not materialize – local and remote​

The “Test Connection” button returns an error. The error message often gives the correct hint.

  • Is the server named correctly? For example, for MySQL or MS SQL the specification of the IP is sufficient, but for MS SQL Express the instance must be named, e.g..: localhost\SQLEXPRESS
  • Is the name of the database spelled correctly? Does the user have access rights to the database? For example, in MS SQL, the databases are assigned to each logon. Ask your database administrator!
  • MS SQL: Is the correct authentication set for the user (SQL and Windows on access with user / password)?
  • Username and password are correct? Spend attention to upper and lower case!
  • Integrated security is enabled. The connection test is not meaningful. Integrated security uses the local Windows or domain user where the program was started to log in. In the configuration environment, this is usually the username with which you logged on to the computer, by contrast, the router service runs under system default (sufficient for local access to MS SQL, not for remote access).
  • Are the required services started (MS SQL: SQL Server and SQL Server Browser, via Server Configuration Manager or Control Panel - Administrative Tools - Services).

Connection does not materialize – only remote​

The “Test Connection” button returns an error. The error message often gives the correct hint. In addition to the above points, you have to check:

  • Is the network connection active? Can you ping the database machine (“Start - Run - ping <IP>”)? Ask your network administrator!
  • Are the firewalls of the involved computers switched off? We recommend deactivating the Windows firewalls of the participating computers. Otherwise, please ensure correct port release. Ask your network administrator to allow unrestricted communication between the router and the database server.
  • Is the server named correctly? For example, for MySQL or MS SQL the specification of the IP is sufficient, but for MS SQL Express the instance must be named, e.g.: 192.168.5.184\SQLEXPRESS or Rechnername\SQLEXPRESS
  • Allows the database to allocate remote connections (e.g. in MS SQL this must be activated for the respective user)?
  • Are the corresponding protocols activated? (MS SQL: Enable Named Pipes or TCP / IP in Network Configuration and Native Client Configuration in Server Configuration Manager depending on connection)?

Connection is established but no tables are visible (MS SQL)​

The button “Test connection” returns OK. However, tables can not be selected in the configuration of the transfer object.

  • Does the user have the appropriate rights to the database? – “Listing tables” may not be allowed to the user, depending on the role.
    • At “Login Properties” of the corresponding login in the user mapping for the required database assign to “db_datareader” and “db_datawriter”. Attention: “db_owner” is required to run stored procedures.. – Ask your database administrator.
    • Of course, the user can also be assigned administrator rights on the database or on the system (e. g. the role “sysadmin”). But this should only happen for a short time for troubleshooting

Stored Procedures can not be executed. (MS SQL)​

  • Does the user have the appropriate rights to the database?
    • At “Login Properties” of the corresponding login in the user mapping for the required database “db_owner”

Stored Procedures are canceled.​

  • Are Command Time-out of the connection and Time-out of the corresponding connection set correctly?
    • Changing the time out of the corresponding database in Storage.
    • Increase the value of Time-out of the corresponding database in Storage.

Connection is established, but the database connection does not appear in the database transfer object.​

The connection test was successful, but the database connection in the connection configuration in the database transfer object does not appear or an error is returned.

  • You must save the database connection via the “OK” button before it is available.

At runtime, no data transfer occurs​

The connection could be easily made at design time. At runtime, the status display indicates a connection error. Open the log file via the tray icon. Look for the error message at the bottom of the file. Look for the error message at the bottom of the file.

14.07.10 17:33:42.228 [Error:::SqlConstantConnection]
Error while opening the sql connection: System.Data.SqlClient.SqlException: 
Error logging in for the user 'NT-AUTORITÄT\ANONYMOUS-ANMELDUNG'
  • If you access the database server remotely and have “built-in security” enabled, you must not run the service as a system user. Configure the service so, that it runs at the domain user.