2013-09-03T21:34:18.800+05:30 [03612 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: VMware vCenter with username
2013-09-03T21:34:18.800+05:30 [03612 error 'utilvpxdVdb'] [VpxdVdb::SetDBType]: Database error: ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
2013-09-03T21:34:18.800+05:30 [03612 error 'Default'] Error getting configuration info from the database
That looks like a not properly configured System DSN or an issue in the registry for the database part.
Hi,
Take a look at a related link https://communities.vmware.com/message/1229184?z=hI303Q - relates to 2.5 but still is applicable, nearly always related to connection to the database or its associated server
I am using the local database. Can you suggest me what i can check?
The vpxd.log otherwise this becomes a guess game
Location of vCenter Server log files
VMware KB: Location of vCenter Server log files
Take the highest number one and clean it out of all domain and security related stuff and attach it here. If the size is below a couple of kb then db issues are most likely otherwise the vpxd.log will give us the correct hint to the solution
Here is related KB for this issue : VMware KB: Starting the VMware VirtualCenter Server service fails with the error: Windows could not ...
thread moved from VMware ESXi 5 to VMware vCenter™ Server
I had this problem some time ago and solved it. Please see the below video i made on the solution.
Also please keep us posted ....
I've seen this before where the vCenter server has run out of disk space. Check both the application and SQL server.
2013-09-03T21:34:18.800+05:30 [03612 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: VMware vCenter with username
2013-09-03T21:34:18.800+05:30 [03612 error 'utilvpxdVdb'] [VpxdVdb::SetDBType]: Database error: ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
2013-09-03T21:34:18.800+05:30 [03612 error 'Default'] Error getting configuration info from the database
That looks like a not properly configured System DSN or an issue in the registry for the database part.