5.5 vCenter to 6.0 VCSA - plugin crashes

[JulietDeltaGolf]

Using the 6.0 U2m migration tool to try and convert 5.5 Windows vCenter to VCSA 6.0. Pre-reqs all run OK, process gets most of the way through (creates new VCSA, configures IP etc etc) then CSD crashes on the server we're running the process from:

Faulting application name: vmware-csd.exe, version: 6.0.0.4185, time stamp: 0x5792f64f

Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9

Exception code: 0x40000015

Fault offset: 0x0005beae

Faulting process id: 0x624

Faulting application start time: 0x01d347fa53780691

Faulting application path: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe

Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll

Report Id: 74d68337-b3f7-11e7-989a-0050569200ba

The old vCenter gets shutdown but the new the VCSA ends up not quite finished:

The suggestion in this article made no difference: Troubleshooting the vSphere 6.0 Client Integration Plugin when it fails to function (2112086) | VMwa...

We've tried Firefox (old extended support version) and IE 11 with the same behaviour.

Any thoughts or suggestions most welcome.

Cheers.

[admin]

You simply just need to download and install the following new version of the CIP package for  Windows  and you will be able to restore the functionality that you once had which no longer relies on NPAPI. This fix applies to both a vSphere 6.0 and vSphere 6.0 Update 1 environment . If you are still having issues after installing the update, make sure you clear your browser cache as the old plugin may still be cached. Some folks had to perform a reboot, especially if you have more than one user on the system which could still have existing running processes.

http://vsphereclient.vmware.com/vsphereclient/2/9/9/4/0/4/1/VMware-ClientIntegrationPlugin-6.0.0.exe

[JulietDeltaGolf]

Hi,

Sorry but I'm not sure you've understood. We're using the 6.0 U2M .iso, that includes the 6.0.0 CIP package, this is what we have installed (it being a pre-req of the vCenter 5.5 to VCSA 6.0 migration process). The client crash occurs during this migration process and prevents the final migration and configuration of the new VCSA being completed.

In fact, having just checked, the CIP that comes with the U2M .iso (VMware-VCSA-all-6.0.0-4191361) is actually slightly newer, being 6.0.0.4185, against the one linked which is 6.0.0.3279.