Troubleshooting Database Access

The button to Apply the xUML service preferences is not enabled.

The user that has logged into the Bridge has no administration rights.

Login with another user that has administration rights (for instance the pre-defined user admin).

The button to Apply the deployment settings of an xUML service is not enabled (tab Settings of the xUML service).

The user that has logged into the Bridge does not belong to a group with role ADMIN or MODELER.

Login with another user that has sufficient access rights (for instance the pre-defined user admin).

The xUML service is still running.

Stop the xUML service.

An xUML service using the SQL adapter cannot be started.

User and password have not been defined in the deployment settings.
The logging file of the xUML service may read: No authorization data for connection "Oracle:: e2eora".

Enter the database user and password on tab Settings of the xUML service.

Running a test case with a database example in the xUML Debugger reports an error.

DB2
Error message: "Can not connect. DBMS API Library 'db2cli.dll' loading fails. ..."

Either the DBMS client libraries have not been installed, or the path of the library file cannot be found.
Check the DBMS client installation.

If the DBMS client has been installed, make sure the preferences are set correctly in the Bridge (tab Preferences of xUML Services).

Oracle
Error message: "Can not connect.
DBMS API Library 'ociw32.dll' loading fails. ..."

Either the DBMS client libraries have not been installed, or the path of the library file cannot be found.
Check the DBMS client installation and install the missing libraries. Make sure file tnsnames.ora includes all necessary parameters for the database connection.

If the DBMS client has been installed, make sure the preferences are set correctly in E2E Bridge (tab Preferences of xUML Services).
Reference the root directory of the Oracle installation, for instance D:\Oracle\ora11g.
Do not directly refer to the directory like bin containing the executables or DLLs.

MySQL
Error message: "Can not connect. DBMS API Library `libmySQL.dll` loading fails..."

Either the DBMS client libraries have not been installed, or the path of the
library file cannot be found.

Check the DBMS client installation.

If the DBMS client has been installed, make sure the preferences are set correctly in the Bridge (tab Preferences of xUML Services).

MySQL 8.0.x fails to connect with an error such as DBMS API Library 'libmysql.dll' loading fails or The specified module could not be found, although the configured libmysql.dll file exists.

libmysql.dll depends on the OpenSSL 1.1 runtime libraries libssl-1_1-x64.dll and libcrypto-1_1-x64.dll. When the SQL connector loads libmysql.dll by full path, Windows resolves its dependencies using the standard DLL search order. The directory containing libmysql.dll is not automatically included, so Windows returns ERROR_MOD_NOT_FOUND (126) when the dependency directory is not in the application directory, a system directory, the current directory, or PATH.

This can occur when the MySQL noinstall ZIP is used and only the client DLL is extracted. Unlike the MySQL Installer, the ZIP installation does not configure PATH or verify the Visual C++ Redistributable.

Set the Windows PATH environment variable as described on Installing and Configuring Database Access for MySQL.

Cannot connect to database via ODBC. Error:

Can not connect: 444 "HY000 [01000 The driver returned invalid (or failed to return) SQL_DRIVER_ODBC_VER: 03.80 HY000 ["

The problem may be caused by missing entries in the PATH environment variable. The variable might have been set by the driver installer and will be propagated to all newly-started applications (thus the third-party tools will be able to connect), but not to the windows services (regardless if they are restarted).

Since Bridge services inherit the environment of the Console windows service, they also end up with missing entries.

Reboot after driver installation.