I have run into three reasons why your RD Web Access page would show no RemoteApps, Personal VMs, or VM Pools.
1. check to make sure the Conneciton Broker (or RDSH server, depending on how you are set up) is added to the Windows Authorization Access Group in AD.
2. If you try to make RDSH and RDCB co-exist on the same machine and make the RDSH part of a farm (I have seen people do this for testing and also because they did not want to virtualize and split these role services out). If you do this, when you choose a connection broker in RDWA, RDWA will show no apps. This also breaks RemoteApp and Desktop Connection. Dont try to combine these roles unless RDSH is in redirection mode only. Take the leap and virtualize and split these two role services up if RDSH is in app mode! :)
3. I had this happen to me. My Connection Broker had an unexpected shutdown. After this my RD Web Access portal came up empty, and the event logs on the connection broker (I have more than one RemoteApp/PersonalVM/Pooled VM resource so I use RD Connection Broker)
RD Web Access was unable to contact pyramid.ash.local, which is the server that is specified as running the RemoteApp and Desktop Connection Management service. Ensure that the name of the server that is specified as running the RemoteApp and Desktop Connection Management service is entered correctly, and that the server is running and available on the network. Error code: 1722.
Of course this was not true. I rebooted the RD COnnection Broker, and then refreshed my RD Web Access page. This did not fix it. I then re-added the RD Connection Broker to RD Web Access Configuration tab, and wha-la. All was fine.