Can't access VAMI - "Unable to get deployment status."

[samsheikh]

I'm sort of a neophyte.  I've installed vCenter 7.0.3/20150588 in a non-production environment for learning purposes.  I cannot access the VAMI.  Whenever I try accessing https://<hostname>:5480/configurev2/#/ or https://<ip>:5480/configurev2/#/ , I get an "Unable to get deployment status." error.

I am, however, able to access vCenter client, on port 443.

I've tried what was outlined in following article, but it didn't work for me: https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-2-Upgrade-Installer-Stage-2-Ex...

EDIT

This is a reply to padapa and Alex_Romeo.  I'm not sure what's going on, but every time I respond, the message disappears.  This is now my 7th or 8th attempt at responding about the DNS.

DNS works.  I read a thread about how it was important, so I manually inserted the records early on.

C:\Program Files (x86)\VMware\VMware Player\bin>nslookup
Default Server:  ar---dc.net
Address:  192.168.xxx.13

> ar---vcenter.net
Server:  ar---dc.net
Address:  192.168.xxx.13

Name:    ar---vcenter.net
Address:  192.168.xxx.5

> 192.168.xxx.5
Server:  ar---dc.net
Address:  192.168.xxx.13

Name:    ar---vcenter.net
Address:  192.168.xxx.5

Any and all help will be greatly appreciated.

[JordonC]

Thanks @JosephDalpiaz Adding those files fixed one of our broken RBO VCenter servers.  

[adamhart84]

After you run the "service-control --start --all the last line shouldn't say successfully started profile "NONE", it should say "ALL". I experienced this issue and checked the defaultStartProfile file located here /storage/vmware-vmon/defaultStartProfile.  I VI'd into that file and edited it to say "ALL" instead of "NONE" and all of my services started after that.