Notification hub export registrations job internal server error RRS feed

  • Question

  • Hi,

    I'm using the Microsoft.Azure.NotificationHubs C# library to export registrations:

    var client = NotificationHubClient.CreateClientFromConnectionString(connectionString, hubName);
    NotificationHubJob job = await client.SubmitNotificationHubJobAsync(
    	new NotificationHubJob
    		JobType = NotificationHubJobType.ExportRegistrations,
    		OutputContainerUri = outputContainerSasUri

    The SubmitNotificationHubJobAsync call is throwing an exception after 25-30 seconds containing the following message:

    "<Error><Code>500</Code><Detail>Internal Server Error.TrackingId:b0947f62-1f43-478c-aac6-56fd54b8cea9_G2,TimeStamp:4/16/2019 1:30:47 PM</Detail></Error>"

    This is using a newly deployed notification hub on the Standard (S1) pricing tier, so initially there weren't any registrations to export. I've since added a registration just in case that was the cause, but I still get the error.

    Could this be looked into please?



    Tuesday, April 16, 2019 2:30 PM

All replies

  • Hi Dan,

    We would like to work closer with you on this matter. Can you please reach out to us at azcommunity@microsoft.com with your subscription ID and the URL of this post? We look forward to your reply.


    Wednesday, April 17, 2019 3:18 AM
  • Hi Bryan,

    I emailed as requested but haven't had a reply yet.



    Tuesday, April 23, 2019 12:57 PM
  • 500 is an internal error, so that's probably on us. Can you try it again and let me know?  If it's still happening, I'll submit a bug and we'll take a look at it. 
    Wednesday, April 24, 2019 5:16 PM
  • Hi John,

    I tried it again and got the same result. I have also just noticed that I get a resource health event shortly after the internal server error.

    4/25/2019 09:01:50 (GMT+1): Job submitted

    4/25/2019 09:02:16 (GMT+1): Error "Internal Server Error.TrackingId:e5133572-eeeb-4e51-9696-11b1547f9eb5_G3,TimeStamp:4/25/2019 8:02:16 AM"

    4/25/2019 09:10:43 (GMT+1): Health event "We are sorry, your namespace is unavailable We're working to automatically recover your namespace and to determine the source of the problem. No additional action is required from you at this time."


    Thursday, April 25, 2019 8:21 AM