[BUG] Service Bus: Unknown error after calling GetNamespaceInfo

[eddynaka]

Describe the bug
When I call client.GetNamespaceInfoAsync it is returning an exception. The message shows an "unknown error".

Expected behavior
Throw an error that is not unknown or successful.

Actual behavior (include Exception or Stack Trace)
Returning unknown error.

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. start the clientManagement
2. call GetNamespaceInfoAsync

   at Microsoft.Azure.ServiceBus.Management.NamespaceInfoExtensions.ParseFromContent(String xml)
   at Microsoft.Azure.ServiceBus.Management.ManagementClient.<GetNamespaceInfoAsync>d__9.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

Environment:

• Name and version of the Library package used: Microsoft.Azure.ServiceBus 5.1.3
• Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8] netstandard2.1, called by netcoreapp3.1
• IDE and version : [e.g. Visual Studio 16.3] VS16.10

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @axisc.

Issue Details

---

Describe the bug
When I call client.GetNamespaceInfoAsync it is returning an exception. The message shows an "unknown error".

Expected behavior
Throw an error that is not unknown or successful.

Actual behavior (include Exception or Stack Trace)
Returning unknown error.

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. start the clientManagement
2. call GetNamespaceInfoAsync

   at Microsoft.Azure.ServiceBus.Management.NamespaceInfoExtensions.ParseFromContent(String xml)
   at Microsoft.Azure.ServiceBus.Management.ManagementClient.<GetNamespaceInfoAsync>d__9.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

Environment:

• Name and version of the Library package used: Microsoft.Azure.ServiceBus 5.1.3
• Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8] netstandard2.1, called by netcoreapp3.1
• IDE and version : [e.g. Visual Studio 16.3] VS16.10

Author:	eddynaka
Assignees:	-
Labels:	Client, Service Attention, Service Bus, customer-reported, needs-team-attention, needs-triage, question
Milestone:	-

[jsquire]

//cc: @shankarsama

[jsquire]

Thank you for your feedback. Tagging and routing to the team best able to assist.

[ramya-rao-a]

@eddynaka Apologies for the late response. This is a parsing error that we cannot replicate without knowing the input to the GetNamespaceInfoAsync method. Would it be possible for you to share that?

Also, please note that the Microsoft.Azure.ServiceBus package is now deprecated. A newer package Azure.Messaging.ServiceBus is available as of November 2020. While the older package will continue to receive critical bug fixes, we strongly encourage you to upgrade. Read the getting started guide and migration guide for more details.

In the new package, the corresponding method to use will be ServiceBusAdministrationClient.GetNamespacePropertiesAsync. Please also share if you are seeing a similar issue when using the new package

[eddynaka]

Hi @ramya-rao-a ,

I just changed and now I receive this: Unknown error. (GeneralError)

and the inner exception:

<feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Publicly Listed Services</title><subtitle type="text">This is the list of publicly-listed services currently available.</subtitle><id>uuid:9f875c19-3997-4acb-838f-5233bc5dff57;id=87</id><updated>2021-10-08T00:34:10Z</updated><generator>Service Bus 1.1</generator></feed>
Status: 200 (OK)

Content:
<feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Publicly Listed Services</title><subtitle type="text">This is the list of publicly-listed services currently available.</subtitle><id>uuid:9f875c19-3997-4acb-838f-5233bc5dff57;id=87</id><updated>2021-10-08T00:34:10Z</updated><generator>Service Bus 1.1</generator></feed>

Headers:
Date: Fri, 08 Oct 2021 00:34:10 GMT
Server: Microsoft-HTTPAPI/2.0
Transfer-Encoding: chunked
Strict-Transport-Security: REDACTED
x-ms-client-request-id: 77693b4a-9b5a-462f-8f29-afe726bbc2f2
Content-Type: application/atom+xml; type=feed; charset=utf-8

[ramya-rao-a]

I just changed

@eddynaka Do you mean to say that you are now using the new package i.e. Azure.Messaging.ServiceBus?

[eddynaka]

Hi @ramya-rao-a ,

i changed to the new package and even with that, I still see the unknown error.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @shankarsama, @DorothySun216.

Issue Details

---

Describe the bug
When I call client.GetNamespaceInfoAsync it is returning an exception. The message shows an "unknown error".

Expected behavior
Throw an error that is not unknown or successful.

Actual behavior (include Exception or Stack Trace)
Returning unknown error.

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. start the clientManagement
2. call GetNamespaceInfoAsync

   at Microsoft.Azure.ServiceBus.Management.NamespaceInfoExtensions.ParseFromContent(String xml)
   at Microsoft.Azure.ServiceBus.Management.ManagementClient.<GetNamespaceInfoAsync>d__9.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

Environment:

• Name and version of the Library package used: Microsoft.Azure.ServiceBus 5.1.3
• Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8] netstandard2.1, called by netcoreapp3.1
• IDE and version : [e.g. Visual Studio 16.3] VS16.10

Author:	eddynaka
Assignees:	JoshLove-msft
Labels:	Service Bus, Service Attention, Client, customer-reported, question, needs-team-attention, needs-team-triage
Milestone:	-

[JoshLove-msft]

Hi @eddynaka,
Can you include a code snippet so we can attempt to reproduce the issue?

[eddynaka]

Hi @JoshLove-msft ,

below the snippet:

var serviceBusOptions = new ServiceBusAdministrationClientOptions();
serviceBusOptions.Retry.MaxRetries = (retry == bool.TrueString) ? 3 : 0;
var client = new ServiceBusAdministrationClient(serviceBusConnectionString, serviceBusOptions);
NamespaceProperties ni = await client.GetNamespacePropertiesAsync();

[JoshLove-msft]

Thanks, this code works when I test it. Do other operations using the admin client work?

[eddynaka]

Hi @JoshLove-msft , this looks like happens when I incorrectly use a notification hub, which is also a service bus.
I just wanted to understand if this is something servicebus should accept or if this is something you should not.

[JoshLove-msft]

Hi @eddynaka, I don't think you can talk to the Notification Hub using the Service Bus SDK.
Have you tried using the Notification Hub SDK - https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/?

[eddynaka]

Hi @JoshLove-msft , since both use ServiceBus, I was expecting both to work or at least to ServiceBus generate some specific message like "u are using the wrong thing".

Don't know if you have a use case for that, for accepting any kind of SB.

Thanks :)

[JoshLove-msft]

Can you clarify what you mean when you say that both use ServiceBus?

[eddynaka]

HI @JoshLove-msft ,

Below, a connection string from NotificationHub Resource:

Endpoint=sb://resource.servicebus.windows.net/;SharedAccessKeyName=DefaultListenSharedAccessSignature;SharedAccessKey=long_key

Below, a connection string from a ServiceBus Resource:

Endpoint=sb://resource.servicebus.windows.net/;SharedAccessKeyName=DefaultListenSharedAccessSignature;SharedAccessKey=long_key

So, I imagined, "hey, both have the same connection string, would that work?"

:)

[JoshLove-msft]

Ah I see. They both share the same connection string format, due to how they are implemented on the backend, but they are separate services. The same is true for Event Hubs (it also uses the same format, but is a separate service with a separate SDK).

[ghost]

Hi @eddynaka. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @eddynaka, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.