- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2023 08:19 AM - edited 04-11-2023 09:12 AM
Hello Experts,
I need to add a test tenant to one of our sub-prod instances to test Virtual Agent, but am getting an error when trying to connect the tenant that does not allow me to. The instance was recently upgraded to Tokyo from San Diego (not sure if that matters) and previously was only connected to our production tenant. Can someone please help me work past this issue. The error message is below:
It seems that I have both tenants installed but I can't see the details of them, nor do I have the 'configure' button. Any assistance is greatly appreciated!!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2023 09:13 AM
To close this out. I identified the issue that happened with the upgrade to Tokyo. When the instance was upgraded, the message auth record was wiped in the Provider Channel Identity record. To resolve this follow the steps outlined below:
1. Navigate to the Provider Channel Identity table (sys_cs_provider_application.list)
2. Open the record in that table (there should not be duplicates)
3. You will see that the Message auth field is blank
4. Click on the search icon and select the corresponding message auth record - it should contain the same tenant id as the provider channel identity record.
5. Save the channel provider identity record with the correct message auth field updated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2023 09:13 AM
To close this out. I identified the issue that happened with the upgrade to Tokyo. When the instance was upgraded, the message auth record was wiped in the Provider Channel Identity record. To resolve this follow the steps outlined below:
1. Navigate to the Provider Channel Identity table (sys_cs_provider_application.list)
2. Open the record in that table (there should not be duplicates)
3. You will see that the Message auth field is blank
4. Click on the search icon and select the corresponding message auth record - it should contain the same tenant id as the provider channel identity record.
5. Save the channel provider identity record with the correct message auth field updated.