Azure Notification Hubs
An Azure service that is used to send push notifications to all major platforms from the cloud or on-premises environments.
383 questions
Microsoft.Azure.NotificationHubs.Messaging.ServerBusyException: The remote server returned an error: (503) ServiceUnavailable.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 15%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJD%3C/text%3E%3C/svg%3E)
Jeegnasa Desai
1
Reputation point
I am frequently seeing this error when sending notifications through Azure Notification Hub.
Microsoft.Azure.NotificationHubs.Messaging.ServerBusyException: The remote server returned an error: (503) ServiceUnavailable. Reason: Service Unavailable..TrackingId:3e604f2f-f78b-4a68-bf52-474ae464b1b5,TimeStamp:2022-04-12T06:30:02.8000794Z
Microsoft.Azure.NotificationHubs.Messaging.ServerBusyException: The remote server returned an error: (503) ServiceUnavailable. Reason: Service Unavailable..TrackingId:4f27e1f9-9536-425b-8122-b5dbe76ab990,TimeStamp:2022-04-12T06:30:02.8000794Z
Microsoft.Azure.NotificationHubs.Messaging.ServerBusyException: The remote server returned an error: (503) ServiceUnavailable. Reason: Service Unavailable..TrackingId:ca6e8288-801e-45dc-b683-68ade966ad43,TimeStamp:2022-04-12T06:31:19.7992682Z
Azure Notification Hubs
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 55.00000000000001%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
ajkuma 28,036 Reputation points Microsoft Employee Moderator2022-04-20T19:29:49.573+00:00 JeegnasaDesai-6427, To better assist you on this, I understand you have mentioned, you’re receiving this error frequently - since when are you facing this issue? Do you recall making any changes prior to this issue? On which region have you provisioned the resource?
--If you haven’t done this already – as a quick test, try upgrading hub/namespace to higher tier and then test.
--Go to the Azure portal > Notification Hubs Namespaces or Notification Hubs. Select the resource you want to update, and go to
Pricing Tier.Also, review the following options to fetch more info:
-
Diagnose and solve problemsblade to fetch some more details about the error -
Navigate to your Notification Hub on Azure Portal and select ‘Diagnose and solve problems’ - Azure Service Health provides personalized alerts and guidance when Azure service issues affect you. It can notify you, help you understand the impact of issues, and keep you updated as the issue resolves.
- Azure Resource Health helps you diagnose and get support for service problems that affect your Azure resources. It reports on the current and past health of your resources.
-
-
ajkuma 28,036 Reputation points Microsoft Employee Moderator
2022-04-20T19:30:43.083+00:00 Adding more info:
As for as Namespace
ServerBusyException Classclient - the exception that is thrown when a server is busy.
Microsoft.Azure.NotificationHubs.MessagingKindly let us know how it goes, I'll follow-up with you further.
-
Jeegnasa Desai 1 Reputation point
2022-04-21T03:41:45.013+00:00 I don't think upgrading the service is a solution here!
The service itself is not working in first place - then why should I upgrade it? (Just to diagnose a problem???)My service is in "North Europe".
Also it shows this error on resource health -
Resource health is not supported for microsoft.notificationhubs/namespaces/notificationhubs at this time. To see the list of supported resource types, please visit https://aka.ms/rhc-types -
ajkuma 28,036 Reputation points Microsoft Employee Moderator
2022-04-21T12:21:21.137+00:00 Thanks for the follow-up! Apologies for any confusion.
I'd performed a similar test and analysis. To dig deeper on this, I would need additional information about your subscription ID (which is PII, so please do not share it on public forum, I'll follow-up with you privately).--I have already reported this issue to our product engineering team internally and will get back to you shortly.
From initial check, it looks like the call Get installation repeatedly with an INVALID installation id called (test)? it seems there are about multiple calls / per minute all failing. Kindly review and share more details about your call.
Thanks for your patience!
As a side note -
Registration IDs are generated by NH (Notification Hub) and be used to identify a particular device. The device token is a property on the registration.
-
Jeegnasa Desai 1 Reputation point
2022-04-21T14:26:29.427+00:00 AS I can see from my application logs, the errors are coming on both Device Register and Push Notification Send.
I am usign Azure SDK (.NET client) and here is stack trace if that helps ...Microsoft.Azure.NotificationHubs.Messaging.ServerBusyException: The remote server returned an error: (503) ServiceUnavailable. Reason: Service Unavailable..TrackingId:3e604f2f-f78b-4a68-bf52-474ae464b1b5,TimeStamp:2022-04-12T06:30:02.8000794Z at Microsoft.Azure.NotificationHubs.NotificationHubClient.<SendRequestAsync>d__126.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Azure.NotificationHubs.NotificationHubClient.<SendNotificationImplAsync>d__115.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Sign in to comment
Sign in to answer