000033417 - After upgrading RSA Archer 5.x, the Instance is missing in the Archer Control Panel (ACP)

Document created by RSA Customer Support Employee on Jul 4, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033417
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Version/Condition: 5.x
IssueAfter upgrade, the Archer Control Panel (ACP) can be opened, but the Instance is missing.
CauseThe wrong connection string in the ArcherTech.Services.ConfigurationService.exe.config file is pointing to the Instance database instead of the configuration database.
ResolutionChange the connection string in ArcherTech.Services.ConfigurationService.exe.config to point to the configuration database instead of the instance database and restart the Archer services.
  1. On each Archer Web and/or Archer Services server, open the ArcherTech.Services.ConfigurationService.exe.config file for edit.  (Typically installed in C:\Program Files\RSA Archer\Services)
  2. Find the <connectionStrings> node in the configuration file and ensure/change (according to your scenario). 
  3. Save the changes to the ArcherTech.Services.ConfigurationService.exe.config file.
For example, change:
add name="SqlDB" connectionString="Server=myoldserver;Database=myoldconfigurationdatabase;UID=myolduid;PWD=myoldpwd;" providerName="System.Data.SqlClient" />

To this:
<add name="SqlDB" connectionString="Server=myNewServer;Database=myNewConfigurationDatabase;UID=myewuid;PWD=mynewpwd;" providerName="System.Data.SqlClient" />

Windows Integrated connection string example:
<add name="SqlDB" connectionString="Server=myNewServer;Database=myNewConfigurationDatabase;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

Attachments

    Outcomes