Using SDL Tridion Sites 9 with Content Manager using Azure SQL Database get error 'Could not connect to the notification hub'

Article Number:000010006 | Last Updated:5/24/2019 10:24 AM

Scope/Environment

SDL Tridion Sites 9

Symptoms/Context

Using SDL Tridion Sites 9 with Content Manager using Azure SQL Database get error:

'Could not connect to the notification hub'

The Content Manager is connected to a database hosted on MS Azure the Message Service Bus is configured in Azure as documented in the Azure documentataion.
The configuring Content Manager for notification broadcasting with a SQL Azure database is done as per instructed at our documentation https://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Sites-v1/GUID-8B1C96F2-464E-442F-9727-3F4E7B21AF23

Resolution

No root cause has been found for this issue however R&D suggest to ensure that the Scale settings for Azure message bus set to Standard (rather than Basic).
In addition the behavior is described as follows:
If there is an established connection between Notification and Backplane hubs, it should look something like:

http://.../hubs/notificationHub/signalr/start?transport=longPolling&clientProtocol=1.5&connectionToken="token"

This error might be thrown on the very first Content Manager Explorer load when internally the notification hub is not initialized, however it does get initialized a shortly after. To see this behavior refer to the Network Tab in the browser

Root Cause

Reference

Send Article Feedback