Symantec Access Management

I installed CA Strong Auth 9.0 with SQL Server database which is running on port-1445. Then started CA Risk Auth 9.0 installation using installer which picked up earlier created data source name (DSN was created during strong auth installation with port=1445) with DB Server name but default SQL Server port 1443. Now since SQL Server here is not listening on SQL Server default port (1443), installation failed. DB Config screen during Risk auth 9.0 installation

* picking up default port 1443

* doesn't allow changing any value including port number and

* test data source is also disabled. hence no way to test connection during install. Its only after you have reviewed install log file that there was a connection issue.

Verified arcotcommon.ini as well as native datasource configuration and both places its set to port-1445. Strong auth service comes up just fine. Any ideas how to change SQL Server port during installation?

Opened a support case# 00958019 as well. 

Thanks

Abhishek

 Find and delete the registry file ".com.zerog.registry.xml" and then try to run the installer. This will force you to re-enter all the details during installation. 

Deleted C:\Program Files\Zero G Registry\ .com.zerog.registry.xml file and retried risk installation, still the same issue

Problem is easily reproducible, For testing I installed AA9 Strong Auth with Oracle DB on port-5050 and then kicked off risk installation which picked up default oracle port 1521 (screen shots below)

This is a defect. I am working with SE to get this fixed.

As a workaround I think you can temporarily rename arcotcommon.ini before starting RiskAuth install. This should give you option to specify db details.

Thanks Ujwol, renaming arcotcommon.ini did indeed allow data source modification during risk install.

There were few more steps needed for a successful service installation and start..following

1- Stop Strong Auth (Strong auth was installed successfully with datasource configured to use non-standard DB port)

2- Rename arcotcommon.ini  (This allows DSN entries modification during risk install)

3- Run Risk installation without primary DB initalization & service starts

4- Provide exact DSN values as provided during strong auth & test connection

5- Complete risk installation

6- Logon to DB and run following queries

     db-config-for-riskauth.sql";

     db-config-for-riskauth-table-index.sql"

7- Rename back to arcotcommon.ini

8- Start services