The 10.8.1a installers act as complete installers for versions of ArcFM Solution prior to 10.8.1, and upgrade installers for ArcFM Solution 10.8.1 and newer. As such, you will first need to uninstall any version of your product that is below 10.8.1 before installing ArcFM Solution 10.8.1a. If your current version of ArcFM Solution is 10.8.1 you can install ArcFM Solution 10.8.1a over your current installation. This page outlines the upgrade steps for various ArcFM Solution applications. These are basic required upgrades and do not include configuration for new tools. If you are skipping release versions (e.g., upgrading from 10.2.1 to 10.8.1a), note the following:
DO NOT install each release in between. Only install the version to which you are upgrading.
DO review the upgrade documentation for each release in between the original version and the one to which you are upgrading. Ensure that your environment meets any requirements set forth in these documents (for example, recommended Esri patches) and that any other necessary changes required by intermediate upgrade steps have been performed. Upgrading the geodatabase only needs to be done on the version to which you are upgrading, but additional steps may be necessary when upgrading specific products such as Geodatabase Manager, Responder, and Designer.
DO run the Create/Update ArcFM Solution System Tables tool only once. There is no need to run it multiple times.
DO run the Upgrade ArcFM Solution Database tool only once. There is no need to run it multiple times.
DO review the What's New page for each release in between to learn about the new functionality available to you.
DO review the Migration pages for each release in between to understand if you need to compile custom code.
On upgrade to 10.8.1a, make sure to upgrade your Geodatabase as per the typical ArcSDE process.
Minimum required .NET framework version for 10.8.1a is .NET 4.6.1.
Any custom log4net references should point to 2.0.12.0 instead of the previously referenced 2.0.8.0.
Licensing Note: When upgrading to 10.8.1a from a version prior to 10.6.1, you must obtain new 10.6.1 version licenses. Learn how to request a new license in How-To - ArcFM - Request a License. Contact Schneider Electric with licensing questions. Sample Data Note: Our Sample Data is now being delivered as .zip files rather than as self-extracting .exe’s. The data can be used the same as always, and it can be extracted to the location of your choice.
The Migrate to 10.8.1a document provides a list of API changes for 10.8.1a. Be sure to review the API changes and perform any migration steps for releases between your original version and the one to which you are upgrading.
Upgrade Conduit Manager
Multiple Cables Per Field can be configured for Conduit Manager if desired. This is optional functionality and Conduit Manager will work as it did prior to this enhancement if you don't choose to configure it. If you'd like to take advantage of this new functionality see the Using Guide topic Number of Cables for details how to set it up.
Upgrade ArcFM Designer Express
This applies to Designer Express users only. Designer Express users need to perform the ArcFM Geodatabase upgrade steps as well.
Update Tables - If you have installed a previous version of Designer Express, you must run the Designer Express Configuration Wizard to update the system tables. You are not required to create and configure an Express Work Location DFC, but you must update the system tables.
NOTE: This is only necessary if you are upgrading from a version prior to 10.2.1c.
Upgrade ArcFM Geodatabase
This applies to all geodatabases being upgraded. If you are using ArcFM Geodatabase Manager, you must upgrade GDBM prior to upgrading your geodatabase, otherwise upgrading your geodatabase should be done prior to performing any other upgrades such as Designer and Fiber Manager. If you are skipping release versions (e.g., upgrading from 10.2.1 to 10.8.1a), review the upgrade documentation for each release in between your original release and the one to which you are upgrading. Perform any relevant upgrade steps such as installing recommended ESRI patches. The Create/Update ArcFM Solution System Tables and Upgrade ArcFM Solution Database tools only need to be run once with each upgrade.
Execute the Create/Update ArcFM Solution System Tables tool with each upgrade. The ArcFM System Tables must be located in the same schema as the SDE system tables. When running this tool, you must be connected to the geodatabase as the user who owns the .Default version. All other users must be disconnected from the database. Running this tool is required.
Use the Upgrade ArcFM Solution Database button to update your geodatabase with modifications required by the latest release. This button remains enabled on the ArcFM Solution toolbar in ArcCatalog. You must be signed in as the owner of the business data to upgrade the database, and you must be connected to an editable version. This tool also requires that there be a single owner for all GIS tables.
If you are running Terminal Services, it must be running in Install Mode.
Upgrade ArcFM Geodatabase Manager
You will need to check for files located in the Bin folder of your ArcFM Geodatabase Manager install location
GdbmConfiguration.xml
GeodatabaseManagerAdmin.exe.config
GeodatabaseManagerMonitor.exe.config
GeodatabaseManagerServices.exe.config
Typically the Bin folder is located at C:\Program Files (x86)\Miner and Miner\ArcFM Solution\Bin on a 64-bit system. Check for any of the following three entries in all the files listed above:
You will need to check for ReplicationConsole.exe.config located in the Bin folder of your ArcFM Geodatabase Replication install location.
Typically the Bin folder is located at C:\Program Files (x86)\Miner and Miner\ArcFM Solution\Bin on a 64-bit system. Check for any of the following three entries in this file:
You will need to check for Web.config located in the ArcFMGDBReplicationService folder of your ArcFM Geodatabase Replication install location.
Typically, the ArcFMGDBReplicationService folder is located at C:\inetpub\wwwroot\ArcFMGDBReplicationService. Check for any of the following three entries this file:
When upgrading Network Adapter to 10.8.1a from any prior release, you must replace "old" with "new" for cases 1 and 2 below. This is for an upgrade to log4net. NOTE: Any custom log4net references should point to 2.0.12.0 instead of the previously referenced 2.0.8.0.
To upgrade from Network Adapter 10.2.1 and earlier without starting from an entirely new configuration file, follow these steps in NetworkAdapter.Config (this file is typically found in C:\Program Files (x86)\Miner and Miner\ArcFM Solution\Bin):
Replace all instances of 10.1.0.0 to 10.8.0.0.
Make sure to update instances of assembly names in your database configuration sections as well to 10.8.0.0, provided you are upgrading these databases to 10.8. If you are upgrading from 10.2, then these will be at version 10.2.0.0. If you are upgrading from 10.6, then these will be at version 10.6.0.0.
After the </system.serviceModel> end tag, add the following XML block:
IMPORTANT: Remove the semicolon (;) after ESRI.ArcGIS.System and ESRI.ArcGIS.Geodatabase shown in the codeblock above before using.
Upgrade Fiber Manager
NOTE: Changes were made around CLS-58365 that change underlying behavior when you re-parent connected items in location editor or re-parent items with connected children. Fiber Manager now deletes those connections and updates any affected circuits. This way data is not corrupted by having connections to re-parented objects that aren't physically possible.
To upgrade from Fiber Manager 10.2.1 and earlier, follow these steps (if you are upgrading from 10.2.1a or later, you can skip these steps):
Check your data to ensure that all your circuits have header information. See the Fiber Header Migration PDF for best practices. If all your circuits have header information, proceed to the next step.
Install ArcFM Solution Desktop 10.8.1a.
Install Fiber Manager 10.8.1a.
Configure your geodatabase with the new circuit model. See the Fiber Manager Configuration Guide for information on how to do this.
Run the Fiber Circuit Upgrade tool if existing circuits are present in your data (review the Fiber Circuit Upgrade Tool for more details).
Important notes concerning Fiber Manager 10.8.1a configuration:
New Fiber Manager functionality allows users to see blocks in their reports and not only stripes as in prior versions. This functionality was introduced at 10.6.1a, so if you are upgrading from 10.6.1a you can ignore this. To see the blocks, users need to delete the .xsl. and .xslt files stored on their machine. For additional information on where those are located, see the Report Locations topic in the Fiber Manager Using Guide. Before deleting any files, be sure to consider if there any custom xsl or .xslt files that shouldn't be replaced with the latest out of the box version. This new functionality affects reports that show fiber coloration and does not affect the Cable Report, the Patch Panel Connection Reports, the Glass Report, or the OTDR Trace report.
If you are upgrading from 10.6.1b, you can ignore this note. An update at 10.6.1b addresses an issue with the Cable Report. It requires users to delete the .xsl. and .xslt files stored on their machine in order for Cable Reports to generate properly.. For additional information on where those are located, see the Report Locations topic in the Fiber Manager Using Guide. Before deleting any files, be sure to consider if there any custom xsl or .xslt files that shouldn't be replaced with the latest out of the box version. This only affects the Cable Report.
Upgrade Responder
This applies to Responder users only. Responder users need to perform the ArcFM Geodatabase upgrade steps as well.
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. If you are upgrading from 10.6.1a or later, you can skip this step as you already completed it during the 10.6.1a install.
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
This applies only if you are upgrading from the 10.2.1d release OR PRIOR to 10.6.1 OR LATER. The first time a user attempts to log in to Responder Web after it has been upgraded to 10.8.1a, they are required to go through the Password Reset process, as we have changed to a more secure password hashing algorithm. Once the password has been reset with the new algorithm, users can log in as usual. Once the administrator has determined that enough users have upgraded to the new algorithm, they can turn off the reset process for users who have not yet upgraded. The administrator can reset passwords for these users. See the Responder configuration documentation for more information. For client sites that do not use the Responder Web Password Reset process (for example, they haven’t configured their SMTP to send Password Reset emails for Responder Web), we offer two additional options. First we have provided a script (Reset Responder Admin Password - 10.6.1 - Oracle.sql or Reset Responder Admin Password - 10.6.1 - SQL Server.sql depending on your RDBMS) that will reset your administrator account password to ‘adminpass’, allowing the administrator access to Responder Web, where any/all user passwords can be reset from there. Secondly, we’ve provided a script (Reset All Responder Passwords - 10.6.1 - Oracle.sql or Reset All Responder Passwords - 10.6.1 - SQL Server.sql depending on your RDBMS) that will reset the administrator account and all other user account passwords to ‘adminpass’, which would allow each user login access, at which point their passwords could then be individually reset. The aforementioned scripts are available on myArcFM by following the link below. https://myarcfm.schneider-electric.com/myarcfm/s/detail/0693600000BNYejAAH
Long Term Device functionality added at 10.6.1b requires certain steps to be completed according to whether you use Oracle or SQL Server. This is required for all users upgrading to 10.8.1a from a version prior to 10.6.1b. To update, follow the steps outlined in Long Term Device Updates for Responder.
Updates to a View and a Trigger related to the new Incident Review tool at 10.6.1a requires steps to be completed according to whether you use Oracle or SQL Server in order to get the updates. This only has to be done once, so if you completed the steps at 10.6.1a, 10.6.1b, or 10.8.1, you don't have to complete it again at 10.8.1a. The steps are outlined in View and Trigger Updates.
When upgrading from previous versions of RxIF, after each component is uninstalled, the configuration file for that component is left on the file system. This configuration file can not be removed or updated by the installer. When the 10.8.1a installer is run, any values entered into the installation dialog will not be saved in the configuration file. This includes database connection settings, MSMQ Server, and Web Application Pool information. It is recommended that these files be renamed or moved to another location if you wish to change any of this information during upgrade.
Upgrade Tables - If you have installed a previous version of Responder, execute upgrade scripts for all versions between the current release and your original release, but note that there are none for 10.8.1, as there were no table changes for this latest release. For example, if you have 10.1 and plan to upgrade to 10.8.1a, you will need to run the scripts for 10.1.1, 10.2.1, 10.2.1a, 10.2.1b, 10.2.1c, 10.2.1d, 10.6.1, 10.6.1a, 10.6.1b, and 10.8.1. This provides the tables, views, and indices necessary for Responder. Execute these scripts on your Responder database. Upgrade scripts do not exist for the 10.2 and 10.2.1 releases as they were not necessary.
Upgrade Configuration - After installing the Responder components, run the installed batch script for each component to automatically update the various configuration files. If you are skipping releases, you must execute the batch scripts for each release between the one you started with and the one to which you're upgrading. For example, if you have 10.1 and plan to upgrade to 10.8.1a, you will need to run the batch scripts for 10.1.1, 10.2, 10.2.1a, 10.2.1b, 10.2.1c, 10.2.1d, 10.6.1, 10.6.1a, 10.6.1b, 10.8.1, and 10.8.1a. Upgrade scripts do not exist for the 10.2.1 release as they were not necessary. If you are installing Responder for the first time, this step is not necessary. Each Responder component (client, server, web) has its own batch script. Just double-click it to execute. These scripts are installed at the following locations:
Client: Program Files (x86)\Miner and Miner\Responder\Developer Resources\[Upgrade for current release]\Config\UpgradeClient.bat
Server: Program Files (x86)\Miner and Miner\Responder\Developer Resources\[Upgrade for current release]\Config\UpgradeServer.bat
TroubleMaker: Program Files (x86)\Miner and Miner\Responder\Developer Resources\[Upgrade for current release]\Config\UpgradeTroubleMaker.bat
Web: C:\Inetpub\wwwroot\Responder\Developer Resources\[Upgrade for current release]\Config\UpgradeWeb.bat. If your Inetpub directory exists on drive other than C:\, you will need to modify the UpgradeWeb.bat file to point to the correct directory.
The following updates are for Responder Integration Framework only. Run these after the non-RxIF Xupdates are finished. Not all Responder customers will need to do this step, only those using the Responder Integration Framework (RxIF).
RxIF Server: Program Files (x86)\Miner and Miner\Responder\Developer Resources\[Upgrade for current release]\Config\RxIF\UpgradeServer.bat
RxIF: Program Files (x86)\Miner and Miner\Responder\Developer Resources\[Upgrade for current release]\Config\RxIF\UpgradeRxIF.bat
Manual Configuration (optional): There are a few cases in which you may need to manually configure files instead of using the batch scripts:
The batch script fails. Some customizations to the configuration files may cause the upgrade script to fail.
NOTE: If a manual update is required, be sure to back up the original configuration files before making any changes. Configuration files for the current release are installed in the following locations:
Client and Server: Program Files (x86)\Miner and Miner\Responder\Developer Resources
Copy the files from the Developer Resources folder and paste them over your original configuration files.
Configure the files with your connection information, etc. If you have modified any feature class IDs, names, or model name assignments, clear the FacilityTypes*.cache files from the cache on the business server. The FacilityTypes files in this directory become out of date and must be deleted manually.
Browse to the Cache folder in the Application Data directory for the current user on the business server (e.g., C:\Documents and Settings\[user name]\Local Settings\Application Data\Miner and Miner\Responder\Cache).
In the Cache directory, select all files that start with FacilityTypes and press Delete on the keyboard.
Additional information on performing an upgrade is available in the Responder Help.
New Users: If you are installing Responder for the first time at Responder 10.8.1a, please follow the Installation Information section of the Responder 10.8.1a ReadMe, refer to the Responder help, and disregard the following Upgrade Information section of this Upgrade doc.
Important notes concerning Responder 10.8.1a configuration:
If you have existing incidents in your grid when you upgrade to 10.8.1a from a release PRIOR to 10.2.1d, those incidents will not work with the new Multiple Incidents for One Device functionality.
For any client upgrading from 10.6.1 OR EARLIER to 10.6.1a OR LATER, a bug was fixed in a Stored Procedure at 10.6.1a which can't be done automatically, as Stored Procedures can't be altered without a full drop and re-add, which could cause any customizations to be lost. Clients that fit this description and would like the fix in CLS-69025, need to update the stored procedure Rx_prediction_nextcall by finding the line "where INCIDENT_ID is null" and changing it to "where INCIDENT_ID is null and ANALYZING_EXPIRES_UTC is null".
If you are upgrading from Responder 10.2.1a OR LATER, this item does not affect your installation. As of Responder 10.2.1a, however, if you are upgrading from ArcFM Solution 10.1.1, 10.2, or 10.2.1, we recommend cancelling any active Jumpers and recreating them after the upgrade is complete. This prevents the possibility of an error occurring when you place a cut adjacent to a Jumper that is active. If the Jumper is active, Responder may not be able to properly determine the Jumper's endpoints after the upgrade due to database schema changes made to support Jumpers drawn with multiple click points.
