VMware Cloud Community
Deepl201110141
Enthusiast
Enthusiast
Jump to solution

Upgrade vShield Endpoint from version 5.1.0-01814505 to version 5.1.0-02563458 error message appears

Hi!

After updating vShield Manager when we attempt to install it the following message appears:

vShield Endpoint installation encountered error while uninstalling vib:Internal server error: Unable to read or write to database.

The process is stopped. This situation is observed on 2 hosts out of 7. Deinstallation causes a similar error.

What actions are appropriate in this situation?

Reply
0 Kudos
1 Solution

Accepted Solutions
Deepl201110141
Enthusiast
Enthusiast
Jump to solution

The problem was solved after restarting the host

View solution in original post

Reply
0 Kudos
4 Replies
Texiwill
Leadership
Leadership
Jump to solution

Hello,

I would open a support case with VMware on this one. How did you perform your upgrade?  vShield first then vCenter then ESXi? or some other way? or did you reinstall ESXi? If so, then that causes vShield to have some issues if you use the same name.

Edward L. Haletky

VMware Communities User Moderator, VMware vExpert 2009-2015

Author of the books 'VMWare ESX and ESXi in the Enterprise: Planning Deployment Virtualization Servers', Copyright 2011 Pearson Education. 'VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment', Copyright 2009 Pearson Education.

Virtualization and Cloud Security Analyst: The Virtualization Practice, LLC -- vSphere Upgrade Saga -- Virtualization Security Round Table Podcast

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos
Deepl201110141
Enthusiast
Enthusiast
Jump to solution

Hello, Edward!

First I performed upgrade of vShield Manager, then I began upgrading of vShield Endpoint on every host. Upgrade of some hosts was completed successfully, but for the remaining hosts an error message appeared. I upgraded neither esxi nor vCenter.

Best regards,

Dmitry

Reply
0 Kudos
Deepl201110141
Enthusiast
Enthusiast
Jump to solution

The problem was solved after restarting the host

Reply
0 Kudos
kbowdrums
Contributor
Contributor
Jump to solution

Running this command from SSH worked for me without having to reboot. It does not impact the running VMs either.

services.sh restart

Kevin

Reply
0 Kudos