Vcenter VCSA 6 update 1

After a recent power failure. I was able to bring all services back and running. All hosts, vcenter and VDP are restarted and Vcenter connects fine with client but when I try to connect with web it shows following error -

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x7f3c1817a650] _serverNamespace = /vsphere-client _isRedirect = false _port = 9090)

The IP address and DNS entry looks correct
LVL 4
pchettriIT DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have you waited for the Web Client to initialize ? because this error can occur, shortly after trying to connect to vCenter Server, shortly after boot.
0
pchettriIT DirectorAuthor Commented:
It was restarted on weekend and I tried connecting on Monday and it is still showing same error
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So, it's never responded correctly since rebooting, are all the services started?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

pchettriIT DirectorAuthor Commented:
yes all the servers are back and running. I am seeing some error on primary DC after running DCDIAG. I may have to reboot, if it is not acting as time source, though netdom fsmo query shows it as time source. May be the order of reboot after last week power failure other than that there are no issues. Not sure if this would cause DNS issue with vcenter though DNS resolution is working correctly for both external and internal servers and services

      ......................... xx.local failed test DNS
   Starting test: LocatorCheck
      GC Name: \\SI-SRV-xx.xx.local
      Locator Flags: 0xe00031bc
      Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
      A Primary Domain Controller could not be located.
      The server holding the PDC role is down.
      Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
      A Time Server could not be located.
      The server holding the PDC role is down.
      Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
      1355
      A Good Time Server could not be located.
      KDC Name: \\SI-SRV-xx.xx.local
      Locator Flags: 0xe00031bc
      ......................... xx.local failed test LocatorCheck
   Starting test: FsmoCheck
      GC Name: \\SI-SRV-xx.xx.local
      Locator Flags: 0xe00031bc
      Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
      A Primary Domain Controller could not be located.
      The server holding the PDC role is down.
      Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
      A Time Server could not be located.
      The server holding the PDC role is down.
      Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
      1355
      A Good Time Server could not be located.
      KDC Name: \\SI-SRV-xx
      Locator Flags: 0xe00031bc
      ......................... xx.local failed test FsmoCheck
   Starting test: Intersite
      Skipping site Default-First-Site-Name, this site is outside the scope
      provided by the command line arguments provided.
      ......................... xx.local passed test Intersite
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
is the time correct across all servers ?
1
pchettriIT DirectorAuthor Commented:
time shows correct. I am rebooting the domain controller to check. As I did not get any error on copy of domain controller that I P2V and imported to my lab......

.......

DCDIAG issue and ntp is fixed after DC reboot but I still have same issue connecting to Vcenter on web
0
pchettriIT DirectorAuthor Commented:
since DC is not reporting any issue I may have to restart vcenter so I tries to contact DC again and restarts all services
0
pchettriIT DirectorAuthor Commented:
rebooting both fixed the issue. I guess the all services on domain was not started during power failure and vcsa was not able to resolve DNS for some reason. First I restarted primary DC and vcsa and now I am able to access web console and VDP plugin.

Thanks
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If AD is not working correctly, it will not be able to authenticate!
0
pchettriIT DirectorAuthor Commented:
fixed after rebooting
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.