Responder 10.2.1c Release Contents

Responder is a GIS hosted, distributed Outage Management System (OMS). Responder focuses on providing the most valuable information to the right people for storm restoration and daily operations, allowing them to make informed decisions.

New functionality is described in What's New in 10.2.1c.

Responder 10.2.1c contains the following bug fixes:

• RX-16115 - Build from History Tool Should be an Equal Opportunity Employer of All Services.
• RX-16128 - Finish the En Route implementation for crew status or remove the domain value.
• RX-16132 - Multiple incidents refuse to archive.
• RX-16133 - Calls not processing on time.
• RX-16134 - Archive memory limits leaving calls behind when archived.
• RX-16136 - Red X thrown in specific data condition.
• RX-16142 - New Model name manager VERY slow on large data sets.
• RX-16143 - OutOfMemoryException on large data.
• RX-16144 - IEEE Standards need updated and Verified.
• RX-16147 - Identify Causes ArcMap Crash.
• RX-16155 - Validation error message never goes away while creating a new SO request.
• RX-16157 - Zoom to Results not honored by Responder Tracing tools
• RX-16158 - Responder Downstream Elements Return tie devices.
• RX-16159 - Error thrown on editing time of location call.
• RX-16160 - Incident Information on Customers doesn't show on invalid data.
• RX-16166 - Adding the Jumpers Tool to a toolbar renders ArcMap useless when logging in as ArcFM Viewer license or no license.
• RX-16183 - Responder "To Date" reports don't include current day.
• RX-16185 - Error adding requests with no regions selected.
• RX-16187 - Highlight does not work when broken layers are present above the highlighted feature in the stored display.
• RX-16191 - Custom fields allow incorrect characters.
• RX-16192 - Decimal separator cannot be entered into Real, Decimal, Float fields.
• RX-16193 - Step Down tool not honoring call times.
• RX-16195 - Resolving a Non-Electric Incident allows a future Time Restored Actual.
• RX-16196 - Calls not being processed if there is a DNO tag on it.
• RX-16197 - Remove Configuration and documentation for disabling the enhanced prediction modes.
• RX-16200 - Update Population Info button is enabled and results in an error when logging as ArcFM Viewer license or no license.
• RX-16207 - Support Nested SCADA Momentaries.
• RX-16214 - Failure to remove leftover tags.
• RX-16220 - Invalid Status Message thrown for a valid configuration.
• RX-16221 - Switch Order Report Doesn't Honor the line breaks in Remarks.
• RX-16223 - Same Phase Restoration Example is Failing.
• RX-16228 - Responder Continues to trace on multiple edges even if they are non traceable.
• RX-16230 - Invalid call data not getting analyzed.
• RX-16243 - Archive failing on constraints in the RX_Customers_Archive table.
• RX-16246 - Cannot execute switch order when multiple tasks on the same device have scheduled times.
• RX-16259 - Error On Archive Explorer/ Responder Explorer startup.
• RX-16272 - StopTimeout setting not working with Line Display.
• RX-16302 - Issue with Prediction and Loadpoint Phasing.
• RX-16311 - Responder Services Crashing from Port Scans.
• RX-16313 - Responder Web Installer not detecting IIS 10.
• RX-16314 - Responder Windows Service Failing to Start if Line Display is Running.
• RX-16340 - Error on Explorer startup.
• RX-16370 - Xupdate scripts do not work on Server 2012 r2.
• RX-16371 - Excessive null reference errors.
• RX-16372 - PubSub Updates not being applied on RXIF integration incidents.
• RX-16432 - Calls under SCADA incidents don't respect call threshold.
• RX-16488 - UpdatePopulationInformation tool fails for IgnoreMultipleFeedPathsReturnZero option.

Upgrade Information

All upgrade information is on myArcFM.

Installation Instructions

Perform the following steps, in sequence, to install Responder Client, Responder Business Server, Responder Web Server, and Responder TroubleMaker:

1. Navigate to GIS Downloads.
2. Double-click the Microsoft installer file for this product.
3. Follow the instructions to complete the installation.

Known Issues

• XY and Join Layers Search/Locate Issue on Map Viewer - Clients who use the Responder Web Map Viewer or Switch Order Request Map cannot use the Search tool on XY Event and Join Layers. These layers are excluded from the drop down of available layers for this tool. We recommend using Query Layers instead of XY layers.
• XY Layer Identify Issue on Map Viewer - Clients who use the Responder Web Map Viewer and the Identify tool can only use the 'Replace' Selection Management option when XY layers are in the result set. A warning message appears when XY layers are in the result set and any other Selection Management option is chosen. In addition, the Lock tool does not function for rows in XY layers, and no results are returned if identifying on an XY layer that is based on a table rather than a view. We recommend using Query Layers instead of XY layers.
• Join Layer Wildcard Search Issue on Map Viewer - Clients who use the Responder Web Map Viewer or Switch Order Request map cannot use the LIKE search with Join layers. The LIKE search works for all layers that do not include joins. (ESRI Bug NIM094565)
• Join Layers Identify Issue on Map Viewer - Clients who use the Responder Web Map Viewer or Switch Order Request map and use the Identify tool on Join layers may notice that the joined table displays all blank fields in the Attribute Viewer. (ESRI Bug NIM092161)
• Log in to ArcMap - After upgrading an .mxd or Stored Display to 10.1 or later, you are required you to log in again once per session when trying to use Responder tools that interact with ArcMap on an Oracle database. This issue can be avoided by saving your Stored Display again after logging in to 10.1 or later.
• Error Message - You may intermittently receive the following exception error message:
  "System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index"
  A supported hotfix is available from Microsoft. View the following article and follow the instructions to install the hotfix: http://support.microsoft.com/?kbid=836874.
• User Account Control - Users running a Microsoft Windows operating system utilizing User Account Control (Windows Server 2008, Windows 7) must run the ResponderPubSubViewer application in Windows XP compatibility mode so the application can write to log files. To do this, complete the following steps:
  • Browse to your Responder installation directory and select the Server subfolder.
  • Right-click ResponderPubSubViewer.exe.
  • Select Properties.
  • On the compatibility tab, check "Run this program in compatibility mode for" and select Windows XP.

For more information on User Account Control and how it interacts with Schneider Electric products, see ArcFM Solution and Windows 7.

• Switch Order User Interface with RTL Environment - Windows Presentation Foundation 3.5 SP1 has a known issue that causes all drag and drop targets to not be properly mirrored when using a right-to-left flow. This causes incorrect drag and drop feedback to users when dragging items in the Switch Order user interface and Switch Order Library. This issue is expected to be fixed in the .NET Framework 4.0.
• Web Logon - When using the Responder web for the first time, you can use the Username of administrator with a password of adminpass.
• Unicode Characters - To support Unicode Characters in your database, you must change all fields with a VARCHAR datatype. In Oracle, you need to change the VARCHAR2 to NVARCHAR2, and in SQL Server, change the VARCHAR to NVARCHAR.
• Oracle Server and RCS Server - The RCS Server should not be installed on the same machine that contains the Oracle Server, or errors will be received.
• Multiple-Database Setups and Direct Connect with SQL Server - Direct connections to a SQL Server database, that have a multiple-database setup, result in Responder services that intermittently throw an error to the event log:
  "System.Exception: Failed to open FeederSpace --> System.Runtime.InteropServices.COMException (0x80041538): Underlying DBMS error"
  There are no side effects of this error, and your services will work as normal.
• Windows 10 - Windows 10 users will notice less clarity in the grid due to a limitation of the underlying grid technology. (RX-16553)
• Help - Our context sensitive help opens two tabs in a web browser. (Esri BUG-000096609)

License Manager

Responder requires the appropriate License before the application can be accessed. Responder has four types of license files:

• ResponderDataServices - This license is used by the data server (server.exe) on the business server. You can run multiple instances of the data server on a single server using only one license.
• ResponderDispatcher - This license is used by the client server when the user opens ArcMap with a valid Responder license.
• ResponderExplorer - This license is used by the client server when the user opens Responder Explorer.
• ResponderPrediction - This license is used by the prediction engine (prediction.exe) on the business server. You can run multiple instances of the prediction engine on a single server using only one license.

Documentation

Schneider Electric no longer ships static help files with each software release. All ArcFM Using and Configuration guides are available in the ArcFM Solution Resource Center. The guides are updated on a regular basis. You can view this information before installing the latest release.