0 
Azure Service Bus
Created: Friday, August 30, 2024
Pricing tier: Premium
Zone Redundancy: Enabled

The topic has been working for multiple months at this point and today (13 May 2025, around 11:30 CEST) suddenly the client trying to connect to the topic started getting timeouts. We could not see any problems from the Service Bus or Topic pages in Azure Portal. To investigate further, we tried to make some changes to the topic, like adding a filter to the topic subscription. This caused the error:

Error: 400 Values are not in range of 0 - Int32.MaxValue, extentId: -1, offset: -1. TrackingId:df0082d5-922b-4940-b198-2e852e0965d5_G14, SystemTracker:sb-xxxx-:Topic:xxxx-schedule, Timestamp:2025-05-13T12:44:34

We could not find a solution for that, so we had to remove the topic. When we tried deleting the topic we got:

Deleting Service Bus topic xxxx Failed deleting Service Bus topic xxxx with error code: MessagingGatewayBadRequest and with message: SubCode=40000. Values are not in range of 0 - Int32.MaxValue, extentId: -1, offset: -1. TrackingId:bb782d15-5eb4-46a0-adca-dee34bb89d63_G2, SystemTracker:xxxx:Topic:xxxx, Timestamp:2025-05-13T13:24:21.

We had to create a new topic with the new name (with the new subscriptions and SAS Policies) and keep the old one since it was not possible to remove it.

What are these 400 and 40000 errors and what could cause them?

Improve this question
2
  • I would suggest taking the tracking ID and opening a support case with Azure. There might be internal Azure Service Bus issues/problems that you won't be able to identify publicly just from the error. Commented May 13 at 16:05
  • We have been through the paid Azure Support before for several months. We did not find it useful, since the "internal" Azure Problems were identified they had no ETA and they only way to fix it "at the moment" was to recreate the resource (in our case it was APIM and some other issues with Service Bus). I believe it is unfair to pay for the support when I report the errors that are Azure internal ones. In this case I was wondering if anyone else had the same issue with the Service Bus, so we could prevent this from re-occurring. Timeouts on the selected dead SB Topics and Queues is "fun". Commented May 13 at 21:00
Related questions
1
Unique messages on a Azure Service Bus Topic
0
Do Azure Functions require permissions to publish messages to a Service Bus topic?
8
Azure function Service bus topic trigger sleeps
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.