1st cut at the vCenter 5 upgrade following KB2004265 fails with:
I am upgrading a Windows 2008 SQL 2008 vCenter which I cloned from the production one and renamed for this test.
I wonder if this is confusing the upgrader since it does not even let me specify the DSN/database
Anyone seen this/offer advice?
...and you are running the installer with the same windows credentials being used to authenticate into SQL. You have dbo on both the MSDB and VCDB? Your DSN is being seen, I sill think it's a permissions problem.
Seems like in your inventory you have nfs datastores mounted on differenet hosts with different hostnames (may be ip address and hostname). Before trying upgrade you need to fix this; make this consistent.
Reason for not supporting this is in below example -
1. Add an NFS datastore to server1 using the array's IP (no hostname available at the time).
2. Add an NFS datastore to server2 using the array's hostname.
The UUID for the same NFS datastore is now different on both machines causing vMotion to fail.
You can look at the KB for more information -