Service Bus Explorer

The Service Bus Explorer is a tool that you can use to manage and test the entities contained in an Azure Service Bus namespace.

C# (9.0 MB)
 
 
 
 
 
4.8 Star
(75)
88,499 times
Add to favorites
6/21/2017
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • .Net 4.5 requirement
    3 Posts | Last post November 21, 2013
    • Looks like recent update to SB Explorer (2.1.3), requires .NET 4.5. Just a bit curious to know the reasoning behind, as I feel .NET 4.5 adaptation is very slow/less in enterprise world? 
    • Hi Dhana
      the reason why the Service Bus Explorer 2.1 requires .NET 4.5 is quite straighforward: the Microsoft.ServiceBus.dll 2.0 introduced Async method overloads and this requires .NET 4.5. Hence, starting from version 2.0 of the tool, I had to switch from .NEt 4.0 to 4.5. Hope this helps. :)
      Ciao
      Paolo
    • Makes sense to leverage Async methods (also no one seems to have noticed except me so far, that may mean what I thought about less adoption of .NET 4.5 might be not correct at least in SB Explorer case :)). 
  • Service Bus 1.1 on a local virtual machine
    3 Posts | Last post November 08, 2013
    • Hi, thanks for your tool, really nice for Azure Service Bus. Now I'm trying to connect to a ServiceBus 1.1 on a virtual machine running locally on my machine. The certificates are installed. I'm able to connect to the SB from my code using a token Provider.
      I tried to connect with your tool, using the same solution as AdditiveLabs, but I'm receiving following error:
       <17:45:55> Exception: The token provider was unable to provide a security token while accessing 'https://win-4d3tqlpsj6v:9355/ServiceBusDefaultNamespace/$STS/Windows/'. Token provider returned message: ''.. Method <GetQueues>b__3c: retry 3 of 10.
      
    • I found it myself: provide OAuthUsername, OAuthDomain and OAuthPassword in Connection string and all is well.
    • I love when folks find a solution by themselves ;)
      Ciao
      Paolo
  • AMQP to Service Bus 1.1 on premise
    2 Posts | Last post November 04, 2013
    • Hi,  Great tool,  but I'm trying to connect to my local service bus (1.1) using the AMQP transport type.  Looking through your code I see that if I supply a connection string its not via AMQP.  So I need to supply the UI values. 
      Can you tell me how to find the values you ask for in your tool:
      URI or (Server FQDN):
      Namespace:
      Shared Secret Issuer Name:
      Shared Secret Issuer Secret:
      
      thanks
    • Hi Geoff
      I looked at my code and I didn't see the problem you mentioned. You need to specify the TransportType=Amqp in the connection string as explained at http://msdn.microsoft.com/en-us/library/windowsazure/jj841075.aspx. I tried debugged through my code and the ServiceBusHelper.Connect method correctly uses the TransportType specified in the connection string. You can specify the latter in the serviceBusNamespaces section of the configuration file or you can copy and paste the connection string in the Connect Form by selecting Enter connection string option from the drop down list. Hope this helps!
      Ciao
      Paolo
  • Service Bus 2.1 Error
    14 Posts | Last post October 23, 2013
    • <17:03:56> MessagingFactory successfully created
      <17:03:56> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:e3a344f4-c879-4b04-a884-9684934d100d_GCIS20AzurePack,TimeStamp:08/16/2013 9:03:56 AM. Method <GetQueues>b__26: retry 1 of 10.
      <17:03:56> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:5fd4276a-91a4-41e4-8a4a-a922e4d0da57_GCIS20AzurePack,TimeStamp:08/16/2013 9:03:56 AM. Method <GetQueues>b__26: retry 2 of 10.
      <17:03:57> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:9195680f-3f26-40ea-a630-bcb4cb918aec_GCIS20AzurePack,TimeStamp:08/16/2013 9:03:57 AM. Method <GetQueues>b__26: retry 3 of 10.
      <17:03:57> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:ccd37fac-221f-42df-a8c0-05280febe273_GCIS20AzurePack,TimeStamp:08/16/2013 9:03:57 AM. Method <GetQueues>b__26: retry 4 of 10.
      <17:03:57> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:3376b777-3bcc-4ba9-b949-aafa71b37a84_GCIS20AzurePack,TimeStamp:08/16/2013 9:03:57 AM. Method <GetQueues>b__26: retry 5 of 10.
      <17:03:57> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:d46166eb-f009-4b75-99fd-932d8f8279bb_GCIS20AzurePack,TimeStamp:08/16/2013 9:03:57 AM. Method <GetQueues>b__26: retry 6 of 10.
      <17:03:57> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:a496ae99-4969-43ff-a93a-899060ec7104_GCIS20AzurePack,TimeStamp:08/16/2013 9:03:57 AM. Method <GetQueues>b__26: retry 7 of 10.
      <17:03:58> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..Trac
    • Same here when connecting to a Service Bus for Windows Server 1.1
    • Hi guys
      I tested the new version with the RTM version of SB 1.1, not with the Beta. Can you please try to replace the Microsoft.ServiceBus.dll with the dll used by the Service Bus for Windows Server 1.1 Beta version and retest? Please contact me on the email address that you can find in the about form. Thanks!
    • Hi, I'm having the same error as above. Where can I get SB.1.1 RTM ? The most recent I found is SB.1.1 preview. 
      
      Microsoft.ServiceBus.dll is version 2.1.3.0, which is latest I think.
    • Just wanted to chime in that I'm having the same problem with the dll that's in the nuget package here
      
      https://www.nuget.org/packages/ServiceBus.v1_1/0.0.1
      
      
    • Hi guys
      I talked to the product group last week, and they confirmed that Microsoft.ServiceBus.dll 2.1.3 is compatible with the RTM version of the SB 1.1 (which is not out yet, but that I've installed on my machine), but is not compatible with the preview/beta of SB 1.1. That's why the tool works fine on my machine, where the RTM is installed, but not on your machine where the preview is installed, sorry about that. :( But don't worry, the good news is that the RTM version of SB 1.1 will be available soon! In the meantime, you have to use the previous version of the tool. If you don't have it anymore, just write me, and I'll send it to you! Hope this helps!
      Ciao
      Paolo
    • Hi Paolo,
      Thanks for the heads-up! I've indeed noticed that v2.0.1 of the client dll is required with SB 1.1 Preview... So how can I get the last compatible version of your tool? Maybe you could set some Skydrive link for us all! :)
      Cheers
      Thomas
    • Here we go :) You can download a copy of the Service Bus Explorer 2.0 from my SkyDrive: http://sdrv.ms/15GEcgz. Let me know if were able to get it! :)
      Ciao
      Paolo
      
      P.S. Could you please write me in private and give me more info about the Project you are working on? You can find my email address and Twitter account (@babosbird) in the about form. Thanks! :)
    • Got it, thanks!
      But this brings me to another question: as I use SB on my dev machine, I need to connect using my Windows credentials as described here: http://msdn.microsoft.com/en-us/library/jj714802%28v=azure.10%29.aspx#BMK_SBDev2
      
      Is there a way to connect like this using SB Explorer?
      
      (yep I'll PM you about my current project)
    • Forget it, you can just use a string like the one described as "Connection String: Service Bus for Windows Server with Explicit Local User" here: http://msdn.microsoft.com/en-us/library/windowsazure/jj149830.aspx
    • I love when smart guys find the right answer by themselves! ;)
      Ciao
      Paolo
    • Thanks for the explanation, the link, and the explorer!
    • Just wanted to follow up that SB Explorer is working just fine for me with the release of the Service Bus 1.1.
      
      Confirming that it works both with
      - Standalone SB1.1 installed via Web Platform Installer and configured with PowerShell (on Win7) 
      - Azure Pack-managed SB1.1
      
      Thanks Paolo.  This tool is extremely helpful to us, even given the large feature set included with the Azure Pack.
    • Thanks a lot for the feedback Jason! I'm trying to understand if the Microsoft.ServiceBus.dll 2.2.1 that was released Yesterday is compatible only with Windows Azure Service Bus or with the Service Bus 1.1 as well. More soon on this!
      Ciao
      Paolo
  • Enter connection string... option fails in new build
    4 Posts | Last post October 09, 2013
    • Trying to connect with a root SAS connection string with Manage/Listen/Send rights; (this works with the previous build):
      
      <13:57:35> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 1 of 10.
      <13:57:35> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 2 of 10.
      <13:57:35> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 3 of 10.
      <13:57:35> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 4 of 10.
      <13:57:35> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 5 of 10.
      <13:57:36> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 6 of 10.
      <13:57:36> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 7 of 10.
      <13:57:36> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 8 of 10.
      <13:57:36> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 9 of 10.
      <13:57:36> Exception: The connection string argument cannot be null.. Method <Connect>b__23: retry 10 of 10.
      <13:57:36> The connection string for service bus namespace Manual is in the wrong format.
      <13:57:36> Exception: The connection string argument cannot be null.
      
    • Can you please send me the details of your error to my email address? I mean, what is the exact form of the connection string that you are trying to use? You can find my email in the about form! Sorry for the delay, but this tool is published on the Windows Azure account, not my personal one! So I don't receive notifications! Thanks!
      Ciao
      Paolo
    • I found the bug, I'm working on that!
      Ciao
      Paolo
    • Fixed. Please download the new version, test it and let me know!
  • Version 2.1 not working with SB 1.1
    1 Posts | Last post October 03, 2013
    • So I have SB 1.1 setup and it works with the 1.8 and even 2.0 versions of this Explorer.  However I receive the following error (10 times) whenever I attempt to use 2.1:
      
      <15:26:35> Exception: The remote server returned an error: (400) Bad Request. No service can handle request..TrackingId:ba985712-2d2a-4718-ad4e-61e9d7ca1fdd_GRCPRODDB5,TimeStamp:10/3/2013 7:26:35 PM. Method <GetQueues>b__3c: retry 1 of 10.
      
      
      I'm simply punching this connection string into the option that says Enter Connection String:
      
      Endpoint=sb://rcproddb5.oec.oeconnection.com/BISServiceBus;StsEndpoint=https://rcproddb5.oec.oeconnection.com:9355/BISServiceBus;RuntimePort=9354;ManagementPort=9355
      
      Any ideas on why I'm receiving that error?  Thanks and great work on a great tool!
      
  • Automated Deployment
    2 Posts | Last post July 16, 2013
    • Hi Paolo,
      
      Thanks for the great tool. It makes working with SB so much easier.
      
      Do you know the best approach for unattended automated deployment of service bus queues, topics and subscriptions? In the BizTalk world, we have the BizTalk Deployment Framework, for example. I see your tool has import and export functions but need something that will work with TFS end to end builds.
      
      Thanks and regards,
      
      Rob
    • Thanks Rob for the great feedback. :) As you probably know, I'm a BizTalk guy, so I know exactly what you are talking about. ;) Unfortunately, as far as I know, there's such tool! Look at my sample: http://code.msdn.microsoft.com/How-to-integrate-BizTalk-07fada58. You may start from the Provisioning console application used by the sample to create the queues, topics and subscriptions used by the solution and create a generic command line tool to provisionin Service Bus entities.
      Hope this helps. :)
      Ciao
      Paolo
  • Problem with metrics: 404 not found
    2 Posts | Last post May 21, 2013
    • Thanks for the tool, it's great!
      
      I have just one problem related to metrics. When I configure them for a queue and click "Get Metrics", I get some errors:
      
      An error occurred while retrieving (incoming) metric data for the [Queues/myqueue/metrics] entity: The remote server returned an error: (404) Not Found.
      
      After this "Object reference not set" is shown on the log. The metrics window opens after this but it's empty.
      
      Any ideas?
    • Hi Mikael, 
      I'm investigating the problem right now. Metrics was working fine till a couple of weeks ago. I'll publish a fixed version as soon as I find the issue! Stay tuned!
      Ciao
      Paolo
  • WCF ServiceContract messages
    2 Posts | Last post April 20, 2013
    • Hi Paolo,
      
      Thanks for the great tool! I wish it was advertised more via Azure Portal. 
      
      I have a question about messages sent to the queue via WCF service contract. For some reason I cannot peek or receive messages sent via contracts.
      
      Do you know what might be a reason for that? Thanks!
      
      
    • Hi mate, 
      thanks a lot for the compliments. When using the NetMessagingBinding and WCF to send messages to a queue or a topic, the body of the message gets encoded using the BinaryMessageEncodingBindingElement. Likewise, when using WCF and the NetMessagingBinding to receive a message from a queue or a topic, the body  is decoded using the BinaryMessageEncodingBindingElement. This means, that a consumer app that uses the .NET SB API (e.g. a MessageReceiver object) to receive a message  from a queue or a subscription that has been sent by a publisher app that uses NetMessagingBinding cannot read the message, unless the latter is decoded using the BinaryMessageEncodingBindingElement. Likewise, a consumer app that uses WCF and the NetMessagingBinding cannot read a message sent by a publisher app sent by an app using the SB .NET API (e.g. using the MessageSender class). However, I implemented a trick in the Service Bus Explorer that makes it possible: you can read more about it on the original article on MSDN at http://msdn.microsoft.com/en-us/library/hh532261%28v=vs.103%29.aspx. In a nutshell, if you want to send a message to a WCF receiver, you need to select WCF as Body Type under the Send tab in my tool. This tells the tool to encode the message with the BinaryMessageEncodingBindingElement before sending out. Likewise, when receiving a message from a WCF app, the tool decodes its body using the BinaryMessageEncodingBindingElement . Hope this helps! :)
      Ciao
      Paolo
  • ServiceBus 2.0?
    2 Posts | Last post April 19, 2013
    • In your final statement you say that Service Bus Explorer 2.0 is not compatible with Service Bus for Windows Server 1.0, which from what I can find, is the thing that everyone can download and install.
      
      So is there a later version of Service Bus somewhere that we need to install? Where is it?
    • Hi there,
      at the moment there's no new version for the Service Bus for Windows Server. The product Group is working to a new version that will re-introduce the simmetry between the cloud and on-premises version of the Service Bus. I can't disclose any dates though for the new version. In the meantime, as I wrote in the notes, you can use the old version of the Service Bus Explorer based on Microsoft.ServiceBus.dll 1.8. 
      Ciao
      Paolo
51 - 60 of 65 Items