Solution - Key Already Exists Error on Manage Incident Command

Version 1

    Behavior

     

    Users may receive the following error when they attempt to manage an incident.

     

    BadConfig.png

     

    2016-05-24 08:34:18,956 [Main Thread] ERROR Miner.Windows [(null)] - An unexpected program error has occurred.

    Refer to the error log for detailed information about the error.

    System.ArgumentException: Key already exists, key: CrewAssignment1

     

    Cause

     

    This can be caused by duplicate key entries in the ExplorerRulesConfig.xml configuration file. Multiple keys may exist that got duplicated in the files.

     

    Solution

     

    Depending upon additional customization in this file, it can be completely replaced, or you can manually remove the duplicates from the file. The file is located in the C:\Program Files (x86)\Miner and Miner\Responder\Server folder. The duplication will exist for CrewAssignment1, CrewAssignment2, and CrewAssignment3 sections that can be manually removed. A backup copy of the configuration is located in the C:\Program Files (x86)\Miner and Miner\Responder\Developer Resources\Implementation Scripts\Config folder, if you wish to just replace the file. Copy the file back into the Responder\Server folder or modify the existing file. All Responder services and clients will need to be restarted after making this change.