{"support":{"yesButton":"Sí","noButton":"No","feedback":{"title":"¿Qué podemos hacer para mejorar?"},"submitButton":"Enviar","successMessage":"Gracias por tus comentarios","title":"¿Te fue de ayuda?","feedbackPercentLabel":"de las personas encontraron esto útil","captcha":{"error":"Por favor, marca una casilla"}}}
Buscar Preguntas Frecuentes
{"searchBar":{"inputPlaceholder":"Busca por palabra clave o haz una pregunta","searchBtn":"Buscar","error":"Ingresa una palabra para buscar"}}
PowerChute Network Shutdown does not proceed with VM Startup after powering on the vCenter Server VM
Issue:
PowerChute Network Shutdown does not proceed with VM Startup after powering on the vCenter Server VM. PowerChute shows an event log entry “Attempting to start vCenter Server VM <VM Name>” but does not proceed to power on VMs.
Product Line:
PowerChute Network Shutdown v4.2, v4.3, v4.4
Environment:
PowerChute Network Shutdown configured with VMware
Cause:
This can occur when some vCenter Services are unable to start.
Solution:
Connect to the vCenter Server VM and check the status of vCenter Services. Manually start services that have not started.
PowerChute Network Shutdown does not proceed with VM Startup after powering on the vCenter Server VM. PowerChute shows an event log entry “Attempting to start vCenter Server VM <VM Name>” but does not proceed to power on VMs.
Product Line:
PowerChute Network Shutdown v4.2, v4.3, v4.4
Environment:
PowerChute Network Shutdown configured with VMware
Cause:
This can occur when some vCenter Services are unable to start.
Solution:
Connect to the vCenter Server VM and check the status of vCenter Services. Manually start services that have not started.
- On Windows, the services.msc console can be used.
- On Linux, execute the following command: