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)
95,862 times
Add to favorites
6/21/2017
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • "manage claim is required for this operation"
    5 Posts | Last post February 08, 2015
    • I'm trying to connect to an EventHub on Azure cloud using a connection string. 
      Doing so I always get "Manage claim is required for this operation".
      "Manage" is set as a permission on the respective rule.
      I'm using the correct subscriptionId & cerficate thumbprint. Anything else that needs to be set here?
    • Hi
      Are you trying to use a specific SAS key for a single event hub or a namespace connection string? In the latest case, if the SAS connection string has the Manage access right, it should work. The thumbprint and subscriptionId are not used to connect to the namespace, they are used only when getting metrics on specific entities.
      Ciao
      Paolo
    • I'm using a connection string. Tried with a couple of different rules, both with 'manage' set as permission - both give me the 401 with 'manage claim is required'.
      
    • I was having this error. I was using a cnString to an specific queue, so I changed to the whole namespace cnString. Select service Bus/[namespace] and then [connection information]. Hope it helps.
      
      Thank you Paolo for this excellent tool!
    • Thanks guys ;)
  • Can't Connect To Azure
    2 Posts | Last post December 31, 2014
    • Paolo..I enter my sb://myhub-ns.servicebus.windows.net/ and for namespace I enter myhub-ns but I do not understand what to enter for Share secret issuer name and secret..can you give more details?
      
      thanks
      bob
    • Hi Bob
      Just copy the SAS connection string of your namespace from the Azure management portal and add it to configuration file of the tool. Alternatively, launch the tool, open the connect form, choose Enter connection string from the dropdown list and paste the connection string in the corresponding textbox. Hope this helps. ;)
      Ciao
      Paolo
  • SBE doesn't connect to on prem Service Bus for Windows
    8 Posts | Last post December 02, 2014
    • Paolo,
      
      I'm running SBE 2.1.3.0 to connect to an on-prem Service Bus for Windows 1.1
      When I try to connect, it always results in this error
      
      "<15:48:11> Exception: The token provider was unable to provide a security token while accessing 'https://machine.domain:9355/ServiceBusDefaultNamespace/$STS/Windows/'. Token provider returned message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'.. Method <GetQueues>b__3c: retry 8 of 10.
      "
      
      The Windows Firewall is switched off.
      Do you have any idea what I can do?
    • Hi Peter
      are you running the tool with a user that is part of the manageusers list of users? See Get-SBNamespace, Set-SBNamespace and New-SBNamespace PowerShell cmdlets for more info! Also make sure you can connect to the endpoint of the security token provider from the machine running the tool!
      Ciao
      Paolo
    • All components are on the same machine. The admin user is in the 'magageusers' list. I'm using the admin account. The added the certificate used by the STS in the trusted root store. I still get the same error.
    • Hi Peter
      can you connect to the STS site from the browser? Any error in the application log? In case open an incident with Microsoft. Sorry about that.
      Ciao
      Paolo
    • Hi Paolo,
      
      I created a completely new VM with all components. On that machine SB explorer works fine. I'll have to check my other machine (installed software is the same).
    • Better so :)
    • I was having the same issue connecting to Windows SB 1.1 on-prem, installed on Server and connecting through my local machine.  Resolved the issue by running SB Powershell Get-SBAutoGeneratedCA on the server (saves .cer file to C:\Program Files\Service Bus\1.1) and then installed the exported cert locally in "Trusted Root CAs".  I was then able to connect successfully.
    • Thanks viperguyinaz :-)
  • Minor Issue: Disabled Subscription Icon
    1 Posts | Last post November 19, 2014
    • 1) Go to a topic with 2 enabled subscriptions, both subscription icons show enabled state.
      2) Right click 1 subscription and 'Disable Subscription', icon shows disabled state.
      3) Go to parent 'Subscriptions' node and 'Refresh', the disabled subscription shows an *enabled* icon even though it is disabled.
  • How can I view the body of a message?
    4 Posts | Last post October 24, 2014
    • Using version 2.4.1.1 of the tool. Previous versions showed the message body (admittedly a bit malformed) and you could work out the content.
      
      The new version shows message text as a series of bytes regardless of the message inspector used (Log or Zip). How can I see the actual message body?
      
      Especially for dead-letter messages.
    • Hi Graham
      that is strange. The code should show the message format only when it recognizes the code as binary or you don't select the proper message inspector to decode the content of the payload. I'm quite busy at the moment and I should have sample of the message you use to investigate the problem. I mean, a piece of code that generates and submit the message to queue. By the way, you can investigate the problem as follows: define a breakpoint to the GetMessageText methods (there are 2 overloads) inside the ServiceBusHelper class and see what happens. Should you find a better code to display the message, please send me an email or even better directlky modify the code on GitHub! In fact, the tool is now available as a public Project on GitHub.
      Ciao
      Paolo
    • Hi Paolo,
      
      Ok we sorted this. It appears that by default the message is sent as binary and none of the default message inspectors could handle it. Not sure why as we don't do anything special when sending the message. We made our message send as a serialized JSON string instead and it now works fine as the App sees it as a string.
      
      Not sure if this is an issue now or not (i.e. standard message not handled by default inspectors) but I'll leave that to you to decide
    • Hi Graham
      When you receive messages from a queue or Subscription, you have to explicitly define a message inspector to use! The tool doesn't try to apply any of them if not explicitly selected from the dropdownlist. Hope this helps!
      Ciao
      Paolo
  • Partitioned queues
    4 Posts | Last post October 24, 2014
    • Hi,
      
      Great tool - thanks very much. However when I use this with an Azure Service Bus partitioned queue I get an error along the lines of 'client not supported'. I thought, according to the Azure docs, partitioned queues where hidden from clients?
      
      Will these be supported in a a later release?
      
    • Hi Graham
      I extensively tested the tool with partitioned entities. Could you please contact me on my email account and provide more context? I'm quite biusy in this period, so I'll do my best to answer. Thanks!
      Ciao
      Paolo
    • Hi Paulo,
      
      This appears to have been fixed in the latest version of the tool (2.4.x)
    • Better so ;)
  • Getting list of Success/failed notifications
    2 Posts | Last post September 04, 2014
    • Does service bus explorer provides a list of device id's which successfully received or failed to receive push notification sent through notification hub.Currently i cannot see that anywhere, only a list of registered devices is shown.My aim is to monitor/re-send push to only those devices on which delivery of messages failed.
      
      Thanks
      Vineet
    • Hi Vineet
      When you send a Notification, the outcome is shown in the log. The tool doesn't track on a datagrid which devices received the Notification and which didn't. You may extend the tool to add this feature and send me the code. :) Sooner or later I'll make the tool available on GitHub so that everyone can contribute to its code.
      Ciao
      Paolo
  • SBE does not pull up any data
    2 Posts | Last post September 04, 2014
    • SBE is able connect successfully to my Service bus. 
      
      <18:02:32> The application is now connected to the sb://mybusnamehere.servicebus.windows.net/ service bus namespace.
      <18:02:32> MessagingFactory successfully created
      
      However it does not bring back any information. I have a very simple setup with 2 Http relays. Any ideas what could be wrong? I just downloaded the latest version today 8/20 
    • The Service Bus Explorer shows only Relay Services that are configured to use the ServiceRegistrySettings endpoint behavior (http://msdn.microsoft.com/en-us/library/microsoft.servicebus.serviceregistrysettings.aspx)to make the service discoverable.
      Ciao
      Paolo
  • SBE 2.1.3 Still in Zip File?
    3 Posts | Last post July 22, 2014
    • I can not find the old version 2.1.3 in the zip file.  I am developing for Service Bus 1.1 and would really appreciate having this application.  Is it possible to get source code?
      
      Thanks.
      
      Kevin
    • Hi Kevin
      I forgot to include it! Thanks for the feedback, the 2.1.3 is back in the zip now!
      Ciao
      Paolo
    • For the code of the 2.1.3 ping me offline at my email address (see the About form)
      Ciao
      Paolo
  • Dead letter messages not being consumed
    5 Posts | Last post July 15, 2014
    • Hi Paolo,
      
      I've developed a SOA approach system that used windows azure service bus and WCF.  This has been up and running for the last year.  I'm not using brokered messages though instead the messages are being pulled through automatically into our respective web service.  
      
      The only issue we have is trying to replay the dead letter messages.  The dead letter messages are being put back on the cue but are is not being consumed.  The message before being dead lettered is hitting the code as I've got logging. 
      
      I'm using the WCF message type when repairing and resubmitting the message and I've now tried to use SeanTaR solution in another Q&A and added the below is my services.
      [ServiceBehavior(AddressFilterMode = AddressFilterMode.Any)]
      public class MyConsumer :  IMyContract
      
      Any help would be much appreciated.
      
      Thanks,
      
      Dale
    • Hi Dale
      I should look at the code to give you an answer. Do you have a WCF service using the NetMessagingBinding that reads messages from the deadletter queue of an existing queue or Subscription? What is the url you use to read messages out of a deadletter queue? It should be sb://<your-namespace>.servicebus.windows.net/<queue-or-subscription>/$DeadLetterQueue.
      Ciao
      Paolo
    • Hi Paolo,
      
      I've got a WCF service which is hosted in a cloud service.  I'm using the NetMessagingBinding which is picking up the messages from the normal queue sb://<your-namespace>.servicebus.windows.net/<queue-or-subscription> 
      
      I'm then using the service bus explorer to repair the dead letter messages that are in the dead letter queue to place these back into the main queue.  But when I do this my endpoint is not picking up the messages.   
      
      Thanks,
      
      Dale
    • In this case, make sure to select WCF in Body Type dropdown list. The default is Stream and it doesn't work when sending the message to a WCf service that uses the NetMessagingBinding. Hope this helps.
      Ciao
      Paolo
    • Hi Paolo,
      
      I'm using WCF in the drop down and the netMessagingBinding for my endpoints but still no joy I'm afraid.  I don't know what else to try now.
      
      Regards,
      
      Dale
31 - 40 of 67 Items