Itgenoac023 Merging Invantive Credentials Server

Questions (nl)
1

When signing in with Invantive Credentials Server from Invantive Data Hub, I receive the message:

itgenoac023:
A connection could not be established to the database ‘ACME\eolmss’.
The connection to the Invantive Credentials Server could not be established within 3 tries spread across 120.0538767 seconds for the database segment ‘acme’.
The operation has timed out.
System.Net.WebException

2

Invantive Data Hub has attempted to contact the Invantive Credentials Server multiple times but was unable to establish a connection because (at least) the last attempt resulted in a “timeout”.

The advice is to restart Invantive Data Hub.

3

I believe we have the same problem. How can I restart the data hub? The server is already restarted daily, and we’ve had this issue since 15 September.

Additionally: The Invantive Data Hub is used for multiple clients on this server. It doesn’t work for Client A, but for Client B, the Data Hub works fine.

4

After restarting the batch files, the same message still appears. In the cloud environment, it can be seen that the refresh token was last updated on 15-09 at 21:35, after which the process stalled.

image
image612×147 31.1 KB

6

Here is the exact timestamp:

2026-09-18 10:05:24.450 Error itgencun016: Error itgenoac023: ** A connection could not be established to the database '...'.
The connection to the Invantive Credentials Server could not be established within 3 tries spread across 120.0817954 seconds for the database segment '...'.

The operation has timed out.
https://credentials.invantive.com
2026-09-18 10:05:26.458 Error itgenoac023: System.Net.WebException
ValidationException
ValidationException
   at System.Net.HttpWebRequest.GetResponse()
   at Invantive.Data.Providers.OAuth.InvantiveOAuthCredentialsServerProvider.GetDatabaseConnectionInfo(GlobalState owner, ExecutionOptions executionOptions, SqlExecutionStep sqlExecutionStep, IProviderManager manager, SerializableCredentialsDataContainer dataContainer, Credentials credentials, String databaseFullName)
2026-09-18 10:05:26.474 Error itgencun016: Error itgendhb005: Could not connect to database 'xxxxxx'. Application will be closed.
2026-09-18 10:05:26.475 Error itgendhb005: ValidationException
   at Invantive.Basics.ValidationException..ctor(GlobalState owner, ExecutionOptions executionOptions, String messageCode, String errorMessage, String kindRequest, String localStackTrace, String nk, Exception innerException, Boolean inheritMessageCodeWhenPresent, Nullable`1 uid, Nullable`1 isRecoverable, String poolIdentityId, String url, Nullable`1 partyUid, String partitionCode, String tableName, String parameter1, String parameter2, String parameter3, String parameter4, String parameter5, String clientId)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(GlobalState owner, ExecutionOptions executionOptions, String[] arguments)
   at Invantive.Producer.Data.Hub.Program.Main(String[] args)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(GlobalState owner, ExecutionOptions executionOptions, String[] arguments) in c:\smoke\ws-26.0\Invantive.Data.Hub\src\Invantive.Producer.Data.Hub\QueryEngine.cs:line 613
2026-09-18 10:05:26.478 Error itgendhb005: Could not connect to database '...'. Application will be closed.
7

The advice is to carefully check the username and password for Invantive Credentials Server.

You can verify this in the Timeline window on Invantive Cloud and in System Notifications. Notifications like the ones below indicate that the password is incorrect:

image
image1249×287 29.2 KB

itgenboe077
Too many consecutive invalid login attempts for user ‘john.doe@acme.eu’. The first failed attempt was on 15-09-2026 21:56:58 (UTC) and the last one was on 18-09-2026 10:07:51 (UTC). Verify if you can log in with this login code on the Invantive Cloud website and try again after 18-09-2026 10:45:37 (UTC).

itgenboe311
Downloading the contents of the user interface was cancelled after 30 seconds, for example, because the user navigated away in a browser.

After a few dozen attempts with the wrong password, each attempt will be delayed by at least 30 seconds until it succeeds. If successful, you will automatically receive an email about this.

8

In release 26.0.301 and later, the block will be reduced from 30 seconds to 15 seconds so that the notification can also be visible in the client application before the timeout occurs.

9

This question has been automatically closed after 1 week of inactivity. The most recent reply has been marked as the solution.

Please post a new question in a separate thread if the issue arises again. In the new question, please include a link to this thread by pasting its URL into the text.