1. UNIFYBroker Forum
  2. UNIFYBroker/Microsoft SharePoint
  3. Questions
0
Answered

Could not find endpoint element

Bob Bradley 10 years ago in UNIFYBroker/Microsoft SharePoint • updated by anonymous 9 years ago • 5

The following exception was displayed when attempting schema discovery for my WSS list connector:

Could not find endpoint element with name 'BasicHttpBinding_ISharePoint2010UserProfileService' and contract 'OrganizationProfileManager.ISharePoint2010OrganisationProfileService' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element.

This is after seeing a similar error, locating QDET-213 (I could not find any config instructions on https://unifysolutions.jira.com/wiki/display/IDBSP40/Microsoft+SharePoint+List+Connector) and adding the following sections to the Unify.Service.Connect.exe.config file:

        <binding name="BasicHttpBinding_ISharePoint2010UserProfileService"
					   
          closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00"
          sendTimeout="10:00:00" allowCookies="false" bypassProxyOnLocal="false"
          hostNameComparisonMode="StrongWildcard" maxBufferSize="204003200"
          maxBufferPoolSize="524288" maxReceivedMessageSize="204003200"
          messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"
          useDefaultWebProxy="true">
          <readerQuotas maxDepth="32" maxStringContentLength="65536000" maxArrayLength="65536000"
            maxBytesPerRead="65536000" maxNameTableCharCount="65536000" />
          <security mode="TransportCredentialOnly">
            <transport clientCredentialType="Ntlm" proxyCredentialType="None"
              realm="" />
            <message clientCredentialType="UserName" algorithmSuite="Default" />
          </security>
        </binding>
        <binding name="BasicHttpBinding_ISharePoint2010OrganisationProfileService"
          closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00"
          sendTimeout="10:00:00" allowCookies="false" bypassProxyOnLocal="false"
          hostNameComparisonMode="StrongWildcard" maxBufferSize="204003200"
          maxBufferPoolSize="524288" maxReceivedMessageSize="204003200"
          messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"
          useDefaultWebProxy="true">
          <readerQuotas maxDepth="32" maxStringContentLength="65536000" maxArrayLength="65536000"
            maxBytesPerRead="65536000" maxNameTableCharCount="65536000" />
          <security mode="TransportCredentialOnly">
            <transport clientCredentialType="Ntlm" proxyCredentialType="None"
              realm="" />
            <message clientCredentialType="UserName" algorithmSuite="Default" />
          </security>
        </binding>
      </basicHttpBinding>
    </bindings>
    <client>
      <endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ISharePoint2010UserProfileService"
      contract="UserProfileManager.ISharePoint2010UserProfileService" name="BasicHttpBinding_ISharePoint2010UserProfileService" />
      <endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ISharePoint2010OrganisationProfileService"
      contract="OrganizationProfileManager.ISharePoint2010OrganisationProfileService" name="BasicHttpBinding_ISharePoint2010OrganisationProfileService" />
    </client>

Note the wording in the error text - specifically that the element name it claims is missing*UserProfileService* but the contract contains OrganisationProfileService. When I tried modifying the above config to reflect this I still got an error - so I am thinking there may be a build issue?

Bob Bradley 10 years ago

Added a third client endpoint:

    <client>
      <endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ISharePoint2010UserProfileService"
      contract="UserProfileManager.ISharePoint2010UserProfileService" name="BasicHttpBinding_ISharePoint2010UserProfileService" />
      <endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ISharePoint2010OrganisationProfileService"
      contract="OrganizationProfileManager.ISharePoint2010OrganisationProfileService" name="BasicHttpBinding_ISharePoint2010OrganisationProfileService" />

      <endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ISharePoint2010OrganisationProfileService"
      contract="OrganizationProfileManager.ISharePoint2010OrganisationProfileService" name="BasicHttpBinding_ISharePoint2010UserProfileService" />
    </client>

Now I am getting the following error on schema discovery, but I don't understand why it is looking for a userprofile.svc when all I am interested is a WSS list?

There was no endpoint listening at http://fimdevadminservice.originenergy.com.au/_vti_bin/unify/userprofile.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Bob Bradley 10 years ago

Ah - now I see this is coming from default agent setting - how do I work out what 

http://fimdevadminservice.originenergy.com.au/_vti_bin/xxx.svc

URL to set for a WSS list?

Bob Bradley 10 years ago

I found the name of the lists webservice (does not end in ".svc":

Am I supposed to use this, and if so do we have a sample config for a WSS list (I can now see I am using a hybrid of the UserProfile one)?

Adam van Vliet 10 years ago

Hi Bob Bradley,

I have a feeling you may have created the wrong agent, the one you want is Microsoft Office Sharepoint Server 2007.

Once set up, you only need the base address of the SharePoint instance. The connector knows the rest of the url (_vti_bin/Lists.asmx).

Regarding testing the agent, unfortunately there isn't anything available to call to make sure it's functioning.

Bob Bradley 10 years ago

User error (and some doco shortcomings).

Customer support service by UserEcho