web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Dynamics CRM Metadata URL is disabled

(0) ShareShare
ReportReport
Posted on by 6,212

Hi

I am trying to integrate Dynamics CRM 2016 with Sharepoint 2013 onpremises server to server side integration. When I run the below command

$i = New-SPTrustedSecurityTokenIssuer –Name "crm" –IsTrustBroker:$false –MetadataEndpoint  "192.168.3.39/.../json"

The remote server error 400 return bad request error occured.

So I copy the url of metadata and placed in the browser and it displays
Metadata URL is not published.

Could you please tell me, to resolve the 400 error Do I need to enable metadata? If it How should i enable?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    If you will open 192.168.3.39/.../metadataendpoint.svc that url you will get a list of instructions how to activate publishing of metadata. If instructions are not available for you for some reason here is the list:

    1. Create the following service behavior configuration, or add the <serviceMetadata> element to an existing service behavior configuration:

    <behaviors>

       <serviceBehaviors>

           <behavior name="MyServiceTypeBehaviors" >

               <serviceMetadata httpGetEnabled="true" />

           </behavior>

       </serviceBehaviors>

    </behaviors>

    2. Add the behavior configuration to the service:

    <service name="MyNamespace.MyServiceType" behaviorConfiguration="MyServiceTypeBehaviors" >

    Note: the service name must match the configuration name for the service implementation.

    3. Add the following endpoint to your service configuration:

    <endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />

    Note: your service must have an http base address to add this endpoint.

    The following is an example service configuration file with metadata publishing enabled:

    <configuration>

       <system.serviceModel>

           <services>

               <!-- Note: the service name must match the configuration name for the service implementation. -->

               <service name="MyNamespace.MyServiceType" behaviorConfiguration="MyServiceTypeBehaviors" >

                   <!-- Add the following endpoint.  -->

                   <!-- Note: your service must have an http base address to add this endpoint. -->

                   <endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />

               </service>

           </services>

           <behaviors>

               <serviceBehaviors>

                   <behavior name="MyServiceTypeBehaviors" >

                       <!-- Add the following element to your service behavior configuration. -->

                       <serviceMetadata httpGetEnabled="true" />

                   </behavior>

               </serviceBehaviors>

           </behaviors>

       </system.serviceModel>

    </configuration>

  • Verified answer
    Alagunellaikumar Profile Picture
    6,212 on at

    Hi

    Enabling the metadata is no need. Reason for 400 error is organization was disabled from my end

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans