Bookshelf v7.5.3: Troubleshooting the Siebel Analytics Installation on UNIX

This section details 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 9.

Table 9. Common Problems and Solutions During Installation on 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.
The Siebel Analytics Server startup operation fails.	You are running a localized installation on AIX.	For AIX platforms localized for Japanese, see Changing Configuration Settings for Japanese Localizations on AIX.
Charts do not appear in Delivers and running iBots appear to hang.	Corda PopChart Image Server (PCIS) has not been configured properly.	Make sure that PCIS is running. Make sure that the port PCIS is listening on (the PORT environment variable in the file pcis.settings) matches the port Analytics Web thinks PCIS is listening on. Refer to the registry entry `HKEY_LOCAL_MACHINE\Software\Siebel Systems, Inc.\Siebel Analytics\Web\n.n\Charts\POP\ServerPrefix`. Make sure that other PCIS configuration steps have been completed properly; for example, the entry in the paths.xml file is correct. Make sure that the Web or application server's name is valid and accessible from the user's browser.
Attempting to access Analytics Web results in the java.lang.UnsatisfiedLinkError	Usually, this means that the environment for the Web server process does not include the directory for Analytics Web native libraries in its library path.	Make sure that the directory INSTALLDIR/Web/Bin is in the library path environment variable (LD_LIBRARY_PATH on Solaris, LIBPATH on AIX and SHLIB_PATH on HP-UX). If using Tomcat, make sure that the syntax for sourcing the Analytics Web initialization script (`$INSTALLDIR/setup/sa-webinit.sh`) is exactly as detailed in the installation instructions. If using Sun ONE, make sure that all Web server processes were shut down and that you started the Web server using the sa-web.sh script from the command line.
Attempting to access Analytics Web results in the javax.servlet.ServletException: Cannot create the server: Does the catalog you are using have read/write permissions for the user you are running as? (nqw:GOTNNXLK line 151 of WebServletWrapper.cpp)	If the Web server did not startup or shutdown properly on previous attempts it is possible that the Web Catalog's version record may have been corrupted. A failure to read this file would result in the observed error.	Locate the directory where your Web Catalog is saved. By default this is `$INSTALLDIR/Data/Web/Catalog`. Make a complete backup of all files in this directory to minimize loss of work. Assuming that your catalog is named SiebelAnalytics.webcat, locate the most recently modified file named SiebelAnalytics.webcat.xx.autosave, and replace the file SiebelAnalytics.webcat with this file. Delete the file named SiebelAnalytics.webcat.version. Try to start Analytics Web. If you still encounter the same error, then replace the SiebelAnalytics.webcat file with the next most current .autosave file.
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.	Stop 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 directory can be accessed from a browser. If this fails, the virtual directory 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.