vickyshiv123
Enthusiast
Enthusiast

vCenter server service cannot start after migrating the DB from SQL server 2005 to SQL server 2014

Hi Everyone,

Could anybody please assist on the below details.

On saturday, we tried migrating vCenter server DB from SQL server 2005full edition to SQL server 2014 full edition and performed following tasks has been performed as per the below link,

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=79608...

  • Taken the snapshot of the vCenter VM
  • Stopped the VMware vCenter server services/VMware Virtual Management Services/VMware update Manager services
  • Taken the backup of the two DBs(vCenter server, VMware update manager) from the existing SQL server 2005
  • Restored two DBs successfully on the new SQL server 2014
  • Updated the ODBC connection for the vCenter server & VMware update Manager to point on the new SQL server 2014, tested the connection it was successful
  • Updated the vcdb properties on the vCenter server VM
  • Started the VMware vCenter server services, it failed to start and given the error

Windows could not start the VMware VirtualCenter Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.

  • For your information, I forget to stop the VMware vCenter server Inventory services, vSphere Profile Driven Storage service before taking the backup of the DBs running on SQL server 2005, would that be the issue preventing vCenter service to start after the restoration?
  • Tried the restarting both the VMware vCenter server Inventory services, vSphere Profile Driven Storage service after the restoration but still the same

Much appreciate if anyone kindly assist me on this

Thanks,

Vignesh

0 Kudos
6 Replies
rcporto
Leadership
Leadership

Have you updated the SQL client to the latest version ? And which account you're using in vCenter Server services ? Can you share the vpxd.log ?

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
krishna_v78
Enthusiast
Enthusiast

Hi Vignesh, Hope you have already verified the port 1433 is open on new SQL 2014 Database server. Regards, Balakrishna

0 Kudos
vickyshiv123
Enthusiast
Enthusiast

Hi Richardson,

Thanks for the reply.

Yes I have updated to SQL Server Native Client 11.0 or is there any other ODBC driver there for SQL server 2014, please advise

We are using local system account in the vCenter server services.

Regarding the vpxd.log, we have reverted to the current snapshot so cannot get the vpxd.log after the migration

Kindly help to advise me on this

Regards,

Vignesh

0 Kudos
vickyshiv123
Enthusiast
Enthusiast

Hi Balakrishna,

Thanks for your reply.

Yes have verified the port 1433 open on the new SQL 2014 DB server and did check the SQL services was started and running.

Is there any other thing that we need to check, pleae advise.

Regards,

Vignesh

0 Kudos
rcporto
Leadership
Leadership

So, you did a rollback and now are running the old SQL version, right ? If yes, next time after the DSN changes, try update the database password in registry just launching a elevated command prompt and running "vpxd -p".

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
vickyshiv123
Enthusiast
Enthusiast

Hi Richardson,

Yes we did a rollback and now we are running on the old SQL version now

So you mean to say that the DB password update would have caused not to start the vCenter services after the migration.

Moreover I am able to edit the following key settings.

HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Virtualcenter\DB.


Edit Key 2 and enter the username in the value data field

Please help to advise.

Regards,

Vignesh

0 Kudos