vCenter 6 Upgrade Internal Error

During a recent vCenter upgrade I received the error message below after the installation process had started.


Encountered an internal error.  Traceback (most recent call last):   File “E:\Program Files\VMware\vCenter Server\firstboot\”, line 110, in main     controller.firstboot()   File “E:\Program Files\VMware\vCenter Server\firstboot\”, line 47, in firstboot     self.start()   File “E:\Program Files\VMware\vCenter Server\firstboot\”, line 63, in start     service.start()   File “E:\Program Files\VMware\vCenter Server\firstboot\identityinstall\”, line 203, in start     self.start_upgrade()   File “E:\Program Files\VMware\vCenter Server\firstboot\identityinstall\”, line 172, in start_upgrade     shutil.rmtree(self.data_path)   File “E:\Program Files\VMware\vCenter Server\python\lib\”, line 252, in rmtree     onerror(os.remove, fullname, sys.exc_info())   File “E:\Program Files\VMware\vCenter Server\python\lib\”, line 250, in rmtree     os.remove(fullname) WindowsError: [Error 32] The process cannot access the file because it is being used by another process: u’C:\\ProgramData\\VMware\\vCenterServer\\data\\vmdird\\data.mdb’ Resolution: This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.

The error and failed installer logs reference a database file for SSO which is locked.

The installer proceeds to ‘roll-back’ changes, however once complete the server is left without any vCenter components installed, vCenter Server 5.5 needs to be reinstalled and reattached to the existing database, other components such as Auto Deploy also need to be reinstalled and reconfigured (e.g. deploy rules).

Not the end of the world but quite a time consuming task just to get back to where you started. However, it turned out to be a simple fix; to resolve the error disable the McAfee McShield service for the duration of the upgrade. This releases the lock on the database file and the upgrade installer completes successfully.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: