Article Number | 000033070 |
Applies To | RSA Product Set: Archer RSA Version/Condition: 5.x, 6.x Product Description: Archer Platform |
Issue | SQL Server is configured to be connected on a customized port other than the standard 1433, so it needs to make changes on Archer accordingly. |
Resolution | After making changes on the SQL Server, please follow the below steps to make change on Archer web server.
- Make a copy of the below file:
<Archer_Installation_Folder>\Services\ArcherTech.Services.ConfigurationService.exe.config Default Archer installation folder is C:\Program Files\RSA Archer - Edit the file and locate the ConnectionStrings part.
- Add comma and port number after the server name. In this example, 2500 is the customized port.
SQL Authentication example:
<add name="SqlDB" connectionString="Server=sql.archer.local,2500;Database=Archer_Config;UID=XXX;PWD=XXXX" providerName="System.Data.SqlClient" />
Windows Authentication (integrated security) example:
<add name="SqlDB" connectionString="Server=sql.archer.local,2500;Database=Archer_Config;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />
- Restart RSA Archer Configuration service.
- Open Archer Control Panel, go to Instance page and Database Tab.
- In the SQL Server field, add a comma and port number after the server, such as Sql.archer.local,2500.
|
Notes | For more information to change the listening port on SQL Server, please refer to Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager). For any questions regarding the Microsoft KB, please contact Microsoft Support. |