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


  • 555-555-0199@example.com
    1 Posts | Last post October 13, 2017
    • 555-555-0199@example.com
  • ServiceBusExplorer Giving Exception
    3 Posts | Last post July 13, 2017
    • Hi,
      I am trying to verify the event which ever i have send to topic using my subscription.but when i try to open subscription in SBE it is not showing the option to see the details of event and same time it was giving exception.
      can any one help me on resolve this issue?
      
      Exception Message:
      =================
      <14:40:26> The application is now connected to the sb://ordercreatedstub.servicebus.windows.net/ service bus namespace.
      <14:40:26> MessagingFactory successfully created
      <14:40:30> The topic ordercreated has been successfully retrieved.
      <14:40:30> The subscription AllMessages for the ordercreated topic has been successfully retrieved.
      <14:40:30> The rule $Default for the AllMessages subscription of the ordercreated topic has been successfully retrieved.
      <14:40:30> The subscription ordercreated.event.endpoint for the ordercreated topic has been successfully retrieved.
      <14:40:30> The rule $Default for the ordercreated.event.endpoint subscription of the ordercreated topic has been successfully retrieved.
      <14:40:35> Exception: Index was out of range. Must be non-negative and less than the size of the collection.
      
                 Parameter name: index
      <14:40:38> Exception: Index was out of range. Must be non-negative and less than the size of the collection.
      
                 Parameter name: index
      <14:41:37> Exception: Index 0 is out of range.
      
                 Parameter name: index
      
    • Hi, did you manage to find a solution to this issue?  I can run on my Win 7 Pro with no issues, but see this exception when running on Win 7 Enterprise laptop.  Version 3.0.4.
    • You can get latest versions at :
      https://github.com/paolosalvatori/ServiceBusExplorer/releases
  • Windwos Service Bus Compatible version Source Code
    3 Posts | Last post March 12, 2017
    • Hi 
      I would like to access the version 2.1 that is compatible with Windows Service Bus 1.1. Unfortunately, the one drive link in your description section is no more working. Can you please help with the source
      
      Thanks
      -Pravin
    • Hi Pravin
      Try this link: https://1drv.ms/u/s!AmUKNmugpNsJrgKSItfhDqF4sx2z 
      Ciao
      Paolo
    • I'm getting 403 error trying to download the zip file with that link. Can you assist. Thanks
  • Connection to service bus Explorer giving error
    2 Posts | Last post October 13, 2016
    • Hi,
      I am using windows service in windows server machine. I am trying to connect to it with SAS connection string. i am seeing error as 
      <20:28:37> The application is now connected to the sb://<<hostname>>.servicebus.windows.net/ service bus namespace.
      <20:28:37> MessagingFactory successfully created
      <20:29:16> Exception: The remote name could not be resolved: '<<hostname>>.servicebus.windows.net' TrackingId:61f4da20-574e-4d9f-b5e4-4c287df1236f,TimeStamp:10/12/2016 2:59:16 PM
      <20:29:16> InnerException: The remote name could not be resolved: 'hyd-onebox55.haicpm.com.servicebus.windows.net'
      
    • Hi Vijay
      You probably meant that you are using the on-premise version of the Service Bus on a windows server machine, right? The current version of the Service Bus Explore does not support Service Bus for Windows Server. You need to use the version 2.1.3 of the tool which is available at https://1drv.ms/u/s!AmUKNmugpNsJrgKSItfhDqF4sx2z.
      Ciao
      Paolo
  • Service Bus Explorer 1.0
    1 Posts | Last post June 01, 2016
    • We have Service Bus 1.0 installed on our servers and need to use Service Bus Explorer 1.0 .where can we find that version?Is it still available?
      
      
  • Error 407 Proxy
    1 Posts | Last post May 19, 2016
    • If you are using a proxy add this to your app config file credit to https://connectedpawns.wordpress.com/2014/04/01/microsoft-azure-examples-the-remote-server-returned-an-error-407-proxy-authentication-required/
        
      <system.net>
          <connectionManagement>
            <add address="*" maxconnection="50" />
          </connectionManagement>
          <defaultProxy useDefaultCredentials="true">
          <proxy bypassonlocal="True" usesystemdefault="True"/>
          </defaultProxy>
        </system.net>
  • On-premises version of Service Bus
    3 Posts | Last post March 17, 2016
    • Hi Paolo,
      
      Is there a version that supports on-premises version of Service Bus?  (RE: your comment on February 19, 2016).
      
      Is there any test harness or management client to inspect the Service Bus for Windows?  I have used this tool for Service Bus in Azure with ease but am trying to get the same functionality for on-premises. 
    • ^--- to answer my own question, within the download package for Service Bus Explorer, there is a zip called 2.1.zip which contains the version for Service Bus on premises (specifically, version 2.1.3).
      
      When connecting to the Service Bus on premises, use the 'custom connection string' option and place the entire endpoint 'connection string' in there.  I wish this was documented above but nevertheless, it wasn't too hard to figure out.
    • ^-- apologies:  it is written so in the very first section under Description point #2. <smacking head>
  • The token provider service was not available
    2 Posts | Last post February 19, 2016
    • Hello,
      I have a server 2008 R2 vm which is in a domain.
      I have Service Bus for Windows Server v1.1 and I am using SAS authentication in my prototype code.
      When I try to create a Queue in my namespace using Service Bus Explorer v2.1.3.0 I get the following exceptions:
      
      <15:45:43> Exception: The token provider service was not avaliable when obtaining a token for 'https://servicebusdefaultnamespace-sb.accesscontrol.windows.net/WRAPv0.9/'.. Method <CreateQueue>b__7c: retry 1 of 10.
      
      This retries 10 times and then I get:
      
      <15:48:09> Exception: The token provider service was not avaliable when obtaining a token for 'https://servicebusdefaultnamespace-sb.accesscontrol.windows.net/WRAPv0.9/'.
      <15:48:09> InnerException: The token provider service was not avaliable when obtaining a token for 'https://servicebusdefaultnamespace-sb.accesscontrol.windows.net/WRAPv0.9/'.
      
      I have tried connecting to the namespace using CustomConnectionString or WindowsAzureServiceBusConnectionString and specifying the Shared Secret Issuer Name and Issuer Secret as reported in the Service Bus Config log created during Service Bus installation.
      
      Would be grateful if you could let me know how to resolve this.
      
      John Tresadern
      
    • Hi John, the latest version of the tool does not support the on-premises version of the Service Bus.
      Ciao
      Paolo
  • Error while connecting to namespace with RootAccessKey for all entities
    1 Posts | Last post January 26, 2016
    • Hello,
      
      We have been using the SBE too to browse the notification hubs, check the number of subscriptions, send test push notifications, ets.
      We usually connected using a RootManageSharedAccessKey for the namespace from the management portal and inputting it as a Connection string "Enter a connection string", and getting a 500 after a while. 
      
      Recently we weren't able to use this method at all. It just got stuck after "Messaging Factory successfully created". Then, we started connecting by unselecting all the "Selected entities" but the Notification Hubs.
      
      I just leave this here to let you know about this small bug an also the workaround we found.
      
      Thanks for your work on this excellent tool.
  • Metric combo box is blank
    2 Posts | Last post January 07, 2016
    • Paolo -
      First - thank you so much for this great tool! We are currently using the Azure Service Bus and SignalR to communicate from a web client to legacy systems via BizTalk 2013. I am exploring monitoring in the Service Bus Explorer, but for some reason do not see any values in the Metric combo box -
      F7 - Open Metrics in SDI mode
      Click on a row, select a Queue
      Metrics Rules now has one row, Entity = selected queue, Type = Queue, Metric - combo box with no values.
      
      Are we missing a certificate or configuration step in Azure to enable this?
      
      Thanks!
      Brad Cote
      
      
    • Hi Brad
      The tool used to have metrics for entities such as queues and topics hard coded in the source code. Then I changed the code to dynamically load the proper metrics depending on the selected entity. Hence, when accessing metrics at the namespace level, make sure to click the Entity column and select an entity first: metrics for the current entity will be dynamically retrieved the first time you select an entity of that kind and the Metric dropdown list will be populated with this data. Hope this helps.
      Ciao
      Paolo
      
      P.S. You can also access metrics at the entity level using the Metrics tab.
1 - 10 of 65 Items