CA RiskMinder Windows Installation Guide › Troubleshooting RiskMinder Errors › Installation Errors

Installation Errors

Problem:

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

Cause:

The installer failed to create the arcotadmin.war WAR file during installation.

Solution:

If the file was not automatically created, you must manually create it. To do so:

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

   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 RiskMinder Server (Arcot RiskFort Service). I see the following error in arcotriskfortstartup.log:

Failed DBPoolManager initialization

or

Datasource Name Not Found

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 arcotcommon.ini. 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. On Windows, you will find the 32-bit version at C:\Windows\SysWOW64.

Note: For detailed information on arcotcommon.ini and other configuration files, see Configuration Files and Options.

Problem:

I cannot start the RiskMinder Server (Arcot RiskFort 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 successfully created.

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.
   • If you found the entry, then clean up the database (See "Dropping RiskMinder Schema") and reseed the database, as described in Section, "Running Database Scripts".
2. Restart the RiskMinder Server.

Problem:

When I launch the Administration Console for the first time ("Logging In to Administration Console") 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

   Depending on the type of deployment, see one of the following sections for information about the location of these files:

   • For a single system deployment, see Step 2: Copying Database Access Files to Your Application Server.
   • For a distributed system deployment, see Step 2: Copying Database Access Files to Your Application Server.
2. Restart the application server.

Problem:

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

Cause:

Some of the probable causes for this issue might be:

• ARCOT_HOME might not be correctly set 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.

  Depending on the type of deployment, see one of the following sections for information about the location of these files:

  • For a single system deployment, see Step 2: Copying Database Access Files to Your Application Server.
  • For a distributed system deployment, see Step 2: Copying Database Access Files to Your Application Server.

Problem:

I deployed the UDS WAR (arcotuds.war), but the UDS 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:

To resolve this issue:

Ensure that you have copied the ArcotAccessKeyProvider.dll and arcot-crypto-util.jar files in the application server JAVA HOME location. Depending on the type of deployment, see one of the following sections for information about the location of these files:

• For a single system deployment, see Step 2: Copying Database Access Files to Your Application Server.
• For a distributed system deployment, see Step 2: Copying Database Access Files to Your Application Server.