Siebel Installation Guide for Microsoft Windows > Verifying and Troubleshooting Your Installation >
Troubleshooting Installation and Configuration for Siebel Business Applications
This topic presents troubleshooting information related to installation and configuration of Siebel Enterprise Server components and Siebel Application Interface. Some of the information also applies to additional components that use the same installer and are also configured using Siebel Management Console. This topic includes the following information:
Related Topics
Starting the Siebel Server Service
Verifying Installation for Siebel Business Applications
Stopping and Starting the Application Container
Troubleshooting Installation and Configuration for the Siebel Gateway
This topic describes potential errors that can result from a faulty installation or configuration of Siebel Gateway. Such problems can have any of several causes, some of the most common of which are listed in Table 14. NOTE: If you cannot start the Siebel Gateway, then you will not be able to configure a Siebel Enterprise or configure and start a Siebel Server.
Table 14. Troubleshooting Siebel Gateway Installation and Configuration
|
|
|
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. |
You cannot start the Siebel Gateway service on \\COMPUTER_NAME. Error XXX: The service did not start due to logon failure.
|
Login failure |
- Navigate to Control Panel, Administrative Tools, and then Services.
- Select the Siebel Gateway.
- Right-click, then choose Properties.
- In the Log On tab, specify the user name and password to use for this service.
|
You receive an error at system startup that a driver is missing. |
This problem can occur if you uninstall earlier Siebel Business Applications versions without first stopping the Siebel Server. |
Stop the Siebel Server before uninstalling Siebel Business Applications. If the services are no longer visible within the Services menu, then contact Oracle Global Customer Support for instructions. |
Troubleshooting Installation and Configuration for the Siebel Server
This topic describes potential errors that can result from a faulty installation or configuration of Siebel Server. Such problems can have any of several causes, some of the most common of which are listed in Table 15.
Table 15. Troubleshooting Siebel Server Installation and Configuration
|
|
|
The Siebel Server cannot be installed. |
Insufficient user privileges |
For information about setting up appropriate administrative user privileges to install, see 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 Business Applications. |
Failure to install the 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. |
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 that the installations were correctly performed, that valid security certificates were used, and so on. 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. 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 that the installations and configurations were correctly performed, that security authentication was correctly configured, services are running, and so on. See also Troubleshooting Installation and Configuration for Siebel Application Interface. For security issues, see also Siebel Security Guide. |
Troubleshooting Installation and Configuration for Siebel Application Interface
This topic provides suggestions for troubleshooting problems that you might encounter when installing and configuring the Siebel Application Interface. Typical problems are shown in Table 16.
Table 16. Troubleshooting Siebel Application Interface Installation and Configuration
|
|
|
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:
- Clear the CGHostURI entry in the applicationinterface.properties file, in
SIEBEL_ROOT \applicationcontainer\ webapps.
- Restart the application container, as described in Stopping and Starting the Application Container.
- Deploy Siebel Application Interface again.
|
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 /ProductName ObjMgr_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. |
|