I've just finished playing with my lab, so I wanted to update you on my findings.
Actually this is not an issue, but an expected behaviour for IIS and Tomcat caused by cross-port usage conflicts - IIS procces takes the port 80 before the VirtualCenter Server service does. That is why the VirtualCenter Server service can not start.
As soon as I've disabled/stopped all IIS services (IIS Admin Service) my VMware Virtual Center Server service was up and running again. I continued googling for some known ways of resolving this...so here you are, should help:1st way
1. Set both services Startup Type
2. Start VMware Virtual Center Server service first and then IIS Admin Service
This workaround would work unless you reboot vCenter Server machine, in this case you should repeat the steps when system boots.2nd one
(seems to be a better choice):
You can change the default port (80) in IIS, so that both web servers are using different ports.
Here is the corresponding KB for that: http://support.microsoft.com/kb/149605
Hope it helps!