Jump to content

KSC Fails to Start After VM Cloning ("Keyset does not exist" Error)


Go to solution Solved by Demiad,

Recommended Posts

Hello everyone,

We're transitioning our datacenter from VMware ESXi to Proxmox and currently updating our VMs. Our challenge involves a VM running Windows Server 2016 with Kaspersky Security Center (KSC) 13.2.

After using VMware Converter to adjust the storage controller and disk size, the new VM boots up fine, but the Kaspersky Security Center doesn’t start. It’s set to automatically start, yet when I attempt to start it manually, it shuts down immediately.

Looking into the Event Viewer, I encounter this error every time I try to start the service:

"Service 'kladminserver' has been stopped due to an error. #1181 (-2146893802) System error 0x80090016 (keyset does not exist)"

It seems like there's an issue with the cryptographic keys that KSC needs to operate. Does anyone have insights on what might be causing this or how to resolve it?

Link to comment
Share on other sites

Posted (edited)
6 minutes ago, Vincentcassel said:

Hello everyone,

We're transitioning our datacenter from VMware ESXi to Proxmox and currently updating our VMs. Our challenge involves a VM running Windows Server 2016 with Kaspersky Security Center (KSC) 13.2.

After using VMware Converter to adjust the storage controller and disk size, the new VM boots up fine, but the Kaspersky Security Center doesn’t start. It’s set to automatically start, yet when I attempt to start it manually, it shuts down immediately.

Looking into the Event Viewer, I encounter this error every time I try to start the service:

"Service 'kladminserver' has been stopped due to an error. #1181 (-2146893802) System error 0x80090016 (keyset does not exist)"

It seems like there's an issue with the cryptographic keys that KSC needs to operate. Does anyone have insights on what might be causing this or how to resolve it?
g

Appreciate any help you can provide!

Edited by Vincentcassel
Link to comment
Share on other sites

  • Solution
Posted (edited)

@Vincentcassel hello

1. Your version KSC is out of date.
https://support.kaspersky.com/corporate/lifecycle

image.thumb.png.cb670d826393d0bf651d3ed269b688e7.png

2. Only the following virtualization platforms are supported:
https://support.kaspersky.com/ksc/14.2/255791

image.thumb.png.d52482453593caa8c74f4f28ad4303a4.png

3. Use this article to update and migrate your KSC:
https://support.kaspersky.com/13920

Edited by Demiad
answer correction
  • Like 1
Link to comment
Share on other sites

Posted (edited)
18 hours ago, Demiad said:

@Vincentcassel hello

1. Your version KSC is out of date.
https://support.kaspersky.com/corporate/lifecycle

image.thumb.png.cb670d826393d0bf651d3ed269b688e7.png

2. Only the following virtualization platforms are supported:
https://support.kaspersky.com/ksc/14.2/255791

image.thumb.png.d52482453593caa8c74f4f28ad4303a4.png

3. Use this article to update and migrate your KSC:
https://support.kaspersky.com/13920g

Thanks Demiad

Edited by Vincentcassel
  • Like 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now


×
×
  • Create New...