vcenter server error???

[RAS_RANA]

hey

ASA

recently i installed vcenter server on windows 2008 R2 server and access it through it vsphere client. but when i restart pc and login to vcenter server then the server was not connected. what to do now?? please guide me?? and when i first time access vcenter server then i write only ip address not the user-name and password and it loged in but after restarting the computer it was not possible to login into vcenter server.

please guide me.

thanks

[Rah201110141]

what error message it is giving on login failure ?

[RAS_RANA]

can not connect to 192.168.98.230 (error)

and some others i will upload the picture yesterday because this pc was in my lab and now im in my room.

[TomHowarth]

What Error message are you getting, have you checked that the services are running,  is the SQL server installed on the same server as vCenter?  Please answer these first batch of questions and we will see if we can help you

[jdptechnc]

I run into an issue where the vCenter Server services in Windows is not started when the server reboots.  You can just start the service, and then you can connect to vCenter.  I had to change the dependancies of the service to depend on the SQL Server service in order to prevent this from happening again (this vCenter had SQL on the same box).

[RAS_RANA]

yes SQL is installed on this same server and also vsphere client is installed on this same server.

[TomHowarth · Accepted solution]

Read and follow the instruction contained in this KB article,  what is happening is that when you boot the server the vCenter service is attempting to start before your SQL Express instance has instanciated.

you need to place a delay on your vCenter server to get it to wait for the SQL Service to start before it attemps to start.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100766...

[RAS_RANA]

this is error.

see the pic

[jdptechnc]

Use Remote Desktop Connection to log in to Windows on your vCenter server.  Run services.msc and look to see if the service listed in the attachment is started.  If not, then start it.  You should then be able to connect to the vCenter application using the vCenter client.  Then, follow Tom's KB posted above to keep the problem from happening again.