pchettri
asked on
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: [N7Vmacore4Http16LocalServ
The IP address and DNS entry looks correct
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServ
The IP address and DNS entry looks correct
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
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.
ASKER
It was restarted on weekend and I tried connecting on Monday and it is still showing same error
So, it's never responded correctly since rebooting, are all the services started?
ASKER
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_SERV
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_SERV
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
......................... 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_SERV
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_SERV
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
is the time correct across all servers ?
ASKER
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
.......
DCDIAG issue and ntp is fixed after DC reboot but I still have same issue connecting to Vcenter on web
ASKER
since DC is not reporting any issue I may have to restart vcenter so I tries to contact DC again and restarts all services
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If AD is not working correctly, it will not be able to authenticate!
ASKER
fixed after rebooting