No metadata returned for SP with matching protocol

[Wessel, Keith]

2016-01-11 17:38:10,209 - INFO [org.opensaml.saml.common.binding.impl.SAMLMetadataLookupHandler:128] - Message Hi,

We have a vendor SP we're trying to partner with (who sent us metadata via email) that we added to our local IDP metadata file. This was my first time adding a new SP to our V3 IDP, so I might be overlooking something. When the SP tried to send a request to us, they get an error and we see:
2016-01-11 17:38:10,209 - INFO [org.opensaml.saml.common.binding.impl.SAMLMetadataLookupHandler:128] - Message Handler:  No metadata returned for https://cchp.tuapath.com/shibboleth-sp in role {urn:oasis:names:tc:SAML:2.0:metadata}SPSSODescriptor with protocol urn:oasis:names:tc:SAML:2.0:protocol
2016-01-11 17:38:10,210 - WARN [net.shibboleth.idp.profile.impl.SelectProfileConfiguration:111] - Profile Action SelectProfileConfiguration: Profile http://shibboleth.net/ns/profiles/saml2/sso/browser is not available for relying party configuration shibboleth.UnverifiedRelyingParty
2016-01-11 17:38:10,210 - WARN [org.opensaml.profile.action.impl.LogEvent:76] - An error event occurred while processing the request: InvalidProfileConfiguration

I'm not seeing any errors when I issue a reload-metadata.sh with the ID of that local file. In addition, I have refresh parameters set in metadata-provider.xml, so the file should have reloaded automatically, anyway, assuming that works for metadata in loca file resources like it did in V2.

I'm confident the metadata has the rquested protocol in it. Here are the first two lines:
<EntityDescriptor entityID=" https://cchp.tuapath.com/shibboleth-sp ">
      <SPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

I also assume that, if the metadata was invalid, I'd be getting an error that the entityID wasn't in metadata instead of that it simply couldn't' find the matching protocol.

Any thoughts on what I or the vendor might be doing wrong?

Thanks,
keith