Itgencmr402 na update Data Hub: The data container ID has not been set

Na het updaten van Data Hub (van Windows naar Multi platform) krijgen we nu de foutmelding:

Error itgencmr402: A connection to the database ACME\ACME could not be established.
The data container ID has not been set.

Stracktrace:

Error itgencmr402: A connection to the database ACME\ACME could not be established.

The data container ID has not been set.
08:48:48.290 InvantiveSystemException
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, Boolean isRecoverable, String poolIdentityId, String url)
   at Invantive.Basics.InvantiveSystemException..ctor(GlobalState owner, ExecutionOptions executionOptions, String validationCode, String errorMessage, String kindRequest, String stackTrace, String nk, Exception innerException, Boolean inheritMessageCodeWhenPresent, Nullable`1 uid, Boolean isRecoverable, String poolIdentityId)
   at Invantive.Data.ConnectionM...ainer credentialsContainer)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(String[] arguments)
   at Invantive.Producer.Data.Hub.Program.Main(String[] args)
   at Invantive.Data.ConnectionManager.A(GlobalState , ExecutionOptions executionOptions, CredentialsContainer , Boolean , Boolean& )
   at Invantive.Data.ConnectionManager.Open(GlobalState owner, ExecutionOptions executionOptions, CredentialsContainer credentialsContainer, Boolean ignoreDecryptionErrors, Boolean& decryptionErrorsOccurred)
   at Invantive.Producer.UtilityBaseCore.OpenDatabase(GlobalState owner, ExecutionOptions executionOptions, String databaseFullName, CredentialsContainer credentialsContainer, Boolean ignoreDecryptionErrors, Boolean& decryptionErrorsOccurred)
Exception during boot: Invantive.Basics.ValidationException: itgendhb005: Could not connect to database 'ACME\ACME'. Application will be closed.

Is het mogelijk om het versienummer uit de logging toe te voegen?

De foutmelding itgencmr402 geeft een indicatie dat de verkeerde versie gebruikt wordt.

Voor het gebruik van de multi-platform variant dienen de volgende stappen als uitgangspunt:

Invantive Data Hub Multi-Platform (22.0.668-PROD+4037) on 29-06-2023 08:48:34 (UTC)

Deze foutmelding is niet terug te vinden onder deze versie, maar wel onder oudere versies onder “Systeemberichten” op Invantive Cloud.

Advies is zorgvuldig te controleren of de genoemde versie wel gebruikt wordt.

Uhm… de versienummer en foutmelding komen uit dezelfde log. Dit is de volledige log:

*** Invantive Data Hub Multi-Platform (22.0.668-PROD+4037) on 29-06-2023 08:48:34 (UTC) ***

(C) Copyright 2004-2022 Invantive Software BV, the Netherlands. All rights reserved.

*** ATTENTION: HEADLESS MODE REQUESTED, YOU CAN NOT ANSWER QUESTIONS. ***
08:48:36.034 itgendhb023: SQL Script File: E:\Scripts\Exact\Invantive\Create_ItemPrices_Table.sql
08:48:36.036 itgendhb029: Log File: E:\Scripts\Exact\Invantive\20230629-Create_ItemPrices_Table.log
08:48:36.037 itgendhb066: License Contract Code: L12345678
08:48:36.038 itgendhb076: License Key ID: 133306128061234567
08:48:36.038 itgendhb067: Licensee: ACME B.V.
08:48:36.039 itgendhb070: Licensor: Invantive B.V.
08:48:36.040 itgendhb033: OS Log On Code: admin.user
08:48:36.040 itgendhb034: Machine: MACHINEAPP01
08:48:36.041 itgendhb034: IIID: 1a35809e-86dc-64c2-285d-ac991302c610
08:48:36.041 itgendhb035: Current Directory: E:\Scripts\Exact\Invantive
08:48:36.042 itgendhb073: Product Installation Configuration File: C:\Users\admin.user\Invantive\Prd\Invantive Data Hub Multi-Platform\Inst\Data Hub Multi-Platform\product-installation-user.settings
08:48:36.043 itgendhb074: Product Configuration File: C:\Users\admin.user\Invantive\Prd\Invantive Data Hub Multi-Platform\product-user.settings
08:48:36.043 itgendhb075: Global Configuration File: C:\Users\admin.user\Invantive\user.settings
08:48:36.044 itgendhb227: User Name: <censored>
08:48:36.044 itgendhb228: User Email Address: <censored>
08:48:36.048 itgendhb229: User Phone Number: <censored>
08:48:36.048 itgendhb030: Database: ACME\ACME

08:48:36.050 itgendhb203: Logging on
08:48:36.530 itgencmr138: Opened service data container 'OAuthHeadless'.
08:48:36.531 itgencmr138: Opened service data container 'Invantive.Producer'.
08:48:36.533 itgencmr138: Opened service data container 'TeamViewer'.
08:48:36.534 itgencmr138: Opened service data container 'KeePass'.
08:48:36.535 itgencmr138: Opened service data container 'Mail'.
08:48:36.535 itgencmr138: Opened service data container 'Ossus'.
08:48:36.536 itgencmr138: Opened service data container 'Os'.
08:48:36.537 itgencmr138: Opened service data container 'InMemoryStorage'.
08:48:36.538 itgencmr138: Opened service data container 'DataDictionary'.
08:48:36.538 itgencmr138: Opened service data container 'LastResort'.
08:48:36.612 itgencmr456: Connecting to Exact Online (alias eol).
08:48:40.465 itgenobr300: Provide TOTP verification code. (eol, ExactOnlineAll)
08:48:42.039 itgencmr128: Got OAuth access token using headless interactive control. (eol) (5.337 ms)
08:48:42.063 itgengpr065: Opening data container 'eol'.
08:48:42.436 itgenoda719: Got OAuth access token using authorization code retrieved from OAuth Code Grant Flow through credentials. (eol) (319 ms)
08:48:42.437 itgengpr152: Opened data container 'eol'.
08:48:42.443 itgengpr065: Opening data container 'eol'.
08:48:42.446 itgengpr152: Opened data container 'eol'.
08:48:44.954 itgencmr456: Connecting to SQL Server (alias sql).
08:48:44.954 itgengpr065: Opening data container 'sql'.
08:48:46.223 itgengpr152: Opened data container 'sql'.
08:48:46.289 Error itgencmr402: A connection to the database ACME\ACME could not be established.

The data container ID has not been set.
08:48:48.290 InvantiveSystemException
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, Boolean isRecoverable, String poolIdentityId, String url)
   at Invantive.Basics.InvantiveSystemException..ctor(GlobalState owner, ExecutionOptions executionOptions, String validationCode, String errorMessage, String kindRequest, String stackTrace, String nk, Exception innerException, Boolean inheritMessageCodeWhenPresent, Nullable`1 uid, Boolean isRecoverable, String poolIdentityId)
   at Invantive.Data.ConnectionM...ainer credentialsContainer)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(String[] arguments)
   at Invantive.Producer.Data.Hub.Program.Main(String[] args)
   at Invantive.Data.ConnectionManager.A(GlobalState , ExecutionOptions executionOptions, CredentialsContainer , Boolean , Boolean& )
   at Invantive.Data.ConnectionManager.Open(GlobalState owner, ExecutionOptions executionOptions, CredentialsContainer credentialsContainer, Boolean ignoreDecryptionErrors, Boolean& decryptionErrorsOccurred)
   at Invantive.Producer.UtilityBaseCore.OpenDatabase(GlobalState owner, ExecutionOptions executionOptions, String databaseFullName, CredentialsContainer credentialsContainer, Boolean ignoreDecryptionErrors, Boolean& decryptionErrorsOccurred)
Exception during boot: Invantive.Basics.ValidationException: itgendhb005: Could not connect to database 'ACME\ACME'. Application will be closed.
   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, Boolean isRecoverable, String poolIdentityId, String url)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(String[] arguments)
   at Invantive.Producer.Data.Hub.Program.Main(String[] args)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(String[] arguments) in c:\smoke\ws-22.0\Invantive.Data.Hub\src\Invantive.Producer.Data.Hub\QueryEngine.cs:line 630.
08:48:48.320 Error itgendhb005: Could not connect to database 'ACME\ACME'. Application will be closed.
08:48:48.320 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, Boolean isRecoverable, String poolIdentityId, String url)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(String[] arguments)
   at Invantive.Producer.Data.Hub.Program.Main(String[] args)
   at Invantive.Producer.Data.Hub.QueryEngine.Run(String[] arguments) in c:\smoke\ws-22.0\Invantive.Data.Hub\src\Invantive.Producer.Data.Hub\QueryEngine.cs:line 630
**** 08:48:48.328 Error itgenube182: itgendhb005: Could not connect to database 'ACME\ACME'. Application will be closed.

For support go to https://forums.invantive.com.

08:48:48.329 itgendhb219: End program execution with exit code 5.
08:48:48.329 itgendhb068: Program finished on 29-6-2023 08:48:48.
itgenpgm001: Application finished
Failed Data Hub job with exit code 5.

Het is niet gelukt om dit probleem te reproduceren of een mogelijke herkomst te bepalen.

Advies is om trace in te schakelen, het programma te starten en dan de resulterende bestanden op te sturen naar support@invantive.com onder vermelding van de URL van dit topic.

De stappen hiervoor staan beschreven in:

Speelt dit probleem nog?

Jazeker. Ik heb op 3 juli en nogmaals op 12 juli de tracefiles gemaild, maar nog geen reactie mogen ontvangen

Dank voor bericht. Een collega zal contact met u zoeken om het bestand nogmaals te sturen.

Ik heb de traces 21-7 opnieuw aangeleverd, maar nog steeds geen enkele reactie mogen ontvangen.

Ondertussen ook een update uitgevoerd naar “Invantive Data Hub Multi-Platform (22.0.705-PROD+4117)”, dit resulteert nog in dezelfde foutmelding.

Dit probleem speelt nog steeds en wij hebben niks meer vernomen.
We beginnen hier erg last van de ondervinden.

Het blijkt een probleem te zijn dat uitsluitend optreedt bij on-premises SQL Server-databases waarvan de server name op null staat.

In de releases vanaf 23.0.44 zal een verbetering toegevoegd zijn om op alternatieve wijze een datacontainer-ID te bepalen. Deze release zal naar verwachting vanaf 28 september te downloaden zijn.

Alternatief is om de servername in te stellen in overleg met de databasebeheerder.

Bedankt. Het werkt weer

1 like

Dit topic is 7 dagen na het laatste antwoord automatisch gesloten. Nieuwe antwoorden zijn niet meer toegestaan.