Siebel Analytics Installation and Configuration Guide > Configuring Siebel Analytics in the UNIX Environment >

Troubleshooting the Siebel Analytics Installation (UNIX)


This topic describes some common problems observed during installations and suggests possible solutions. To resolve the problem, look for it in the Symptom/Error Message column in Table 39.

For some components, such as PopChart Image Server, that are installed under Windows platforms only, see also Troubleshooting the Siebel Analytics Installation (Windows).

Table 39.  Common Problems and Solutions During Installation Under UNIX
Symptom/Error Message
Diagnostic Steps/Cause
Solution

The Siebel Analytics Server startup operation fails.

Look in the log files for messages indicating possible reasons. Log files are located in the $INSTALLDIR/Log/subdirectory.

You can use a text editor to view a log file. (Set your viewer to UTF-8 to avoid seeing garbled text.)

Make sure that the syslog service is running, and look for any system or Siebel Analytics-related messages.

The log files contain messages indicating why the server startup failed.

For example, if there were a syntax error in the NQSConfig.INI file, both the operating system's log and the NQServer.log file would contain messages about the syntax error. After examining the log messages, correct the problem and start the server again.

 

You are running a localized installation on AIX.

For AIX platforms localized for Japanese, see Changing Configuration File Settings for Japanese Localizations on AIX.

Charts do not appear.

Analytics Web is unable to communicate with Corda PopChart Image Server (PCIS).

NOTE:  This note applies if you are upgrading from Siebel Analytics 7.5 versions.
The location, structure, and content of the Corda image server directory have changed from Siebel Analytics version 7.5. The image server is now installed under the main installation directory. Also, the file key.txt is no longer required.

  1. Make sure that PCIS is running.
  2. Make sure that the port value of PCS_Port in $INSTALLDIR/Corda51/config/server_config.txt is the same as the port number specified in the $INSTALLDIR/Data/web/config/instanceconfig.xml setting: WebConfig/ServerInstance/Charts/POP/ServerPrefix.
  3. Make sure that the Web or application server's name is valid and accessible from the user's browser.

Note that it is possible for Analytics Web and PCIS to run on separate machines, but for administrative as well as performance reasons, it is recommended that they be installed on the same machine.

Charts do not appear in Delivers and running iBots appear to hang.

PCIS has not been configured properly.

Make sure that you can see charts outside of Delivers; for example, in Answers or on other dashboards. If charts are otherwise visible, contact Siebel Technical Support.

Unable to log on to Siebel Analytics Web. Message:

Siebel Analytics ODBC returned the error:
(No error info available)

The Analytics Server process nqservice.exe is not running or is terminated abruptly.

Kill the process nqscomgateway.exe manually and restart the Analytics server by running the command ./run-sa.csh start from the following location: $INSTALLDIR/setup.

Hourglass icon remains in processing state when trying to log on to Siebel Analytics Web.

This database that the user.csh file points to is incorrect, or is a corrupted database. This may also happen due to the abrupt disconnection of the database in the middle of processing.

Open the file user.csh (located at $INSTALLDIR/setup. Check for the database parameters. Using the command sqlplus, check whether or not the connection is being established.

When starting the Scheduler, you receive an error.

Set the DISPLAY variable for Scheduler.

  • For Korn, Bourne, or bash shells:

    export DISPLAY=ip_address:0

  • For C shell:

    setenv DISPLAY=ip_address:0

No Login Screen - No Errors

Incorrect configuration or incomplete shutdown/memory allocation.

  • Make sure that Web server is running.
  • Make sure that the empty.htm file in the installed virtual server can be accessed from a browser. If this fails, the virtual server path is incorrectly defined.
  • Shutting down the server and Web server usually requires that the script mwcleanup be executed prior to restarting.

No login Screen - Web server errors

Conflicting ports used

Make sure that the Analytics Web does not use the same port numbers as existing software (for example, accidentally picking the same port number as an existing Web server).

No Login Screen - Analytics Server restarted

Analytics Web lost connection to the Analytics Server

Ideally, Analytics Web should be shut down prior to the server and restarted after the Siebel Analytics Server has been restarted.

nQSError: 77006 (Not Found: The requested object does not exist on this server...)

Siebel Analytics Web Server parameter is not set correctly in schconfig.exe— Configure iBots.

Make sure that the Siebel Analytics virtual Web server is correctly configured. Reconfigure the Siebel Analytics Web Server parameter as http://<host:port>/CUSTOM/saw.dll, where CUSTOM is the custom path specified in web-apps.xml.

See Configuring a Custom Name for a Virtual Web Server.

The URL http://<server:port>/analytics results in a server error, and Web server logs contain errors about JSP compilation.

The Web server is unable to access a scratch directory to handle the JSP.

Set up a Web server scratch directory.

See Testing the Tomcat Web Server Installation (UNIX).

Siebel Analytics Installation and Configuration Guide