locked
Cannot complete Lync2013 integration because autodiscover/metadata/json/1 does not exist RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I am trying to setup integration between Microsoft Lync 2013 Server and Exchange 2013 Server so that in OWA you can see presence information and also use Instant Messaging.

    I am able to complete all the steps except for the following line on the Lync server:

    New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl "https://autodiscover.domain.com/autodiscover/metadata/json/1"


    I am getting an error that its not found:

    New-CsPartnerApplication : Cannot bind parameter 'MetadataUrl' to the target. Exception setting "MetadataUrl": "The
metadata document could not be downloaded from the URL in the MetadataUrl parameter or downloaded data is not a valid
metadata document, error: The remote server returned an error: (404) Not Found."

    Now I've already followed THIS thread: http://blogs.technet.com/b/jenstr/archive/2012/11/22/getting-internal-server-error-500-when-creating-new-cspartnerapplication-for-exchange-2013.aspx  But that did not help me at all.  Nor should it because that particular thread is a procedure to remedy an error 500.  Remember I am getting an error 404.

    I can validate that the path to /autodiscover/metadata/json/1 does not exist because I get a 404 in any web browser that I attempt to access this path.  Also in IIS Manager on Exchange I do not even see a metadata folder.  IIS has been reset and also the server has been rebooted as of 7:40 AM EST today and the issue persists.

    I am not sure what goes in that location but I would be willing to accept if someone else would upload their metadata/json/1 file on SkyDrive and I could put it at this location.

    Otherwise Autodiscover service appears to be working as Outlook and Lync clients do not pose an error.  Testing e-mail autodiscover returns correct values and the paths /autodiscover/Autodiscover.svc and also autodiscover/autodiscover.xml are both reachable in a web browser.

    • Moved by Amy.Wang Tuesday, December 2, 2014 1:15 AM Lync related
    Monday, December 1, 2014 1:06 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi KJSTech1,

    You could try to modify the autodiscover Url by following command.

    Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri "https://autodiscover.contoso.com/autodiscover/autodiscover.xml"


    Run the following command in Lync Management Shell.

    Set-CsOAuthConfiguration -Identity global -ExchangeAutodiscoverUrl "https://autodiscover.contoso.com/autodiscover/autodiscover.svc"

    After doing the above work, please re-run the New-CsPartnerApplication command to test.

    Best regards,

    Eric


    • Edited by Eric_YangK Wednesday, December 3, 2014 7:13 AM
    Wednesday, December 3, 2014 7:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have two exchange servers.  A 2007 and a 2013.  Can they both be set to https://autodiscover.domain.com/autodiscover/autodiscover.xml ?  


    Currently external and internal DNS points to autodiscover.domain.com to the cname of the Exchange 2013 server.

    Wednesday, December 3, 2014 12:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi.

    Were you able to resolve this issue?

    Before you criticize a man, walk a mile in his shoes. That way, if he gets angry, he's a mile away and barefoot.

    Wednesday, September 16, 2015 12:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Despite that error message, Lync integration works fine with Exchange.  So yes I guess you can say we were able to resolve the issue.  Not resolve the error message, but the integration works and that is the bottom line.
    Wednesday, September 16, 2015 4:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    how did you solve this issue?

    I've the same problem by connecting SharePoint 2013 with Exchange 2013. "autodiscover/metadata/json/1" does not exist.

    Thanks for your help.

    Kind regards


    • Edited by 123tdona Monday, September 28, 2015 9:53 AM
    Monday, September 28, 2015 9:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello.

    Same for me, didn't found an answer yet :(.

    Regards,

    Thursday, November 5, 2015 2:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Had you looked at this page how to activate the partner application?

    https://technet.microsoft.com/en-us/library/jj204975.aspx?f=255&MSPPError=-2147217396

    regards Holger Technical Specialist UC

    Saturday, November 7, 2015 8:47 AM