Daniela Martinez
asked on
Could not connect to one or more vCenter Server systems - vmware vsphere 5.5
Good evening,
I am currently presenting problems in my vCenter Quality-Development. The following message appears when I enter the vCenter (Image 1). Where I can not visualize the vm, datastore, Host, of both environments. (Image 2).
I entered my server Windows Server 2012, to validate the vCenter services, and note that the vCenter Server service and together with the VirtualCenter Management WebServices service, do not start, since they depend on each other. You can even see that they are waiting to start. (Image 3 and 4).
Validating the log in the vCenter folder, it tells me the following error:
"error 'utilvpxdVdb'] [VpxdVdb :: SetDBType] Failed to connect to database: ODBC error: (08001) - [Microsoft] [ODBC Driver 11 for SQL Server] TCP Provider: No connection could be made because the target machine Item.
-> Retry attempt: 1 ... "
The error indicates that there are connection problems with the vCenter database.
Validating the connection in the ODBC, performs a Test Connection test and there is a connection failure. (Image 5).
I spoke with the Database team, and they tell me that the instance that points to the vCenter is below, which is why the service can not start. Our vcenter points to the Quality instance.
The Database team recommended that I point the vCenter to the Development instance. Obviously to do this, you should reinstall the vCenter to select the new instance. Is this a recommended practice? What could be the consequences?
What other options would you have for trying to solve the problem, just the reinstallation? or do I depend on the data base equipment so that they can recover the affected instance?
I can only manage my vm, directly from ESXi, nor can I access my backups through VDP.
vCenter-Imagen1-.PNG
vCenter-Inventary-Imagen-2-.PNG
Virtual-Center-Server-Imagen-3-.PNG
VirtualCenter-Services-Imagen-4-.PNG
ODBC-Connection-Imagen-5-.PNG
I am currently presenting problems in my vCenter Quality-Development. The following message appears when I enter the vCenter (Image 1). Where I can not visualize the vm, datastore, Host, of both environments. (Image 2).
I entered my server Windows Server 2012, to validate the vCenter services, and note that the vCenter Server service and together with the VirtualCenter Management WebServices service, do not start, since they depend on each other. You can even see that they are waiting to start. (Image 3 and 4).
Validating the log in the vCenter folder, it tells me the following error:
"error 'utilvpxdVdb'] [VpxdVdb :: SetDBType] Failed to connect to database: ODBC error: (08001) - [Microsoft] [ODBC Driver 11 for SQL Server] TCP Provider: No connection could be made because the target machine Item.
-> Retry attempt: 1 ... "
The error indicates that there are connection problems with the vCenter database.
Validating the connection in the ODBC, performs a Test Connection test and there is a connection failure. (Image 5).
I spoke with the Database team, and they tell me that the instance that points to the vCenter is below, which is why the service can not start. Our vcenter points to the Quality instance.
The Database team recommended that I point the vCenter to the Development instance. Obviously to do this, you should reinstall the vCenter to select the new instance. Is this a recommended practice? What could be the consequences?
What other options would you have for trying to solve the problem, just the reinstallation? or do I depend on the data base equipment so that they can recover the affected instance?
I can only manage my vm, directly from ESXi, nor can I access my backups through VDP.
vCenter-Imagen1-.PNG
vCenter-Inventary-Imagen-2-.PNG
Virtual-Center-Server-Imagen-3-.PNG
VirtualCenter-Services-Imagen-4-.PNG
ODBC-Connection-Imagen-5-.PNG
ASKER
Hi Andrew,
I answer your questions.
A few questions?
1. How many hosts and VM do you have?
I have 12 Hosts, 59 vm in Development and 65 in Quality.
2. Do you really want to use Windows?
We use Windows because this is how the infrastructure is mounted.
3. Do you really want to use an external database?
The database is located on another Windows server, which we do not manage
4. Why not use VCSA? (Linux device)
It is an option, but for the moment we must work with what we have
I guess this is a new deployment, and do you understand that 5.5 ends at the end of life in September 2018?
I have in mind that the final support for version 5.5 ends in September.
I answer your questions.
A few questions?
1. How many hosts and VM do you have?
I have 12 Hosts, 59 vm in Development and 65 in Quality.
2. Do you really want to use Windows?
We use Windows because this is how the infrastructure is mounted.
3. Do you really want to use an external database?
The database is located on another Windows server, which we do not manage
4. Why not use VCSA? (Linux device)
It is an option, but for the moment we must work with what we have
I guess this is a new deployment, and do you understand that 5.5 ends at the end of life in September 2018?
I have in mind that the final support for version 5.5 ends in September.
Okay, well back to basics, with 12 Hosts, you really need vCenter Server to manage them, but remember vCenter Server is ONLY a management server it does not affect the running of VMs, when you add hosts to vCenter Server.
Back to basics.....you have an SQL database issue, the permissions or access is not correct, if you cannot run a test correctly, with correct username and password, vCenter Server is not going to be able to connect to the database.
Solve the SQL database issue, and try a re-installation of vCenter Server.
You state
but you have not deployed a working vCenter Server yet.... VCSA comes ready packaged and working....
Has vCenter Server failed, or is this a new install ? e.g. you've never had a working vCenter Server ?
Back to basics.....you have an SQL database issue, the permissions or access is not correct, if you cannot run a test correctly, with correct username and password, vCenter Server is not going to be able to connect to the database.
Solve the SQL database issue, and try a re-installation of vCenter Server.
You state
It is an option, but for the moment we must work with what we have
but you have not deployed a working vCenter Server yet.... VCSA comes ready packaged and working....
Has vCenter Server failed, or is this a new install ? e.g. you've never had a working vCenter Server ?
ASKER
Hello,
My vcenter, was working without problems, until the problem with the instance of the database.
In addition to the connection test of the database, perform it with the service user with whom the vcenter was installed.
Also vmware staff told us that it was very bad idea to point the vcenter to another instance, that was not the original one with which the installation of the vcenter was made.
My vcenter, was working without problems, until the problem with the instance of the database.
In addition to the connection test of the database, perform it with the service user with whom the vcenter was installed.
Also vmware staff told us that it was very bad idea to point the vcenter to another instance, that was not the original one with which the installation of the vcenter was made.
Okay, so vCenter Server FAILED! in service! So lets restart the question.......
So what network changes or changes to SQL have been performed that is your issue.
If you cannot resolve this with your "SQL Team", you will have no choice but to install a brand new installation to a brand new Database, this is why I suggested VCSA, because you'll be up and running with out issues, and "SQL Team"
(will not affect your VMs).
Are you a complex environment? e.g. do you use Distributed Switches, SRM, VDP, vOPs, vROPS., NSX etc ?
So what network changes or changes to SQL have been performed that is your issue.
If you cannot resolve this with your "SQL Team", you will have no choice but to install a brand new installation to a brand new Database, this is why I suggested VCSA, because you'll be up and running with out issues, and "SQL Team"
(will not affect your VMs).
Are you a complex environment? e.g. do you use Distributed Switches, SRM, VDP, vOPs, vROPS., NSX etc ?
ASKER
Hello,
No changes have been made at the Network or Database level, until the moment I spoke with the database team and they told me to carry out a reinstallation.
We have SRM and VDP
No changes have been made at the Network or Database level, until the moment I spoke with the database team and they told me to carry out a reinstallation.
We have SRM and VDP
Okay, stop what you are doing and escalate to VMware Support, otherwise SRM and VDP will both be broken.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Okay, you need to have a working connection to the SQL database, for VMware vSphere vCenter Server to install correctly.
A few questions ?
1. How many hosts and VMs do you have ?
2. Do you really want to use Windows ?
3. Do you really want to use an external database ?
4. Why not use the VCSA ? (Linux Appliance)
I assume this is a new deployment, and you understand that 5.5 goes end of life in September 2018!?