Troubleshooting Installation and Configuration for Siebel Application Interface

This task is part of Troubleshooting Installation and Configuration for Siebel CRM.

This topic provides suggestions for troubleshooting problems that you might encounter when installing and configuring Siebel Application Interface. Typical problems are shown in the following table.

Problem	Cause	Solution
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_AI_ROOT\applicationcontainer_external\webapps. Restart the application container, as described in Stopping and Starting the Siebel 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_external\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_external\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.