Forum Discussion
Getting DMTS_InvalidTenantKeyId when creating any new Gateway Data Source Connection
email I recieved from the support 1h ago:
Upon checking further from my end, we can see the similar cases from our most valued customer like you and I already escalated this case to our Product group team.
We got an update that these types of failures only be seen while creating a data source using gateways that got tenant migrated and also I checked with them and asked for ETA and they updated us current ETA for the fix will get deployed in end of next week.
Also we have a workaround till that time, this issue will happen only for a gateways that don’t have a TenantKey. So it’s better if you can add a new gateway then you can create data sources for that gateway.
Most importantly, it's to do with addressing the existing configuration of the gateway. Please reach out to the person who configured the gateway to check the status of the gateway on the server where it is installed.
The service account that's been used on configuring the gateway might have been moved/expired. Using the different service account will generally resolves the issue unless there's something else to check. But, make sure you've the Recovery Key before changing the service account. After you change the service account, you can take over the existing gateway and and try connecting the data sources again.
This is the most info I've seen yet, thanks for sharing.
I can confirm the service account we're using is not disabled / locked out / expired, but I can certainly change the credential used to run the service and then change it back.
Thanks for the suggestion.
Also make sure your gateway version is upgraded too.