I would agree with this is probably a permissions issue with not seeing any items in vCenter web client. I've ran into that before.
As for the alerts seen in vCenter Service Health this is what I've come up with for a solution.
From my searches through the web I have seen that the three services, Storage Profile Service, vSphere Web Client and Orchestrator all try to start on port 31000 by default. Below this is a known issue in 5.0 U3 and we're running 5.1U1a and still are seeing this crop up. I looked through the 5.1 and 5.5 release notes and didn't find anything related to this
Alerts on these three services:
License Services -
- Asset Properties History service - Cannot obtain asset properties from vCenter Server query service
- VMware vSphere Profile-driven Storage Service - Unable to retrieve health data from http://localhost/sps/health.xml
- VMware vCenter Storage Monitoring Service - Service initialization failed
This is a known issue with vCenter 5.0 U3
VMware vCenter Server 5.0 Update 3 Release Notes
KB article
More explanation in a community forum