Hello,
Cannot upgrade VCSA 6.0 to VCSA 6.5
always on stage 2 i get this error:
Error
Internal error occurs during Export of vSphere ESX Agent Manager.
Resolution
Send upgrade log files to VMware technical support team for further assistance.
i found article https://kb.vmware.com/kb/2147898, but this article applied only to vCenter Server 6.0 installed on Windows
I'm guessing this procedure isn't going to be supported by VMware?
I'm seeing some instability due to a database error after migrating from 6.0 U3 to 6.5 b, just a heads up in case any of these other upgraded vCenters are being flaky.
2017-04-09T09:25:09.933Z error vpxd[7F1FE9E58700] [Originator@6876 sub=Default opID=HB-host-97553@32887-67f22e81] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (23505) - ERROR: duplicate key value violates unique constraint "vpxi_psa_path";
--> Error while executing the query" is returned when executing SQL statement "INSERT INTO VPX_PSA_PATH (HOST_ID, PATH_ID, KEY_VAL, LUN_NUMBER, SCSI_LUN_ID, HBA_ID, TARGET_ID, LUN_LINK_KEY, ADAPTER_LINK_KEY, TARGET_LINK_KEY) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"
VCSA 6.5.0c was just released but does not fix the upgrade error
3d released 4/18 does work!
I love these response and VMware also does it, to Fix "What ever" remove unwanted plugins. How do I know which ones are unwanted?
What plugin did you remove to get the installer to complete?
Bouda0175 Mar 30, 2017 11:04 PM (in response to TomKalabis) Bouda0175
I followed Bouda0175 Steps and got past the Agent Manager Issue.
Alleged Update completed Successfully.
Following this discussion. I upgraded my test VCSA 6.0U3 last week to 6.5.0d and didn't experience any issues (luckily). I am now about to do ESXi and happened to look at the compatibility chart only to find to my horror that this upgrade path is not supported! I will probably do the test system anyway just for the hell of it, but i cannot do production or our Horizon environment until it is supported. I contacted VMware technical support who were not helpful at all. According to them there may be an update 1 due out in July or August but would not confirm if an upgrade to this from 6.0U3 would be supported
This product just seems to be getting worse its like they are not even doing proper QA anymore! How does something like this get released without testing things like that? So now we are all just stuck at 6.0U3 until VMware decide to release another patch for this? Its just as well cloud computing is really taking off now and I cant wait to move off this platform. No more dodgy upgrades
I hate to even leave these kind of posts and I apologise for not offering any useful information in this post but this is really annoying!
I,ve just upgraded from 6.0 U3a to 6.5.0U1c and had to follow the exact same steps.
(Jnewton03's original post) ---
I was able to get this working yesterday with 6.5a. I have not yet tried 6.5b.
Here is what I did:
To remove unwanted plug-ins from the available plug-in list:
I then stopped the VMWare-EAM service on the source appliance by doing the following:
1. SSH into the source appliance
2. Go into shell
3. issue a service-control --stop vmware-eam
I then re-ran the upgrade and was successful. Note that doing just one or the other of the above steps may have worked, but I have not tested it.
THANK YOU!!!
I have been battling this error for about a week. (VC6 to 6.7 to get to VC 7) The installer logs were worthless, and I can't read the tar logs to send to VMware. No useful data, and much Googling led my down false paths. I saw this post and thought nothing to lose, doubt it will work since the error has nothing to do with extensions. I had the error stating "Cannot validate target appliance configuration as not enough information from the source appliance can be collected. For more details check out the server logs." Joke is on me, there were no useful details in the logs! And nothing about this error tells me an extension is in the way. Anyway rant over. Apparently they were an old 5.x environment under another MSP, and the extension happened to be exactly the same one you posted. This post was immensely helpful, thank you again!