locked
Error enabling Federation Sharing RRS feed

  • Question

  • Hi, we have Exchange 2013 CU13 with 2 CAS and 3 MBX in DAG configuration. We tried to enable Federation sharing but kept getting the following error either via EAC or EMS.

    Microsoft.Exchange.Management.FederationProvisioning.FederationMetadataException: Unable to access the Federation Metadata document from the federation partner. Detailed information: "The underlying connection was closed: An unexpected error occurred on a send.". at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Management.SystemConfigurationTasks.NewFederationTrust.ProvisionSTS() at Microsoft.Exchange.Management.SystemConfigurationTasks.NewFederationTrust.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed) 

    Any helps would be appreciated!

    Thanks

    Wednesday, August 17, 2016 3:02 PM

Answers

  • My experience is that this is usually caused by a firewall restriction or a misconfigured reverse web proxy server.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Wednesday, August 17, 2016 11:12 PM
    Moderator

All replies

  • Hi, we have Exchange 2013 CU13 with 2 CAS and 3 MBX in DAG configuration. We tried to enable Federation sharing but kept getting the following error either via EAC or EMS.

    Microsoft.Exchange.Management.FederationProvisioning.FederationMetadataException: Unable to access the Federation Metadata document from the federation partner. Detailed information: "The underlying connection was closed: An unexpected error occurred on a send.". at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Management.SystemConfigurationTasks.NewFederationTrust.ProvisionSTS() at Microsoft.Exchange.Management.SystemConfigurationTasks.NewFederationTrust.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed) 

    Any helps would be appreciated!

    Thanks

    Wednesday, August 17, 2016 3:04 PM
  • My experience is that this is usually caused by a firewall restriction or a misconfigured reverse web proxy server.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Wednesday, August 17, 2016 11:12 PM
    Moderator
  • I am merging this thread with your duplicate post if a different forum.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Wednesday, August 17, 2016 11:13 PM
    Moderator