Installing the Web Interface › Web Interface Configuration Errors

Web Interface Configuration Errors

The following actions help you correct common configuration errors that you may experience with the Web Interface.

HTTP Status 404 Errors

HTTP Status 404 errors indicate that the web.xml file is incorrect. To fix the error, rename one of the other web*.xml files to web.xml.

HTTP Status 500 Errors

HTTP Status 500 errors indicate a problem in the harweb.cfg file.

The following are possible causes:

• One or more of the following is invalid: the user name, password, hostname, port number, database ID, or working directory.
• The JDBC driver or Webext is missing.
• For Oracle, check the Oracle Listener and start it if necessary.
• The Webext does not load; this problem occurs if more than one instance of the Web Interface is being used with the DFO option.

HTTP Status -1000 Errors

HTTP Status -1000 errors indicate one of the following problems:

• The command line is missing or not in the operating system variable path name variable. Check the variable and correct it if necessary.
• The command line parsing has been broken. To see if this problem exists, enter several commands with different options at the command line. Enter each command twice: once as you would typically enter the command and once with the -di option. For example, enter the following hchu commands:

  hchu input.txt
  hchu -di input.txt
  

  For both commands in this example, the input.txt is:

  -b broker -usr username -pw password -l
  

If you are using Tomcat, start the command line as the same user that starts Tomcat.

Java Errors

Java errors indicate a problem with Java. Possible causes are that only the Java Runtime Environment (JRE) is installed or that CA Harvest SCM does not support the Java SDK Standard edition installed. If either condition is true, the new Web Interface installation fails and custom forms do not compile.

Note: For the versions of Java SDK Standard edition that the product supports, see the Release Notes.

Web Interface requires a larger heap space when working with large numbers of versions. If you receive a “java.lang.OutOfMemoryError: Java heap space” error, the Java Maximum Heap Size needs to be increased for the Application Server/Servlet Engine. The option that your Application Server/Servlet Engine will need to pass to Java is –Xmx. For example, to set the Maximum Heap Size to 512 MB, change the –Xmx option to –Xmx512m. Refer to the Application Server/Servlet Engine documentation for instructions on completing this task.

Form Errors

Form errors indicate problems with generating custom forms. If you experience form errors, verify that a version of the Java SDK Standard edition that the product supports is installed and is defined in the operating system PATH variable.

Verify that you have set and tested all applicable system variables. For details, see Set and Test System Variables in Performing Pre‑installation Tasks.

Verify that the JSP files for any forms that you want to update are write-able. For example, if you want to regenerate an existing form like comment, verify that the Comments.jsp file is write-able, so that you can overwrite the existing file with a new file when you generate the new version of the form.

If you are using UNIX or Linux, verify that all *.sh files are executable.

Tomcat Errors

Tomcat does not start and displays the following error:

com.microsoft.sqlserver.jdbc.SQLServerException: Failed 
logon:com.microsoft.sqlserver.jdbc.SQLServerException: Login failed 
for user 'cascm'. The user is not associated with a trusted 
SQL Server connection

This error message occurs if the SQL Server authentication mode is set to Windows Authentication mode and the Web Interface connection is using SQL Server authentication. To fix this problem, set the authentication mode of your SQL Server to Mixed mode, which permits both Windows Authentication and SQL Server Authentication.