PatrickHoban
Enthusiast
Enthusiast

HTTP Status 404 When Opening vCOPS

Installed the vCOPS 5.8 virtual appliance for testing. It was working fine until this morning when I powered my lab back on. I can get into https://vcops/admin just fine. When browsing to https://vcops/vcops-vsphere I get an error that says, "HTTP Status 404. The requested resource () is not available".

error.JPG

As the UI VM was booting I did notice that it took a long time to start vcopsService.

2.JPG

I've rebooted the vApp but keep getting the same error. I'm not really sure where to even start to look. Thoughts?

http://patrickhoban.wordpress.com
0 Kudos
4 Replies
mark_j
Virtuoso
Virtuoso

You cited this as your "lab". How have you been powering the vApp down hard or gracefully?

If you find this or any other answer useful please mark the answer as correct or helpful.
0 Kudos
PatrickHoban
Enthusiast
Enthusiast

I right clicked the vApp (VMware vCenter Operations Manager) & selected Shutdown. Watching the console of the VMs they both appear to be shutting down gracefully.

http://patrickhoban.wordpress.com
0 Kudos
MarkStrong
Enthusiast
Enthusiast

Hi Patrick,

I had exactly the same issue in vCOPs 5.8.4 environment.

I fixed it by unregistering ALL vCenter Servers.  There was an error message "Operation is complete but service restart failed", after each Unregister operation.

I then re-registered all vCenter Server back... Two vCenters were registered OK but when I tried to register the third, error message "Operation is complete but service restart failed" appeared and vCOPs UI stopped working again... As soon as I initiate Unregister process for that particular vCenter, everything went back to normal.  Will investigate this further.

Regards

Mark Strong

http://www.vStrong.info

VCP5, VCP4 | VCAP4-DCD | MCITP | HP Master ASE | CCNA, Cisco UCS Support Specialist
0 Kudos
MarkStrong
Enthusiast
Enthusiast

OK, here is an update on this issue:

No matter what I tried to do to re-register a particular vCenter:

  • used different case for the connection string (vCOPs will warn you that the server is the same) - helped me before with a different issue
  • used IP address instead of the server name
  • user different user to register vCenter
  • restarting vcops-admin services
  • restarting the appliance

...nothing worked!  There must be something not right withing the vCOPs database, something that screw everything up...

What I did is followed KB Removing non-existent virtual machines from the vRealize Operations Manager vApp (2020638)

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

to set quite aggressive DB purging and left it overnight.

The next morning the whole data for that particular vCenter have been purged from vCOPs DB and I managed to add vCenter again.

I hope this will help

Regards

Mark Strong

http://www.vStrong.info

VCP5, VCP4 | VCAP4-DCD | MCITP | HP Master ASE | CCNA, Cisco UCS Support Specialist
0 Kudos