No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Windows-based VM Suspended in the Applying user settings Page for a Long Time

Publication Date:  2014-10-24 Views:  859 Downloads:  0
Issue Description
[Application Scope]: FusionAdapter version is V1.2.00.100 or earlier versions \ FusionAdaptor version is V1.1.00.601 or earlier versions
Symptom 1:
After a user starts a Windows-based virtual machine (VM) and logs in to the system, the user finds that the network service is disabled. For the Windows 7 operating system (OS), the network connection icon at the right bottom corner is in waiting state and the network configuration page cannot be opened. In addition, some services also encounter exceptions (such as in disabled state).
Symptom 2:
After a user starts a Windows-based VM, the user attempts to log in to the system using the user name and password through the virtual network computer (VNC). However, the system is suspended in the Applying user settings page and the login fails, as shown in Figure 1. The desktop login succeeds about two hours later.
Figure 1 Desktop login failure
Alarm Information
Handling Process
Users can manually modify the ServicesPipeTimeout registry to solve this problem. The detailed procedure is as follows:
1. After the Windows OS starts, log in to the VM.
2. Click Start, type regedit in Search or Run, and press Enter.
3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout registry in the registry editor. Double-click the registry, select Decimal, set Value data to a proper value (Using the default value 30 seconds for example, set the value to 30000), and click OK, as shown in Figure 3.
Figure 3 Setting the value of ServicesPipeTimeout
Root Cause
The common symptom is that the system is not abnormal persistently and restores in 5 minutes or two hours. Based on the Windows log, the system is suspended for a period until an application reports a timeout error. Then, a batch of services is enabled.
These symptoms are caused by incorrect configuration of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout key value table. This key value table specifies the timeout interval for starting Windows services. If the value is set to 300000 or 7200000, the time for starting services is 300 seconds (that is 5 minutes) and 7200 seconds (that is two hours). When a service is abnormal, the service start fails and the system is in waiting state until a timeout error is reported after the interval specified by the preceding table. Accordingly, services started after the abnormal service are also forced to wait for such a period. The Windows network service is started late. Therefore, the network service may be not started after the system starts for a long time.
This problem may cause start delay of a random service that is started after the abnormal service. Therefore, other symptoms may be involved.