Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Not able to connect to vCenter 503 error
Issue connecting to vCenter
vSphere client could not connect to 192.168.x.x (IP for vCenter)
An unknown connection error occurred (The server could not interpret the clients request) The remote server returned an error 503 available
Getting this when trying to access vCenter via Web client and Thick Client, vSphere version is 6.0
Whats easiest and best way to get this working? I couldn't restart VMware Virtual Centre Server in services (2012R2 OS) got an 1068 error, rebooted the vCenter virtual machine, still getting the error
Small environment 2 ESXi hosts which were rebooted last night, no shared storage, there has been a NAS box setup recently
Version is Essentials 6.0
vSphere client could not connect to 192.168.x.x (IP for vCenter)
An unknown connection error occurred (The server could not interpret the clients request) The remote server returned an error 503 available
Getting this when trying to access vCenter via Web client and Thick Client, vSphere version is 6.0
Whats easiest and best way to get this working? I couldn't restart VMware Virtual Centre Server in services (2012R2 OS) got an 1068 error, rebooted the vCenter virtual machine, still getting the error
Small environment 2 ESXi hosts which were rebooted last night, no shared storage, there has been a NAS box setup recently
Version is Essentials 6.0
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Thanks Andrew, in the meantime (and i have seen your previous posts saying to use appliance) is there anything that can be done to get vCenter working in Windows?
is there anything that can be done to get vCenter working in Windows?
It's like this, 10 minutes to install VCSA, add your hosts back to new vCenter, VMs will not be affected in this process, and you've got a nice new shiny VCSA, not on Windows, not affected by Windows updates, and is the future of vCenter Server, (because VMware announced at VMworld 2015, eventually vCenter Server for Windows will be going away....)
OR... troubleshoot why your current Windows version has failed, which may not ever be fruitful and will take long than 10 minutes....
and if you've reboot vCenter Server, and waited 30 minutes and still have this error it's time to debug, which in our experience, unless password has expired....install new or re-install.
I can help you if you wish to troubleshoot. If Windows needs some more logs info..
Get me programdata/vmwarw/vcenter
Get me programdata/vmwarw/vcenter
Trouble shooting guide starts here -
"503 service unavailable" error when connecting to vSphere Web Client (2121043)
"503 service unavailable" error when connecting to vSphere Web Client (2121043)
Last question Andrew does the Windows vCenter have to be working in order to deploy VCSA, you said it would take 10 mins, any good deployment guide available? The customer does not have VMware support will that affect access to the appliance?
Last question Andrew does the Windows vCenter have to be working in order to deploy VCSA,
No.
Deployment Guide written by me...
HOW TO: Deploy and Install the VMWARE vCenter Server Appliance 6.0 (VCSA 6.0)
HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5)
If they do not have support, they'll not be entitled to download the software.
Check if they can login, to VMware and download, otherwise, new Windows Server, and re-install vCenter Server.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial