How To - Responder - Troubleshooting Responder ArcMap Auto-Refresh

Version 2



    Responder uses Multicast messaging to communicate to ArcMap that there has been a change in the Responder system. Upon receipt of a message indicating the data has changed, Responder will trigger a refresh on a predetermined set of layers to lower the impact of a full refresh.  Listed below are some of the methods available to find and troubleshoot why the automatic refreshes may not be working automatically.


    Although Responder uses different methods for updates to Responder Explorer and ArcMap, it's best to verify that Responder Explorer is actually getting the updates as well or if both clients aren't working.  Most issues are related to Multicast being blocked, which presents itself with both clients not receiving the updates.  Verify that the client has a refresh rate set to an interval such as the 10 seconds below and see if a submitted call comes in on its own:



    2015-02-11 09_11_35-Responder Explorer - Shawn Leingang [nam_sesa220610].jpg






    1. Assuming the message is received by ArcMap, Responder will only update the layers that are included in the Responder grouping which has to match what the configuration is.  Find the name of the group highlighted below for the customer's map:


    2015-02-11 09_04_11-Untitled - ArcMap.jpg





    Make sure this name matches the configuration that Responder is looking for.  This highlighted configuration is in the Miner.Responder.Explorer.exe.config file located in the Responder\Client folder:



    2015-02-11 10_23_42-Miner.Responder.Explorer.exe.config - Microsoft Visual Studio (Administrator).jpg



    2. Newer versions of Responder also contain a troubleshooting tool called the ResponderNotifications.exe located in the Server\Tools folder.  This tool, and the configuration file, can be copied to the Responder\Server on the Responder Server folder and the Responder\Client folder of a machine not receiving the messages.  The configuration file that needs to be set to the Responder Server Name or the Message Router implemented:


    2015-02-11 10_30_39-ResponderNotifications.exe.config_ - Microsoft Visual Studio (Administrator).jpg



    You can then launch the exe from each computer.  It subscribes to the Multicast IP address set in the DataServices configuration.  Also, note the TTL setting and verify it's long enough to traverse the network nodes between the Clients and the Server. 


    2015-02-11 10_34_59-Miner.Responder.DataServices.exe.config_ - Microsoft Visual Studio (Administrato.jpg




    It then shows the traffic it receives from that channel. This can be normal responder traffic or it can be traffic you create using the two buttons on the bottom of the tool:


    2015-02-11 10_39_03-Responder Notifications.jpg


    Pressing the buttons on the client or server should show that the opposite computer received the same message.  Not seeing it arrive on the other side indicates the Multicast message was not received by the remote computer.  Traffic created by Responder, such as new calls or incidents, will show up on both tools on its own.  This setup can be used with your network team to troubleshoot Multicast traffic not traversing the network devices. 


    The IP address can be changed as well in the Dataservices shown above but all Responder applications will need to be restarted if this change is made.