Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Scaleout - ServiceBus: No tracing with incorrect connection string #2211

jcondex opened this Issue · 5 comments

5 participants


I have a servicebus scaleout app with full tracing enabled in the web.config file. I mistakenly used an invalid servicebus connection string and no traces informing me of the error written to the hub's tracelisteners.

Accessing 'signalr/hubs' on the hub url with a browser correctly displayed the error.


Can you add clear repro steps and the trace config please.

@abnanda1 abnanda1 was assigned

@jcondex just wanted to follow-up on this.


To repro, setup the configuration for a scaleout setup using servicebus and specify an incorrect connectionString:


strinb backplaneConnectionString = "sb://;SharedSecretIssuer=owner;SharedSecretValue=y87m+fQql/+eCutwuonq1Lon3uIYr3/4EiqEpXMLz9w=";
GlobalHost.DependencyResolver.UseServiceBus(backplaneConnectionString, name);

NOTE: The above connection string does not start with 'Endpoint='. The correct connectionString should start with 'Endpoint=sb://"


Looking at the code, the same issue should be there for SQL and Redis as well. I am going to repro that and fix that as well.


I tried setting invalid connection strings on the three scaleout options. I will open a new issue to emit an error level trace for SQL Server

SignalR.ServiceBusMessageBus Error: 0 : Invalid connection string 'connection string': The Service Bus connection string contains invalid property. 'connection string' is not a valid property within the connection string.

SignalR.RedisMessageBus Error: 0 : Error connecting to Redis - System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it
at BookSleeve.RedisConnectionBase.ConnectAsyncComplete(Object sender, SocketAsyncEventArgs args) in c:\Dev\BookSleeve\BookSleeve\RedisConnectionBase.cs:line 315

SignalR.ScaleoutMessageBus Information: 0 : Stream(0) - Error has happened with the following exception: System.ArgumentException: Format of the initialization string does not conform to specification starting at index 0.
at System.Data.Common.DbConnectionOptions.GetKeyValuePair(String connectionString, Int32 currentPosition, StringBuilder buffer, Boolean useOdbcRules, String& keyname, String& keyvalue)
at System.Data.Common.DbConnectionOptions.ParseInternal(Hashtable parsetable, String connectionString, Boolean buildChain, Hashtable synonyms, Boolean firstKey)
at System.Data.Common.DbConnectionOptions..ctor(String connectionString, Hashtable synonyms, Boolean useOdbcRules)
at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous)
at System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(DbConnectionPoolKey key, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions)
at System.Data.SqlClient.SqlConnection.ConnectionString_Set(DbConnectionPoolKey key)
at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
at Microsoft.AspNet.SignalR.SqlServer.DbOperation.ExecuteT in d:\signalr\dev\src\Microsoft.AspNet.SignalR.SqlServer\DbOperation.cs:line 126
at Microsoft.AspNet.SignalR.SqlServer.DbOperation.ExecuteScalar() in d:\signalr\dev\src\Microsoft.AspNet.SignalR.SqlServer\DbOperation.cs:line 57
at Microsoft.AspNet.SignalR.SqlServer.SqlInstaller.IsSqlEditionSupported(String connectionString) in d:\signalr\dev\src\Microsoft.AspNet.SignalR.SqlServer\SqlInstaller.cs:line 53
at Microsoft.AspNet.SignalR.SqlServer.SqlInstaller.Install() in d:\signalr\dev\src\Microsoft.AspNet.SignalR.SqlServer\SqlInstaller.cs:line 31
at Microsoft.AspNet.SignalR.SqlServer.SqlMessageBus.Initialize(Object state) in d:\signalr\dev\src\Microsoft.AspNet.SignalR.SqlServer\SqlMessageBus.cs:line 93.

@NTaylorMullen NTaylorMullen referenced this issue from a commit
@NTaylorMullen NTaylorMullen Added tracing to ServiceBusConnection to indicate when an invalid con…
…nection string has been provided.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.