Unspecified error during off-star VM access

Today, the customer encountered an Unspecified error during online decompression. I thought it was a controlled permission, but it still failed to reset the controlled end, and the access control was still normal, but http: // controlled domain name/freehost. dll errors may occur. It seems that it is not an IIS issue or mutual access problem. It must be a problem with an out-of-the-stars component;

The error image is as follows:

Solution: Reload the license of the controlled terminal. If it is not the controlled terminal, the license can be K;

The following is a general error message and solution provided by the official team. If the problem cannot be solved, go on to the page;
It is strongly recommended that those who read this article read it all before performing any further operations,
The license cannot be reinstalled;

Error message: The requested header was not found or The operation timed out or The connection with the server was terminated abnormally or Unspecified error

Cause 1: The master server cannot connect to the controlled website, which may be caused by the firewall or
A very small number of data centers prohibit access between servers.

Analysis: You can use IE to open the controlled website on the master server to check whether the website can be accessed.
? If the access fails, the above error will occur. If you can open a controlled URL
You can try again:
Http: // controlled domain name/freehost. dll
If the access fails, the preceding error occurs.
If you cannot access the controlled website on the master, you can ping
Domain Name control to check whether the resolution is normal and whether the network is connected.
If ping is enabled, check whether the controlled website is stored on the controlled server.
At the beginning, you can automatically set the controlled website to be rebuilt.

Solution: you can close the firewall on the controlled server to solve the problem above.
If the network is restricted in the IDC, you can only contact the IDC.
　　　　　　　
　　　　
Cause 2: the IIS of the controlled server is stopped or the IIS is very busy and cannot respond to the request.

Solution: restart IIS.

　　　　
　　　　
Cause 3: The controlled domain name is resolved to the wrong IP address.

Analysis: This usually happens when you forget
The domain name is resolved to a new IP address.

Solution: You can resolve the controlled domain name to the correct IP address. Generally, several
Please be patient. The resolution will be successful in a few hours.

Cause 4: there is a problem with the routing of your dual-line data center.

Analysis: This usually happens on a dual-Data Center Server. One server has two
IP address, when accessing server B from server A, sometimes using IP1 on server
Access Server B (successful at this time), sometimes using IP2 on server
Access Server B (this will fail ).

Solution: this problem is caused by the data center. Only the data center can solve this problem. Generally, you can ask
If a static route is set for the IDC, use a correct IP address to access the IDC.
Ask another server.

Cause 5: the connection between servers is affected when the CC firewall is installed in the IDC. In this case
Is the feature automatically generated after the URL? Fwtdpfd = 10309 random
.

Solution: this problem is caused by the data center. Only the data center can solve the problem. Generally
Disable the CC settings for links between servers in the IDC.

Cause 6: the URLSCAN component is installed. Delete it.

Cause 7: When the VM data exceeds 10 Gb is deleted, it may occur:
"The operation timed out", this is normal, because The deletion time
Too long, resulting in timeout, which does not need to be processed.

Cause 8: MCAFEE is installed and special rules are set:
You can temporarily Delete the MCAFEE test.