VMware Cloud Community
hgov
Enthusiast
Enthusiast
Jump to solution

Errors after vCenter update to 7.0.3 build 19234570

Upgraded to version 7.0.3.00300 yesterday and now have messages indicating "Loading chunk x failed...." when looking at the datacenter or cluster Updates\Hosts or Updates\Images within vCenter. Most everything else seems fine. This did not occur prior to the upgrade from 7.0.1 Build 17005016 to 7.0.3 Build 19234570. Is this "normal" behavior after an upgrade? Any suggestions on how to repair the vCenter server and eliminate the errors? Both seem to refer to separate .js files.

Thanks in Advance,

Reply
0 Kudos
1 Solution

Accepted Solutions
virtsysadmin
Enthusiast
Enthusiast
Jump to solution

HTML5 cache creating some issues with the browsers, especially after patching .

Try to login to vSphere Client from Browser incognito mode or  clear the cache and cookies from the browser and retry to access vLCM.



I am a VMware employee, But I contribute to VMTN voluntarily (ie. not in any official capacity)
VCIX-DCV 2020|CKA|VCP|VCP vSphere 7|MCTS|RHCA|CCNA|ITIL| Master Specialist - VMware Cloud on AWS 2021
Please hit resolved, when your question has been answered.

View solution in original post

3 Replies
virtsysadmin
Enthusiast
Enthusiast
Jump to solution

HTML5 cache creating some issues with the browsers, especially after patching .

Try to login to vSphere Client from Browser incognito mode or  clear the cache and cookies from the browser and retry to access vLCM.



I am a VMware employee, But I contribute to VMTN voluntarily (ie. not in any official capacity)
VCIX-DCV 2020|CKA|VCP|VCP vSphere 7|MCTS|RHCA|CCNA|ITIL| Master Specialist - VMware Cloud on AWS 2021
Please hit resolved, when your question has been answered.
Tibmeister
Expert
Expert
Jump to solution

This is absolutely not normal behavior.  You should open an SR on this as it sounds like something in the database is wonky.

Reply
0 Kudos
hgov
Enthusiast
Enthusiast
Jump to solution

Thanks. Clearing the cache, history and cookies appears to have fixed the issue. No more errors.

Reply
0 Kudos