Have the CPU resources available to support the increased workload will cause Setting the ListenBackLog value high when you do not This value if Web requests are being rejected and you have the CPU resources Queue length lower if a system bottleneck begin to occur, and subsequently increase
IIs will reject any new connections until the queue length shortens. Whenever this queue length limit is reached, the This increases the maximum active connections that are held in the Iis queueįrom the default of 15 to 30. To increase the workload that Iis will accept, add the registry value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\InetInfo\Parameters\ListenBacklog=0x1E. If your processor usage looks relatively well distributed, and if onlyģ0 percent of processor resources are being used, consider increasing the workload Well across all processors in an NT environment, so watch each processor's usageĬlosely. Utilization counter for each CPU in your Web server. First determine if you have additionalĬPU capacity available by monitoring Perfmon's Processor object's Processor So let's ensure they are put to good use! Under heavy Web workloads, keeping Learn More Buy Strategy: Tune Your Web Application to Utilize AvailableĬPU resources are not that inexpensive that you want them to sit around idle,
#Inetinfo service windows#
Restart the Web server.Tuning and Sizing Windows 2000 for Maximum Performance Make sure that the permissions meet the requirements described in Requirements for Installing and Configuring the Siebel Web Server Extension. 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. Or, the Siebel Web Client login page does not display properly for example, images might be missing. The browser status bar might display errors such as:Īlso, the login page might stop responding. Inability to access the Siebel Web Client. If, after doing this, you still cannot start Siebel Business Applications, then you must restart the computer. 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: Stopping the IIS Administration service from Control Panel, Administrative Tools, then Services creates an error. The service did not respond to the start or control request in a timely fashion For information about configuring these and other parameters, see Configuring the SWSE Logical Profile.Īfter stopping the IIS Administration service, an error message appears: Make sure that the section of the eapps.cfg file contains valid AnonUserName, AnonPassword, HTTPPort, and HTTPSPort values.Īlso make sure that SessionTimeout and GuestSessionTimeout have appropriate values. Your Siebel application stops responding, displays a blank page or page not found, or times out.Īppropriate parameters are not available within the section of the eapps.cfg file for Siebel Business Applications. Make sure that the necessary Siebel Server components and component groups are enabled. Siebel Server components or component groups might not be enabled.
The value resembles the following example (where load balancing is not deployed):ĬonnectString = :// SiebelServerHost:2321/ EnterpriseServerName/ ProductNameObjMgr_ language Make sure that the connect string for the Siebel application is correct. The connect string for the Siebel application is incorrect. Otherwise, end users cannot access the home page. 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. For information, see Creating Custom Virtual Directories.Īnonymous users have incorrect responsibilities. 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. Make sure that the Local Path for the virtual directories is correct and resembles the following: Virtual directories were not installed or configured properly. Verify that the Web server port information in the eapps.cfg file is correct. The Web server port is incorrectly specified in the eapps.cfg file. Refresh the connection between your browser and the Web site. Make sure that the Web server instance is running. After installation, when the Siebel Web Client is started, a message appears, stating:
0 kommentar(er)
