Article ID: 11132, created on Mar 16, 2011, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows
  • Connection Broker

Symptoms

The Parallels Virtuozzo Containers Management Service or Virtuozzo KSAL service does not start:

C:\Users\Administrator>vzlist -a
Service 'Parallels Virtuozzo Containers Management Service' is not started
There is no Parallels container installed.

C:\Users\Administrator>net start "Parallels Virtuozzo Containers Management Service"
System error 1068 has occurred.

The dependency service or group failed to start.

You may also see these messages in the Event Viewer:

Log Name:      System
Source:        Service Control Manager
Event ID:      7001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
The vzsched service depends on the vzktech service which failed to start because of the following error:
A device attached to the system is not functioning.

Cause

This problem is commonly caused by incompatible Microsoft update(s) installed on the Node.

Resolution

As of Virtuozzo Containers 4.5, a vzksal utility is available, which checks for incompatible Microsoft updates.

Here is an example output of this command:

On a working server:

C:\Documents and Settings\Administrator>vzksal check
Parallels Containers (R) Ksal Server 2.2 Copyright (C) Parallels Inc., 1995-2009

VERDICT: Specified database is compatible with current OS.

On a broken server:

C:\Users\Administrator>vzksal check
Parallels Containers (R) Ksal Server 2.2 Copyright (C) Parallels Inc., 1995-2009


File: C:\Windows\system32\DRIVERS\ntfs.sys
PDB: 3C882431A6B845D98E746E59187817B72
Image: ntfs.sys
Version: 6.1.7601.17514
Locales: Language 1033, codepage 1200: 6.1.7600.16385 (win7_rtm.090713-1255)
Verdict: PDB signature not found in database

File: C:\Windows\system32\ntoskrnl.exe
PDB: 3844DBB920174967BE7AA4A2C20430FA2
Image: ntkrnlmp.exe
Version: 6.1.7601.17514
Locales: Language 1033, codepage 1200: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Verdict: PDB signature not found in database

File: C:\Windows\system32\win32k.sys
PDB: 21E2778DD2954987A9B7212463FFDC5E2
Image: win32k.sys
Version: 6.1.7601.17514
Locales: Language 1033, codepage 1200: 6.1.7600.16385 (win7_rtm.090713-1255)
Verdict: PDB signature not found in database

File: C:\Windows\system32\winlogon.exe
PDB: 33967333A9DE45D68A9CB7EFF86F1B6E2
Image: winlogon
Version: 6.1.7601.17514
Locales: Language 1033, codepage 1200: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Verdict: PDB signature not found in database

VERDICT: Some OS modules are missing from the database.

If one or more PDB signatures are missing from the database, you should uninstall the corresponding Microsoft Updates and reboot the physical server.

To find out which Microsoft Updates correspond to the missing PDB signatures, run the vzksal utility against the respective system file. For example:

C:\Documents and Settings\Administrator>vzksal origin -file c:\windows\system32\win32k.sys
Parallels Containers (R) Ksal Server 2.2 Copyright (C) Parallels Inc., 1995-2009

File: c:\windows\system32\win32k.sys
PDB: D896ADA4D4C94A7FB9EE6D6B0663204B2
Image: win32k.sys
Version: 5.2.3790.4769
Locales: Language 1033, codepage 1200: 5.2.3790.4769 (srv03_sp2_gdr.100831-0407)

Origin: KB981957
Display: Security Update for Windows Server 2003 (KB981957)
Update: 1

In the example above, it is KB 981957 that must be uninstalled.

There are cases when PDB signatures are missing from the database and Microsoft Updates are not shown by the command above:

C:\Windows\system32>vzksal check
Parallels Containers (R) Ksal Server 2.2 Copyright (C) Parallels Inc., 1995-2009

File: C:\Windows\system32\win32k.sys
PDB: BC9E46EC04C04CDB9C991B9DCE40B7732
Image: win32k.sys
Version: 6.1.7601.18512
Locales: Language 1033, codepage 1200: 6.1.7600.16385 (win7_rtm.090713-1255)
Verdict: PDB signature not found in database

VERDICT: Some OS modules are missing from the database.

C:\Windows\system32>vzksal origin -file C:\Windows\system32\win32k.sys
Parallels Containers (R) Ksal Server 2.2 Copyright (C) Parallels Inc., 1995-2009

File: C:\Windows\system32\win32k.sys
PDB: BC9E46EC04C04CDB9C991B9DCE40B7732
Image: win32k.sys
Version: 6.1.7601.18512
Locales: Language 1033, codepage 1200: 6.1.7600.16385 (win7_rtm.090713-1255)

C:\Windows\system32>

Check that all installed Microsoft updates are supported by installed VZUpdates. For example, there may be a KB2978668 installed, which is supported by VZU460073. However, the node only has 68 VZUpdates. In cases like this, install all missing VZUpdates and reboot the node.

For more details on which Microsoft updates are compatible with Virtuozzo Containers, see this page:

Supported Microsoft Updates

We do not recommend that you manually install any Microsoft updates other than those listed on this page (which are installed automatically). Otherwise, Virtuozzo containers may stop functioning correctly. If you need an update that is not listed as being supported, please create a support ticket with Odin asking if it is safe to install the update. If it happens to be unsafe, you will be able to file a request to support it.

For other versions

Refer to Knowledgebase article #3588 for instructions on how to check KSAL for Virtuozzo containers 4.0.

Additional information

Use the attached script to check if installed updates are present in the list of Supported Microsoft Updates.

113634 Microsoft Updates and Virtuozzo Containers for Windows

11154 Containers do not start after installation of Service Pack 1 for Windows Server 2008 R2 on the node

Search Words

VZcore not starting

installation

there is no parallels container installed

起動しない

vzksal

Parallels Virtuozzo Containers Management Service' is not started

VZsrv not starting

update

ms updates

incompatible updates

taskbar missing virtuozzo

Attachments

d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 2897d76d56d2010f4e3a28f864d69223 be1e704b496bd05825ed07b8a06c74ab

Email subscription for changes to this article
Save as PDF