<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Trying to upgrade to newest vCenter Server... in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840490#M25618</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try create a brand new DB with sufficient privileges and all the right plugins etc and then restore your backup over it. I did the exact same for esx4-4.1 vCentre upgrade and worked a charm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gregg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Oct 2011 16:12:07 GMT</pubDate>
    <dc:creator>firestartah</dc:creator>
    <dc:date>2011-10-07T16:12:07Z</dc:date>
    <item>
      <title>Trying to upgrade to newest vCenter Server...</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840488#M25616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've used the data migration tool to backup my vcenter server, and am trying to now restore onto a new server in order to facilitate the conversion from 32-bit to 64-bit, go to ESXi on VSphere 5, etc.&amp;nbsp; Current database is sitting on a SQL 2008 Enterprise server and works great.&amp;nbsp; I backed it up too.&amp;nbsp; &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I go through the process of running the restore on the new server, and get to the part where it tries to connect to the database whereby I get the ever-popular error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1841889.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/40440i6045C3E7064CA718/image-size/large?v=v2&amp;amp;px=999" role="button" title="1841889.png" alt="1841889.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is, I've tried with 3 different usernames, including a new one just to make certain I haven't missed anything.&amp;nbsp; In all cases, the users are domain users and in the database have DBO, sysadmin, etc. to both the Virtual Center database and the MSDB database.&amp;nbsp; In fact, one user has wide-open permissions to every damned database (this is a named instance server with a lot of databases, so he was just a test).&amp;nbsp; I still get this error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DSN is 64-bit, using the SQL native drivers and tests just fine.&amp;nbsp; Every other database from BES to SharePoint is working great, and even our DBA can't find any problems.&amp;nbsp; I'm completely stuck here and am looking for options. If need be, I'll even create a new database and migrate this one over if that's easy enough... I just want to get through this @#$@! so I can move on with my life.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Considering the lack of errors on the SQL side, we're wondering if there might be some sort of problem with named instances on the new vcenter?&amp;nbsp; Or a bug?&amp;nbsp; We've been running the same configuration for years now and have upgraded with no problems in each case.&amp;nbsp; This is the first time we're seeing this error and are more than a little bewildered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Oct 2011 23:19:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840488#M25616</guid>
      <dc:creator>SomeClown</dc:creator>
      <dc:date>2011-10-06T23:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to upgrade to newest vCenter Server...</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840489#M25617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sounds like something went amiss with the migration from the 32bit to the 64bit DB.&amp;nbsp; Does the DSN check out and complete a successful connection?&amp;nbsp; I'd lean heavily on opening up a support ticket on this one since it sounds like what you are doing is fully supported.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Oct 2011 15:40:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840489#M25617</guid>
      <dc:creator>morrisosu</dc:creator>
      <dc:date>2011-10-07T15:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to upgrade to newest vCenter Server...</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840490#M25618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try create a brand new DB with sufficient privileges and all the right plugins etc and then restore your backup over it. I did the exact same for esx4-4.1 vCentre upgrade and worked a charm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gregg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Oct 2011 16:12:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Trying-to-upgrade-to-newest-vCenter-Server/m-p/840490#M25618</guid>
      <dc:creator>firestartah</dc:creator>
      <dc:date>2011-10-07T16:12:07Z</dc:date>
    </item>
  </channel>
</rss>

