Getting errors when trying to launch VMware Vsphere client
esx 4.0 vsphere client running on server 2003 sp2 R2. I installed IIS 6.0 yesterday on the server for something unrelated and now I cant access VSphere. i get the following error:
vSphere Client could not connect with the vCenter Server "servername"
Details: the server closed the connection.(The underlying connection was closed: The connection was closed unexpectedly)
I did uninstall IIS 6 but that didnt make a difference. Any ideas how to get this working
vSphere Client could not connect with the vCenter Server "servername"
Details: the server closed the connection.(The underlying connection was closed: The connection was closed unexpectedly)
I did uninstall IIS 6 but that didnt make a difference. Any ideas how to get this working
ASKER
That would appear to be the issue. Its not running and will not start it gives the error I have attached
vmware-error.bmp
vmware-error.bmp
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Its local SQL 2005
Are you "married" to your DB data? If not, you can do a reinstall/repair of vCenter to repair whatever may be broken. You can also check the SQL Express service to see if that is started before attempting a reinstall? If that isn't started, then your vCenter Server Service won't be able to start.
ASKER
The sql services are running. No I would say Im married to the data a reinstall would be fine. I didnt do the initial setup of our VMware enviroment so Im not all that familiar with this. I do have a call into tech support but its up to 4 hours before they call back. I think I will wait for them to see what they want to do.
Sure...keep me posted. You could restart vCenter to see if that works.
ASKER
I will. I have rebooted several times.
Thanks
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to reset it but I still was unable to restart the service. here is the error log
event-error.bmp
event-error.bmp
Ok...well, the reason for the error you posted is because of vCenter Server Service not starting. The reason why it's not starting is because something got messed with when you uninstalled IIS. At this point, your options are limited beyond doing a vCenter Server repair (should keep your data) and/or a complete reinstall.
Let me modify my above post...'the reason why vCenter Server Service isn't starting is *seemingly because* something got messed up with the IIS piece. I obviously don't know 100% that is the reason, but seems to be the case :)
ASKER
I figured that was the case. Although one clarification. I install the IIS 6.0 and thats when it broke then I uninstalled it hoping it would come back (it didnt) since I have reinstalled it.
Honestly, "bankadmin", it's hard to know what installing IIS did to vCenter. I'm not sure of what all registry keys/processes it messes with during its install :)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I switched the port for IIS and now Im getting this error
3-7-11erorr.bmp
3-7-11erorr.bmp
but your vCenter server is running fine now, correct?
ASKER
No Im still unable to start the virtual center server. My previous post is the error that the server generates when I attept to start the service.
hmmm...that's odd, since the source for the message is w3svc which is IIS.
It looks like the ISAPI message may be related to .Net . At this point, I'd say uninstall/re-install VC 4.1 with a reboot in between the two operations.
It looks like the ISAPI message may be related to .Net . At this point, I'd say uninstall/re-install VC 4.1 with a reboot in between the two operations.
Concur; and, a reinstall of VC doesn't mean you'll lose your data. If memory serves, you get prompted during the (re)install if you wanna keep your current database. Did you ever get to speak to VMware support?
~coolsport00
~coolsport00
ASKER
They still have yet to call me back.. The worst support ever
Wow :(
ASKER
Finally got it taken care of with the the help of VMware. There were several things wrong everytime we would clean up one error another would pop-up.. Thanks for the help
ASKER
THere were several things wrong some of which were mentioned above
~coolsport00