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

Page Cannot be displayed

The Web server instance is not running.

Make sure that the Web server instance is running.

Refresh the connection between your browser and the Web site.

The Web server port is incorrectly specified in the eapps.cfg file.

Verify that the Web server port information in the eapps.cfg file is correct.

Virtual directories were not installed or configured properly.

Make sure that the Local Path for the virtual directories is correct and resembles the following:

SWSE_ROOT\PUBLIC\language

If you use a custom virtual directory, then make sure that you add the sweiis.dll parameter to your virtual directory to allow communication with the Siebel Server. For information, see Creating Custom Virtual Directories.

Anonymous users have incorrect responsibilities.

Make sure that anonymous users specified in the eapps.cfg file (AnonUserName and AnonPassword parameters) 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 (where load balancing is not deployed):

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 parameters are not available within the [defaults] section of the eapps.cfg file for Siebel Business Applications.

Make sure that the [defaults] section of the eapps.cfg file contains valid AnonUserName, AnonPassword, HTTPPort, and HTTPSPort values.

Also make sure that SessionTimeout and GuestSessionTimeout have appropriate values. For information about configuring these and other parameters, see Configuring the SWSE Logical Profile.

After stopping the IIS Administration service, an error message appears:

The service did not respond to the start or control request in a timely fashion

Stopping the IIS Administration service from Control Panel, Administrative Tools, then Services creates an error.

Open a DOS command window, and enter the following command to release all of the resources that are used by this service, such as inetinfo.exe and dllhost.exe:

IISRESET /START

If, after doing this, you still cannot start Siebel Business Applications, then you must restart the computer.

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 IUSR (IIS 7 or later) or IUSR_computername and IWAM_computername (IIS 6) user accounts do not have proper permissions to the SWSE_ROOT\public\lang directory.

Stop the Web server. Make sure that the permissions meet the requirements described in Requirements for Installing and Configuring the Siebel Web Server Extension. Restart the Web server.