• Read our blog
  • Follow us on Twitter
  • Follow us on Facebook
  • Connect with us on LinkedIn


You are here:   Tech Support Home >  Downloads >  Patches

General Patch for Responder - Patch #5323 9.3 Rev2


This patch is intended for installation on Responder Client, Server, and Web 9.3 Rev2 (build 5168) and also requires that Responder Patch #5208 be applied and all configuration changes made before installing. This patch has replaced previous patches #5211, #5214, #5242, #5252, #5262, #5269, #5282, #5287, #5290, #5307, #5314, and #5318.

This patch also requires ArcFM Patch #5303 be applied to all Client, Server, and Web machines running 9.3 Rev2 (build 5168). This is required as a feeder manager change was made to correct some behavior in Responder when comparing trace results during incident management. Note - If Patch #5303 gets replaced by a subsequent patch, that new patch will be required prior to installing this patch.

Functionality Included: This patch fixes numerous issues across various parts of the Responder system.

Recommended Users: Clients who use Responder on 9.3 Rev2 would benefit from this patch.

The following files are included in the patch and will replace existing files:

  • Default_rtl.css
  • Default_ltr.css
  • Miner.Data.Decoration.dll
  • Miner.Responder.Desktop.dll
  • Miner.Responder.Explorer.exe
  • Miner.Responder.Framework.dll
  • Miner.Responder.MessageRouter.exe
  • Miner.Responder.PredictionServices.exe
  • Miner.Responder.Processors.dll
  • Miner.Responder.PubSub.dll
  • Miner.Responder.QueryWindowsService.exe
  • Miner.Responder.Shared.dll
  • Miner.Responder.Web.dll
  • Miner.Responder.Web.Base.dll
  • Miner.Responder.Web.DataProviders.dll
  • Miner.Responder.Web.Presentation.dll
  • Miner.Responder.Windows.dll
  • Miner.Responder.WindowsService.exe
  • Prediction.aspx
  • PredictionAssignmentsListControl.ascx
  • PredictionAssignmentsListControl.ascx.resx
  • PredictionInfoControl.ascx
  • PredictionInfoControl.ascx.resx

Installation instructions:

  1. Download the patch installer Patch_930Rev2_5323.exe to any local folder (Client, Server, and Web boxes).
  2. Double-click the file to launch the installation.
  3. At the installer dialog, review the readme information if desired. Then click 'Install Patch'.
  4. When the installer dialog displays 'Completed', click the 'Close' button.

Prediction Web Page Fix in Patch #5318

With this patch, an enhancement was made to how prediction modes are changed from the web. This enhancement now makes it necessary to have your services (data, prediction, and archive) use the same multicast address. You can verify this by looking in each one of the .config files associated with each service (i.e. Miner.Responder.DataServices.exe.config) and finding the multicast tag which is associated with each configuration setting. If the multicast address ( in the example below) is the same across all services, no changes need to be made. If you have a difference, please make sure to update the .config(s) to make them all the same. An example is listed below:

<multicast group="" port="6679" ttl="2" />

Optional configuration for patch #5307 - Query Services Improvements

With patch #5307, you have the ability to configure Responder Explorer to connect directly to Query Services on startup. This will make startup times faster, especially while under load. If you choose not to do this, some requests will go through Data Services until a connection to Query Services is made. When Data Services are under heavy load and Responder Explorer applications are opened up, it could lead to timeouts and slower loading. If you would like to take advantage of the efficiencies of using Query Services exclusively at startup, please follow the steps below:

On all Responder client machines, please open Miner.Responder.Explorer.exe.config and find the line below:

<section name="Miner.Windows" type="Miner.Windows.ConfigBasicInfoHandler, Miner.Windows" />

Below that line, add the following line:

<section name="queryService" type="System.Configuration.IgnoreSectionHandler" />

Next, find the line below:


Below that line, add the following lines:

  <queryService server="localhost" port="2063" enabled="true" />

For the server parameter, change localhost to the machine name that is running Query Services. If you are running multiple Query Services, you can use a comma delimited list of machine names (i.e. "server1,server2,server3").

Optional configuration for patch #5307 - Feature Class Caching

With Patch #5307 you have the ability turn on some additional caching to improve performance of Responder services. Responder services can now be configured to open each feature class in the geometric network at service startup time, and to hold references to the opened feature classes for the lifetime of the process. This practice minimizes schema locks, which improves performance. If you would like to take advantage of this new setting, follow the steps below:

On all Responder server machines, please open Miner.Responder.DataServices.exe.config and find the section of the config which contains your database connection information:

<configuration name="yourConfigName">

Then find the <geodatabase> tag in that section and update the tag to look like the one below:

<geodatabase featureClassCaching="true">

Repeat these sets of steps for Miner.Responder.PredictionServices.exe.config and Miner.Responder.QueryWindowsService.exe.config

If you have previously applied patch #5290, you can skip the steps below:

On all Responder server machines, please open ExplorerRulesConfig.xml and find the line:

<b:RuleClass Key="ValidateTagForInsert" Type="Miner.Responder.Explorer.ValidationRules.ValidateTagForInsert,Miner.Responder.Explorer" />

Below that line, add the following line:

<b:RuleClass Key="ValidateIncidentCauseChange" Type="Miner.Responder.Explorer.ValidationRules.ValidateIncidentCauseChange,Miner.Responder.Explorer" />

A new localizable warning message has been added for QFE41479.

If you wish to localize this warning message, please add the following text just above the </root> tag in Miner.Responder.Explorer.Properties.Resources ResX file on all Responder Server machines:

<data name="MsgCallTroubleTypeWillBeChanged" xml:space="preserve">
    <value>There are {0} calls with {1} = '{2}' assigned to this incident.  Changing the incident's {3} to '{4}' will result in the {1} field being reset to '{5}' for these calls.</value>

After this text is added, it can be localized.

If you have not done so when applying patch #5287 or #5282, then on the database server, please run the following SQL Script, as this is the fix associated with QFE40428:

	    variable MyCount number
	    select count(*) into :MyCount from USER_INDEXES where INDEX_NAME='RX_HAZARDHISTO_INCID_IDX';
	    if :MyCount = 0 then
	    execute immediate 'create index RX_HAZARDHISTO_INCID_IDX on RX_HAZARDS_HISTORY (INCIDENT_ID)';
	    end if;
	    variable MyCount number
	    select count(*) into :MyCount from USER_INDEXES where INDEX_NAME='RX_INCDEVHIST_INCID_IDX';
	    if :MyCount = 0 then
	    select count(*) into :MyCount from USER_IND_COLUMNS where TABLE_NAME = 'RX_INCIDENT_DEVICES_HISTORY' and column_name = 'INCIDENT_ID';
	    if :MyCount = 0 then
	    end if;
	    end if; 
	    variable MyCount number
	    select count(*) into :MyCount from USER_INDEXES where INDEX_NAME='RX_LPHIST_LPID_IDX';
	    if :MyCount = 0 then
	    execute immediate 'create index RX_LPHIST_LPID_IDX on RX_LOADPOINTS_HISTORY (LOADPOINT_ID)';
	    end if;
	    select count(*) into :MyCount from USER_INDEXES where INDEX_NAME='RX_LPHIST_INCID_IDX';
	    if :MyCount = 0 then
	    select count(*) into :MyCount from USER_IND_COLUMNS where TABLE_NAME = 'RX_LOADPOINTS_HISTORY' and column_name = 'INCIDENT_ID';
	    if :MyCount = 0 then
	    execute immediate 'create index RX_LPHIST_INCID_IDX on RX_LOADPOINTS_HISTORY (INCIDENT_ID)';
	    end if;
	    end if;
	    variable MyCount number
	    select count(*) into :MyCount from USER_INDEXES where INDEX_NAME='RX_CALLS_HIST_INC_ID';
	    if :MyCount = 0 then
	    execute immediate 'create index RX_CALLS_HIST_INC_ID on RX_CALLS_HISTORY (INCIDENT_ID)';
	    end if;

Patch #5323 contains the following bug fixes:

  • QFE42703 - Improvements to tree controls
  • QFE42779 - Message router optimizations
  • QFE42840 - Explorer hard refresh times grow with each consecutive refresh
  • QFE42872 - Asynchronous appearance changes cause Switching Order error
  • QFE42941 - Asynchronous appearance changes broke filters in main Explorer Grid
  • QFE42983 - Asynchronous appearance changes added a delay between refresh and appearance application

Patch #5318 contains the following bug fixes:

  • QFE42525 - Prediction settings page on the web times out, especially under load
  • QFE42526 - Improve server side caching for region mode assignments
  • QFE42549 - PubSub disconnect message sporadically occurs on startup, even when a connection has actually been made
  • QFE42572 - Improvements to prediction call query to guarantee that the earliest call gets processed first

Patch #5314 contains the following bug fixes:

  • QFE42290 - Remove load of customers related to calls during Explorer opens and refreshes
  • QFE42297 - Improve application of grid appearances and tree building on opens and refreshes
  • QFE42345 - Improve server side caching
  • QFE42436 - Custom calculated field throws an error in a few different places
  • QFE42456 - Cut not showing loadpoints below sidestream transformer
  • QFE42463 - Remove data updates on hard refreshes

Patch #5307 contains the following bug fixes:

  • QFE41962 - All data requests need to go through Query Services on startup and refresh of Responder Explorer
  • QFE42028 - Dashboard customer view does not handle customer count variations well
  • QFE42084 - Repair Line Display Errors Tool Fails with More than 1000 Incidents Active
  • QFE42088 - Tracing Improvements to increase performance
  • QFE42089 - Improved caching of feature classes to increase performance
  • QFE42157 - Improved shutdown order of Responder services
  • QFE42174 - Feeder Manager is being initialized many times during incident processing
  • QFE42270 - Remove soft refresh from close, cancel and complete operations

Patch #5290 contains the following bug fixes:

  • QFE41473 - Two issues with submitting multiple calls per customer and then changing the incident cause or device status
  • QFE41479 - Callbacks are being generated when they shouldn't be

Patch #5287 contains the following bug fixes:

  • QFE41312 - Need to be able to better support create fault, create switching operation, change fault and update population tools when used with multi-feeds

Patch #5282 contains the following bug fixes:

  • QFE38519 - Two Feeder IDs Showing In A Backfeed When We Expect One
  • QFE39055 - Display Issue With Cancellation Below Source Loop
  • QFE39873 - Notify User that PubSub is down at startup and the data will not be accurate
  • QFE39875 - Transformers Being Treated As Nested Incorrectly
  • QFE40820 - Cancellation of One Outage In Loop Doesn't Reprocess Other Outage
  • QFE40821 - Display Issue With Cancellation of One of Two Faults In a Loop
  • QFE40822 - Display Issue When Restoring One Fault of Two In Loop
  • QFE40430 - Cache user permission set to reduce database IO

Patch #5269 contains the following bug fixes:

  • QFE39389 - Custom Expressions are causing errors when searching on the web.
  • QFE40421 - Feeder ID is incorrect when outage is on subsource when using EFM.
  • QFE40451 - Customization to archive causes messages to be assigned the wrong priority.

Patch #5262 contains the following bug fixes:

  • QFE38923 - Switching operations in looped data create unintended large outage.
  • QFE39047 - Move Upstream and Consolidate tools should skip loops.
  • QFE39222 - Status of devices "chatter" after status change from Responder.
  • QFE39370 - Opening/Closing or Closing/Opening a device in the same switch order causes "restore step" to never complete.

Patch #5252 contains the following bug fixes:

  • QFE38710 - When updating other phone number on the web, it does not update in the database.
  • QFE38721 - Re-opening a device with calls is causing some loadpoints to have an incorrect time of outage.
  • QFE38873 - Archive services needs to log more debug information.
  • QFE38874 - Inefficiency in archive services, need to cache more information.
  • QFE38921 - Build archive from history tool performance enhancements.

Patch #5242 contains the following bug fixes:

  • QFE37510 - Line Display is incorrect during some backfeed scenarios.
  • QFE37511 - Line Display is incorrect during some partial phase outage scenarios.
  • QFE37512 - Line Display does not get removed in some scenarios.
  • QFE37725 - Line Display is incorrect during some isolation scenarios.
  • QFE38075 - Negative Duration error when creating an incident while a restored SCADA incident exists upstream.
  • QFE38117 - Enhancement to find calls in some queries/reports which currently only look for loadpoints.
  • QFE38266 - Predicted incidents lose call trouble.
  • QFE37267 - Restoring upstream incident removes loadpoints from downstream probable incidents.

Patch #5214 contains the following bug fixes:

  • QFE37722 - Nested incidents which contain non-outage calls are not processed correctly in some cases.

Patch #5211 contains the following bug fixes:

  • QFE37713 - Backfeed does not set incident status to restored.
  • QFE37717 - Improper rollup attempt of incidents leaves corrupt data and call stragglers.
  • QFE37752 - Bad performance on Edit Incident in Archive Explorer.

Internationalization updates:

For ArcGIS and ArcSDE issues, please seek assistance from ESRI Technical Support.