(AIX, HP-UX, and Oracle Solaris only)

In a migration installation of Siebel Gateway, the postinstallation profile creation step fails.

The cloudgateway.log file contains an exception error.

In some cases, an error might have occurred in updating the CGHostURI entry in the cloudgateway.properties file.

See also Troubleshooting Installation and Configuration for the Siebel Server.

The Siebel Application Interface might not have been available when it was required for the configuration process.

Try the following:

1. Clear the CGHostURI entry in the applicationinterface.properties file for Siebel Application Interface, in SIEBEL_AI_ROOT\applicationcontainer\webapps.
2. Restart the application container for Siebel Application Interface, as described in Stopping and Starting the Siebel Application Container.
3. Restart Siebel Gateway migration installation.

The Siebel Gateway does not start.

You might not have privileges as the Siebel service owner.

Review the instructions in Creating the Siebel Service Owner Account.

The Siebel Gateway does not start.

Failure to start the Siebel Gateway can be caused by a number of problems including, but not limited to:

• Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable
• Incorrect permissions set on shared libraries
• Missing shared libraries

Use the ldd command to show missing libraries.

Make sure that $SIEBEL_HOME/lib is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set $SIEBEL_HOME/lib as the first element of the shared library path environment variable.

Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell), and siebenv.csh or siebenv.sh.

Make sure that all files were correctly generated.

The Siebel Server cannot be installed.

Insufficient user privileges

For information about setting up appropriate administrative user privileges to install, see Setting Permissions and Ownership and Creating the Siebel Service Owner Account.

Trying to install or configure the Siebel Server out of sequence

For the required installation and configuration sequence, see Overview of Installing Siebel CRM.

Failure to install required hardware or software

Installation errors related to software requirements are logged in the Siebel Enterprise Server installer log file. For requirements, see the Certifications tab on My Oracle Support.

Environment variables not set properly

For more information about environment variables, see Managing Environment Variables.

Faulty network connection

Sometimes a faulty network connection can result in the system administrator being unable to install to the $SIEBEL_HOME directory in which he or she has write privileges. Verify that your network connection is stable.

The Siebel Server does not start.

Failure to start the Siebel Server can be caused by a number of problems including, but not limited to:

• Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable
• Incorrect permissions set on shared libraries
• Missing shared libraries

Use the ldd command to show missing libraries.

Make sure that $SIEBEL_HOME/lib is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set $SIEBEL_HOME/lib as the first element of the shared library path environment variable.

Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell), siebenv.csh or siebenv.sh, and dbenv.csh or dbenv.sh.

Make sure that all files were correctly generated.

Application Object Manager component does not start.

Heavily used servers running more than 50 instances of Object Manager components can experience a condition where some of the Object Managers do not start correctly and log the following error message:

Got error 1801210 when dequeuing a connection request (62)

Change TCP stack parameters.

For more information about sizing Application Object Manager components, see Siebel Deployment Planning Guide, Siebel Performance Tuning Guide, and other relevant documents on Oracle Technology Network or My Oracle Support.

The Siebel Server does not start after configuration.

Siebel Gateway not started

Verify that the Siebel Gateway was started. Start it if it was stopped.

Invalid input values for Siebel Server profile creation and deployment

Verify that the input values were valid.

Insufficient system privileges

Verify that you have sufficient system privileges to start the service. For more information, see Creating the Siebel Service Owner Account.

Cannot save a new profile in Siebel Management Console.

The specified profile name might already exist.

Provide a unique name for the new profile and retry saving the profile.

URL does not bring up Siebel Management Console.

Installations might not have been correctly performed.

Security certificates might not be valid, as configured.

You might have specified an incorrect port number in the URL.

Other causes might apply.

Verify the following:

• The installations were correctly performed,
• Valid security certificates were used, and the security authentication system is available
• The Siebel Application Interface application container is running
• The URL is correct and includes the correct HTTP or HTTPS port

See also Troubleshooting Installation and Configuration for Siebel Application Interface. For security issues, see also Siebel Security Guide.

URL does not bring up login page for a Siebel application.

Cannot log in to a Siebel application.

Configuration of Siebel Server or Siebel Application Interface might not have been correctly performed or completed.

Siebel database information might have been specified incorrectly.

The Application Object Manager might not have been enabled on the Siebel Server.

You might have specified an incorrect port number in the URL.

You might have added components on a new Siebel Server, but neglected to update the Siebel Application Interface profile.

Siebel system services might not be running.

You might be experiencing problems with the security authentication system you are using.

Other causes might apply.

Verify the following:

• The installations and configurations were correctly performed, and database information was specified correctly
• Security authentication was correctly configured and the security authentication system is available
• The Siebel Application Interface application container is running
• The Siebel Gateway and Siebel Server services are running
• The URL is correct and includes the correct HTTP or HTTPS port

See also Troubleshooting Installation and Configuration for Siebel Application Interface. For security issues, see also Siebel Security Guide.

Siebel Application Interface profile deployment fails despite no obviously incorrect profile values.

The application container might not have been available to support the configuration process.

Try the following:

1. Clear the CGHostURI entry in the applicationinterface.properties file, in SIEBEL_AI_ROOT\applicationcontainer\
webapps.
2. Restart the application container, as described in Stopping and Starting the Siebel Application Container.
3. Deploy Siebel Application Interface again.

The Siebel Application Interface does not start.

Failure to start the Siebel Application Interface can be caused by a number of problems including, but not limited to:

• Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable
• Incorrect permissions set on shared libraries
• Missing shared libraries

Use the ldd command to show missing libraries.

Make sure that $SIEBEL_HOME/lib is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set $SIEBEL_HOME/lib as the first element of the shared library path environment variable.

Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell).

After installation, when the Siebel Web Client is started, a message appears, stating:

Page Cannot be displayed

The application container is not running.

Make sure that the application container is running.

Refresh the connection between your browser and the Siebel Application Interface.

The Siebel Application Interface port is incorrectly specified.

Verify that the Siebel Application Interface port information is correct.

Applications were not configured properly.

Make sure that the Local Path for the configured applications is correct and resembles the following:

SIEBEL_AI_ROOT/applicationcontainer/webapps/siebel

Anonymous users have incorrect responsibilities.

Make sure that the specified anonymous users are also defined in the Siebel database with the correct responsibilities. Otherwise, end users cannot access the home page.

The connect string for the Siebel application is incorrect.

Make sure that the connect string for the Siebel application is correct. The value resembles the following example:

ConnectString = siebel.TCPIP.none.none://SiebelServerHost:2321/EnterpriseServerName/ProductNameObjMgr_language

Siebel Server components or component groups might not be enabled.

Make sure that the necessary Siebel Server components and component groups are enabled.

Your Siebel application stops responding, displays a blank page or page not found, or times out.

Appropriate settings are not available within the application configuration defined in the profile for the Siebel Application Interface.

Make sure that the configuration contains valid anonymous user and port number values.

Also make sure that appropriate values were specified for session time-out and guest session timeout. For information about configuring these and other settings, see Creating a Siebel Application Interface Profile.

Inability to access the Siebel Web Client. The browser status bar might display errors such as:

SWESubmitOnEnter is undefined

Also, the login page might stop responding.

Or, the Siebel Web Client login page does not display properly; for example, images might be missing.

The user account running the Siebel Application Interface does not have proper permissions to the SIEBEL_AI_ROOT/ applicationcontainer/webapps/siebel directory.

Stop the Siebel Application Interface. Make sure that the permissions meet the requirements described in Requirements for Installing and Configuring the Siebel Application Interface. Restart the Siebel Application Interface, as described in Stopping and Starting the Siebel Application Container.