Web service unavailable

Web service unavailable

1. Remotely connect to the Windows instance.

2. Check the web service log.

Method 1: Browse the log folder.

The log path of the operating system of Windows Server 2008 R2 and above is: C:LogFiles.

Method 2: Check the IIS Manager.

*Select the Start icon > Windows Administrative Tools > Internet Information Services ((IIS) Manager.

*In the IIS area of the web service home page to be viewed, click Log, and then click Browse in the Operation column. View web log (Windows) new image

*On the log page, modify the log storage path according to your actual situation, copy and paste the corresponding address to the file explorer, and press Enter.

You can view the corresponding log folder in File Explorer. view log path new

3. Check the running status of the instance through the task manager to see if there is any abnormal process.

a. Right-click on the desktop and select Task Manager.

b. Click the Process tab.

You can view the CPU and memory information of the process in the task manager, and locate the abnormal process. View abnormal processes in task manager new

4. Check the instance monitoring information on the console.

Check whether the instance CPU and memory are sufficient. If not, refer to Troubleshooting Windows Instance Bandwidth and CPU Running Full or High.

Check whether the instance bandwidth is sufficient. If not, try to upgrade the instance bandwidth. For details, see Modifying Bandwidth Configuration.

5. Check whether there are too many TCP connections on port 80 of the instance.

a. Open the CMD command prompt.

*Click the Start icon icon in the lower left corner of the desktop, then click the Search icon icon.

*Input cmd in the search box. Click Command Prompt

* Click Command Prompt.

Enter the command prompt. go to command prompt

6. Execute the following commands in sequence to collect statistics on the number of TCP connections.

netstat -n |find /i "time_wait" /c
netstat -n |find /i "close_wait" /c
netstat -n |find /i "established" /c

The default number of dynamic ports is 16384 (starting from 49152 and ending at 65535). If the number of close_wait is close to the number of dynamic ports, it means that there are a large number of close_wait connections that have not been released. You need to perform the next step to modify the registry to reduce the Time Wait time. Counting the number of TCP connections

7. Open Registry Editor.

a. Click the Start icon icon in the lower left corner of the desktop, and then click the Search icon icon.

b. Type regedit in the search box. Open the Registry Editor

c. Click regedit.

Enter Registry Editor. 2012 Registry Editor

8. In the Registry Editor's

Set the value data of the registry key TcpTimedWaitDelay to the decimal value 30.

If the TcpTimedWaitDelay entry does not exist, please create a corresponding registry entry, and then modify the value data. Taking TcpTimedWaitDelay as an example, the operation is as follows:

a. In Registry Editor

Right-click the blank area of the registry key, and then select New (N) > DWORD (32-bit) Value. Create new registry key

b. Type TcpTimedWaitDelay and press Enter.

c. Right-click the registry key TcpTimedWaitDelay, and then click Modify. Click Modify Registry Key

d. In the dialog box, check Decimal, and set the Value data to 30.