CA AuthMinder UNIX Installation Guide › Troubleshooting AuthMinder Errors › Installation Errors

Installation Errors

Problem:

I do not find arcotadmin.war in <install_location>/arcot/java/webapps directory.

Cause:

The file might 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/tools/common/bundlemanager 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/java/webapps directory.

Problem:

I cannot start the AuthMinder Server (Arcot WebFort 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 might be:

• 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 cause, you must 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), you must use the 32-bit version of the ODBC Manager.

Note: For detailed information on arcotcommon.ini and other configuration files, see the topic titled "Configuration Files and Options" in CA AuthMinder Installation and Configuration Guide.

Problem:

I cannot start the AuthMinder Server (Arcot WebFort 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 AuthMinder Schema") and reseed the database, as described in section, "Running Database Scripts".
3. Restart the AuthMinder Server.

Problem

When I launch the Administration Console 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:

• libArcotAccessKeyProvider.so
• arcot-crypto-util.jar

Solution:

Do the following:

1. Ensure that the LD_LIBRARY_PATH variable includes the absolute path to the following files:
   • libArcotAccessKeyProvider.so
   • 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/.

  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/.

• Ensure that you copy the libArcotAccessKeyProvider.so 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 libArcotAccessKeyProvider.so 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:

1. Verify whether the UDS information that you have provided in the "User Data Service Configuration" page of the Administration Console is correct. The details in Host, Port, and Application Context fields must be correct.
2. Check the UDS log file to ensure that the service was initialized successfully.