Azure service bus emulator does not start

[pwrreset]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm getting this error, some people of our team get it all the time, others get it intermittently:

Azure.Messaging.ServiceBus.ServiceBusException: The messaging entity 'sb://sbemulatorns.servicebus.onebox.windows-int.net//$management' could not be found. To know more visit https://aka.ms/sbResourceMgrExceptions. TrackingId:23f889f037af4b169d16bc3fe40c9a38_G0, SystemTracker:gateway1, Timestamp:2025-03-05T12:24:59 (MessagingEntityNotFound). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.

Expected Behavior

It runs and service bus emulator works as it is supposed to.

Steps To Reproduce

var builder = DistributedApplication.CreateBuilder(args);

builder.Configuration.AddUserSecrets();

var serviceBus = builder.AddAzureServiceBus("servicebus")
.RunAsEmulator();

var topic = serviceBus
.AddServiceBusTopic("ctopic", builder.Configuration["redacted"]);

var sub = topic
.AddServiceBusSubscription("c-subscription", builder.Configuration["redacted"]);

builder.Build().Run();

Exceptions (if any)

No response

.NET Version info

.NET SDK:
Version: 9.0.200
Commit: 90e8b202f2
Workload version: 9.0.200-manifests.69179adf
MSBuild version: 17.13.8+cbc39bea8

Runtime Environment:
OS Name: Windows
OS Version: 10.0.26100
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\9.0.200\

.NET workloads installed:
[aspire]
Installation Source: VS 17.13.35818.85
Manifest Version: 8.2.2/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.2.2\WorkloadManifest.json
Install Type: Msi

[wasm-tools-net8]
Installation Source: VS 17.13.35818.85
Manifest Version: 9.0.2/9.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.workload.mono.toolchain.net8\9.0.2\WorkloadManifest.json
Install Type: Msi

[wasm-tools]
Installation Source: VS 17.13.35818.85
Manifest Version: 9.0.2/9.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.workload.mono.toolchain.current\9.0.2\WorkloadManifest.json
Install Type: Msi

Configured to use loose manifests when installing new manifests.

Host:
Version: 9.0.2
Architecture: x64
Commit: 80aa709f5d

.NET SDKs installed:
9.0.200 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

Anything else?

No response

[pwrreset]

At first I thought it was relevant as I'm using a VM to do development but it's been confirmed in my team that people without VM have the same issue.

[pwrreset]

Another issues we've encountered is that we can't get the connection string from the WithEnvironment for the service bus emulator to map it to Service Bus output Attribute (Microsoft.Azure.Functions.Worker.ServiceBusOutput). Since the emulator isn't working, we won't integrate the emulator into Aspire for now. It would be nice to be able to do the same as with the sql database emulator:

.WithEnvironment(async (context) =>
{
    //this fetches the connection string from the parent resource sql server
    var conn = await sonDb.Resource.Parent.GetConnectionStringAsync();
    context.EnvironmentVariables["sql-connection"] = $"{conn};Database={sonDb.Resource.DatabaseName}";
}

We have the same problem with Signalr emulator as well.

[davidfowl]

Can you provide a fully application or a minimal application that we can run that shows the problem? It's hard to tell from these snippets of code if you might have bugs or if the emulator is having a hard time starting.

[pwrreset]

Can you provide a fully application or a minimal application that we can run that shows the problem? It's hard to tell from these snippets of code if you might have bugs or if the emulator is having a hard time starting.
Here:
https://1drv.ms/u/c/90ddd96bb517c510/EWk2l1o36GBArTTfMc3Wp_UBspFectgKjgvTC4ORwIa_rw?e=xhZM3j

[sebastienros]

I was able to repro and isolated the problem. It's a bug in our integration, I have a fix already.

The mitigation is to use the same resource and topic/name, assume it's possible for you. For instance in your example

// .AddServiceBusTopic("ctopic", builder.Configuration["redacted"]);
.AddServiceBusTopic(builder.Configuration["redacted"], builder.Configuration["redacted"]);

[sebastienros]

Already fixed yesterday #7997