CA Strong Authentication Windows Installation Guide › Troubleshooting CA Strong Authentication Issues › Installation Errors

Installation Errors

Problem:

When I download the CA Auth ID in IE browser on the server with CA Strong Authentication installed, it gives the following error:

Your security settings have blocked an application signed with an expired or not-yet-valid certificate from running.

Solution:

Change Java Settings by navigating to Control Panel and click on Java. Select the Security option as Medium (Instead of High). Default option is High which gives the exception. Then download CA Auth IDusing "Arcot Applet Client" & "Arcot Flash Client" on IE or Firefox or Chrome.

Problem:

When I download the CA Auth ID in Chrome browser on the server with CA Strong Authentication installed, it gives the following error:

Permanent storage in the Flash player is disabled.

Solution:

Enable HTTPS instead of HTTP to download using "Arcot Flash Client". Then download the CA Auth ID on IE or Firefox or Chrome.

Problem:

I do not find arcotadmin.war in <install_location>\Arcot Systems\java\webapps directory.

Cause:

The file may not have been created during installation.

Solution:

Perform the following steps to create the arcotadmin.war file:

1. Open command window.
2. Ensure ARCOT_HOME environment variable is set.
3. Navigate to <install_location>\Arcot Systems\tools\common\bundlemanger directory.
4. Run bundlemanager with the following command:

   java -jar bundle-manager.jar
   

   The preceding command generates the arcotadmin.war file in <install_location>\Arcot Systems\java\webapps directory.

Problem:

I cannot start the CA Strong Authentication Server (CA Strong Authentication Service). I see the following error in arcotwebfortstartup.log:

Failed to initialize DB Pool Manager

or

Data source name not found and no default driver specified

Cause:

The possible causes for this issue are:

• The DSN for your database was not created as System DSN.
• You are using a 64-bit platform. As a result, the DSN was created by using the 64-bit ODBC Manager.

Solution:

You can verify the DSN-related issues in the arcotcommon.ini file. If the problem is DSN-related, then:

1. To resolve the first issue, ensure that the DSN is a System DSN. To do so:
   1. Open the Control Panel, navigate to Administrative Tools, and Data Sources (ODBC).
   2. Activate the System DSN tab, and verify that your DSN exists here. If not, then you must re-create the DSN with the same name as earlier.
   3. Restart the service.
2. To resolve the second issue (if you are using a 64-bit platform), use the 32-bit version of the ODBC Manager. On Windows, you will find the 32-bit version at C:\Windows\SysWOW64.

   Note: For detailed information about arcotcommon.ini and other configuration files, see appendix, "Configuration Files and Options" in the CA Strong Authentication Installation and Configuration Guide.

Problem:

I cannot start the CA Strong Authentication Server (CA Strong Authentication Service). The error message indicates that the service starts and stops automatically.

Cause:

A possible cause for this issue might be that you specified details for a Database during installation, but the data source was not created successfully.

Solution:

To resolve this issue:

1. Verify if there is a corresponding entry for the DSN in arcotcommon.ini.
   • If entry not found, manually create the DSN.
2. If you found the entry, then clean up the database (see "Uninstalling CA Strong Authentication Schema") and reseed the database, as described in section, "Running Database Scripts".
3. Restart the CA Strong Authentication Server.

Problem:

When I launch CA Advanced Authentication for the first time (section, "Performing the Bootstrapping Tasks") as the Master Administrator, I see the following message:

The server encountered an internal error that prevented it from fulfilling this request."

I see the following error in the arcotadmin.log file:

adminLog: java.lang.UnsatisfiedLinkError: no ArcotAccessKeyProvider in java.library.path

Cause:

The JAVA library does not include the path to one of the following files:

• ArcotAccessKeyProvider.dll
• arcot-crypto-util.jar

Solution:

Do the following:

1. Ensure that the PATH variable includes the absolute path to the following files:
   • ArcotAccessKeyProvider.dll
   • arcot-crypto-util.jar
2. Restart the application server.

Problem:

I do not see the log file (arcotadmin.log, arcotuds.log, or webfortserver.log) in the logs directory in ARCOT_HOME.

Cause:

Some of the probable causes for this issue might be:

• ARCOT_HOME might not be set correctly during installation.
• The application server JAVA HOME might be pointing to JRE instead of the JDK HOME.

Solution:

To resolve these issues, you must:

• Ensure that you reset the ARCOT_HOME to point to the correct location. Typically, this is <installation_location>\Arcot Systems\.

  As a result of this, when you use the cd %ARCOT_HOME% command in the command prompt window, your current directory must change to <installation_location>\Arcot Systems\.

• Ensure that you copy the ArcotAccessKeyProvider.dll and arcot-crypto-util.jar files in the application server JAVA HOME location.

Problem:

I deployed the UDS, but it is not coming up.

Cause:

One of the possible causes might be that the application server JAVA HOME might be pointing to JRE instead of the JDK HOME.

Solution:

Ensure that you have copied the ArcotAccessKeyProvider.dll and arcot-crypto-util.jar files in the application server JAVA HOME location.

Problem:

Connection to the UDS fails. I see the following error message:

Unable to contact User Data Service

Cause:

The possible causes might be:

• You might not have specified the UDS Host, Port, and Application Context information for UDS correctly.
• The UDS service might not be initialized.

Solution:

To resolve this issue:

Verify whether the UDS information that you have provided in the "User Data Service Configuration" page of CA Advanced Authentication is correct. The details in Host, Port, and Application Context fields must be correct.

1. Check the UDS log file to ensure that the service was initialized successfully.