Salesforce

Responder 10.6.1a SP1 ReadMe

Printable View
« Go Back
Information

Responder 10.6.1a SP1 ReadMe

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.

There is no new functionality for Responder in 10.6.1a SP1.

All patches released on Responder 10.6.1a are automatically included in Responder 10.6.1a SP1.

Responder 10.6.1a SP1 contains the following bug fixes:
  • CLS-70822 - Calls never appear in Incident Details grid if the incident is edited before calls load.
  • CLS-73325 - Find does not work in Tag and Ground Steps table.
  • CLS-73694 - Change Fault should not be available on restored devices.
  • CLS-73773 - Certain Calls Not Posting Properly.
  • CLS-74007 - Responder Snapping only works on default version.
  • CLS-74435 - Unable to Select Replacement For Deleted Device When Grounds or Jumpers Present.
  • CLS-67302 - Ping Downstream Meters from Explorer pings MCSP meters multiple times.
  • CLS-73083 - RX IVR integration crashes data services.
  • CLS-73893 - Maximum Customer Count Invalid On Incident Report With Certain Data.

 

ReadMe Links:

This service pack includes fixes from all the following:

 

    Upgrade Information

    All upgrade information is available in Upgrade to 10.6.1a.
     

    Installation Instructions

    PRE-INSTALLATION NOTES

    • The installation files for version 10.6.1a SP1 are NOT complete installations. To install 10.6.1a SP1, you must have 10.6.1a installed.
    • Ensure that your hardware and software meet the ArcGIS system requirements.
    • Ensure that your hardware and software meet the 10.6.1 - 10.6.1a Responder Server - Supported Version.
    • To those who have not upgraded to ArcGIS 10.6.1, Responder 10.6.1a SP1 requires a complete upgrade to ArcGIS 10.6.1. ArcGIS must be upgraded before you upgrade to Responder 10.6.1a SP1.
    • When you upgrade to Responder 10.6.1a SP1, you must upgrade all ArcFM Solution products. Mixed versions of ArcFM Solution products are not supported.
    • Responder 10.6.1a SP1 requires that you have ArcFM 10.6.1a installed.
    • Anti-Spyware must be disabled before installation to avoid interference with the installation. They may be restarted after installation is complete.

    IMPORTANT

    • Install the applications in the following order. Installing out of order can cause errors.
      1. Responder Client
      2. Responder Server
      3. Responder Web Server
      4.  Responder TroubleMaker
    Perform the following steps, in sequence, to install Responder Client, Responder Server, Responder Web Server, and Responder TroubleMaker:
    1. Navigate to Downloads.
    2. Double-click the Microsoft installer file for this product.
    3. Follow the instructions to complete the installation.
    Responder was updated in 10.6.1a to use Oracle Managed Driver to connect to Oracle databases. After creating the tnsnames.ora file, the Managed driver needs to know where the file is located. Access System Properties, then add the Variable Name TNS_ADMIN as an environment variable. 
    Set the Variable value to the path where the tnsnames.ora file resides. For example: C:\app\client\username\product\18.0.0\client_1\network\admin

     

    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)
    • 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.
    • 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.
    • 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 licenses before the application can be accessed. Responder has four types of license files:
    • ResponderDataServices - This license is used by the data server on the 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 when the user opens ArcMap with a valid Responder license.
    • ResponderExplorer - This license is used by the client when the user opens Responder Explorer.
    • ResponderPrediction - This license is used by the prediction engine on the server. You can run multiple instances of the prediction engine on a single server using only one license.
    • Responder AMI Adapter - This license is used by the AMI Services when processing events from smart meters.
    • Responder CIS Adapter - This license is used by the CIS Service when syncing a customer database with the Responder database.
    • Responder IVR Adapter - This license is used by the IVR Service when processing calls from an IVR system.
    • Responder SCADA Adapter - This license is used by the SCADA Services when processing events from a SCADA system.

    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.
    Additional Information
    Responder 10.6.1a SP1 ReadMe
    Andrew Sauer
    Responder-10-6-1a-SP1-ReadMe
    Knowledge
    Published
     
    Powered by