Greetings,
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. Current database is sitting on a SQL 2008 Enterprise server and works great. I backed it up too. 
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:
The problem is, I've tried with 3 different usernames, including a new one just to make certain I haven't missed anything. 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. 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). I still get this error.
DSN is 64-bit, using the SQL native drivers and tests just fine. Every other database from BES to SharePoint is working great, and even our DBA can't find any problems. 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.
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? Or a bug? We've been running the same configuration for years now and have upgraded with no problems in each case. This is the first time we're seeing this error and are more than a little bewildered.
Thanks in advance.
