Thanks for the follow-up, Michael.
*ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker>* **Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market…*** On Tue, Apr 16, 2013 at 8:58 AM, Michael Leone <[email protected]> wrote: > So I never did get an answer on this, either from here, VMware > Communities, or Tech Support. :-) But since the Host Agent Pre-Check > passed, and the new vCenter 5.1 Pre-Install Check Script passed, I > just went ahead and did it. > > So yesterday I upgraded my 5.0 to 5.1.0b. And it all Just Worked, > surprisingly enough. :-) Every section said completed successfully. It > does pay to do your homework - in my case, the SQL instance where I > created my RSA Single Sign On database was on a separate server. Being > a named instance (i.e., not default), the port number was 50977, not > the standard 1433). I found that port by asking my head DBA. :-) I > specified that when installing SSO, and it seemed to work. Also, when > installing Syslog Collector and Dump Collector, I had to specify the > username as "user@domain", not the "user" that the configuration > screen pre-filled in for me. > > (to be extra safe, I made a local hosts file on my vCenter, just > incase there were problems with my DNS. There wasn't - all my hosts > properly resolved forward and backward in DNS; I'm a bit of a stickler > for that - but it doesn't hurt just to be safe. Remember to do a > "ipconfig /flushdns", to reload the hosts file) > > Other than that, I didn't have any problems. Took about 80 minutes (I > went slowly, just in case). I also upgraded 2 vSphere clients on > workstations (mine and my boss), and again that just worked, along > with the Update Manager upgrade. > > So at this point, I just need to change my SQL Agent job that creates > a nightly backup of my VirtualCenter DB to also make a backup of my > RSA database. And then upgrade my hosts ... > > I will let it sit and percolate for another day, and start to upgrade > the hosts to 5.1, by using the Update Manager. > > On Thu, Apr 11, 2013 at 10:23 AM, Michael Leone <[email protected]> > wrote: > > I realize this is more than a bit OT for this list. But I'm still > > waiting to hear back from VMware Tech Support (they said they need to > > contact their engineers), and I've had no response from the VMware > > community yet. So I thought I would take a chance and ask here. > > > > I am about to upgrade from ESXi 5.0 U2 to 5.1. I am running the > > vCenter Server Database Pre-Upgrade Checker as a pre-step, and it is > > failing. Regardless of whether I run 32 or 64 bit checker, and > > regardless of whether I choose the ODBC or Credentials type of check.. > > > > vCenter OS=Win 2008 R2; DB = SQL 2008 R2 in a named instance, on a > > remote server. > > > > I am using ODBC as connection type, and am using the name I see in > > ODBC, and the correct SQL sa user and password. But it fails. Even if > > I use the "Credentials" option, it still fails. Both complain about > > failing to create a file. > > > > vCenter Server version = 5.0.0 Build 804277 > > > > > > The log shows: (snipped) - same error whether running an ODBC or > > Credentials check > > > > --------------------------- > > Signature file path: > > C:\Users\admin\Documents\64bit-check.xml-signature20130410141806.xml > > Message output file path: > > C:\Users\admin\Documents\64bit-check.xml-message20130410141806.txt > > Output archive file created. > > Error: no such file > > C:\Users\admin\Documents\64bit-check.xml-signature20130410141806.xml > > --------------------------- > > > > And the Debug log: > > C:\Users\admin\Documents\64bit-check.xml-signature20130410141806.xml > > (The system cannot find the file specified) > > > > The KB (< > http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004286 > >>) says that the checker compares a signature file of what I am > > running, against a "standard" signature file. From the looks of it, > > it's not creating my signature file, even tho the log says it did. > > > > Anybody ever run this? Does it even work? Looks to me like an error in > > the Java code that creates the signature, or the code that reads it > > back in, it's the only thing I can think of. > > > > Mind you, the 5.1 Host Agent Pre-Upgrade check runs flawlessly. But I > > am presuming that the Database PreCheck does a more comprehensive > > check (else why does it exist?). > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
