A container is not pinging and is not accessible over Remote Desktop Protocol (RDP) or any other network services.
The following messages can be found in the container's event logs:
Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2012-12-10 22:33:21 Event ID: 2 Task Category: None Level: Information Keywords: User: SYSTEM Computer: CT17133 Description: License policy-cache corruption detected. Log Name: System Source: Service Control Manager Date: 2012-12-10 22:34:24 Event ID: 7022 Task Category: None Level: Error Keywords: Classic User: N/A Computer: CT17133 Description: The Group Policy Client service hung on starting.
After these events, more services also get hung in their starting state.
Stopping the container produces the following messages:
Stopping container ... WARNING: Native API function call 'ZwWaitForSingleObject' failed, code 0x102 Tim eout waiting for BaseNamedObjects\SC_AutoStartComplete event in session 887 WARNING: Failed to wait for SC_AutostartComplete in CT 887
Since the Group Policy Client was not started, all dependent services were also unable to start.
The exact root cause of this issue varies.
Incorrect content of the following registry key on the container may affect the License policy-cache:
HKEY_LOCAL_MACHINE\vzCTID\MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions ProductPolicy REG_BINARY
Compare the contents of the
ProductPolicyregistry key with the one from a healthy container. If there is a difference, replace this registry key with the values from another container.
If the registry values are correct, or the issue remains after modifying the ProductPolicy key:
Download the PSTools archive, unpack it, open the command prompt, and change your current directory to the PSTools folder.
Using psexec, run the registry editor under the system account:
C:\PSTools> psexec -s -i TERMSESSIONID regedit
NOTE: TERMSESSIONID is the ID of the current terminal session, which can be obtained in the following way:
C:\>qwinsta | findstr Active >rdp Administrator 4 Active
In the Registry Editor, navigate to
HKLM\vzCTID\MACHINE\SYSTEM\Currentcontrolset\Services\gpsvcand change the "Start" value from 2 to 4.
Start the container, then stop and mount it again:
C:\> vzctl start CTID && vzctl stop CTID && vzctl mount CTID
Revert the "Start" value of
HKLM\vzNEWID\MACHINE\SYSTEM\Currentcontrolset\Services\gpsvcfrom 4 to 2.
- Start the container.
The network should now be functional again in the container.
- If the procedure does not help, try to restore the whole
HKLM\SYSTEM\Currentcontrolsethive from a container backup.