The message indicates that the value database cannot be accessed. The software can still be started, "only" access to the measured value database is not possible.
The reasons for this may vary depending on the values database used:
Access database
The database is either physically inaccessible (not available, paths and links incorrect), or the Access database is corrupt.
In addition to the links, the database may need to be opened and repaired using the "Access" software.
It is generally recommended to stay away from Access databases and switch to MS SQL
Special case: O-QIS MCA/CMMM--Reporting with Access-databases
If the MCA/CMM-Reporting is running with access-databases which are automatically compressed, it can happen, that the renaming of the databases did not work. In the folder of the databases, this 3 (or more) "renamed databases" can be found:
The QDAS_CMM.CDB is the original renamed QDAS_CMM..MDB.
To solve this: Move all other types (*.SIC and *.BDM) to a new created subfolder (can be deleted afterwards, if the software is running again).
Rename the QDAS_CMM.CDB to QDAS_CMM.MDB
Open this database with Microsoft Access and use the function "Compact and Repair".
Please run this function two to three times in a row, as it usually doesn't work the first time.
Then restart the program and the problem should be temporarily resolved. A final solution will be to avoid the usage of Access-databases and switch to MS SQL (Express).
MS SQL or Oracle database
The server or the database itself is not available. (can be simulated by switching the value database offline)
Possible Solution
After the start of the Software (as a SuperUser or ConfigurationUser) the Database connection can be chosen
and here the database connection can be tested. This test is "Outside of the Q-DAS System", and just check the possible connection.
Depending on the type of database, the message can show the local IT where the problem can be:
In case of an Access-Database the path can be seen, maybe adapted, or with the local IT the database then "compressed and repaired"
What if everything is obviously set correctly?
A rarely occurring problem: Everything seemed to be configured correctly. All databases on MS SQL. but the database connection to the value database is not established. A test with "Test Connection" shows no problems at first. One reason for this may be that the ODBC driver was not installed.
The application addresses the databases in the order "Text / Config / Licence / Values", but only the measured value database has "stored procedures". These require the ODBC drivers.
Solution:
For client installations, install the client with the ODBC installation activated
For server installations: install the ODBC manually or (easier): Install a client on the server, but confirm the installation of ODBC during its installation.
(The Client on the Server can be uninstalled afterwards again)