Friday, March 6, 2015

Exchange 2010 federation calendar sharing reports the error: “The attendee’s server couldn’t be contacted. (Error code: 5016)”

Problem

You’ve completed configuring federation for two Exchange 2010 server organizations and begin testing calendar sharing but noticed that users from one of the Exchange organizations displays the following message when viewing free/busy schedule:

The attendee’s server couldn’t be contacted. (Error code: 5016)

image

Executing the Test-FederationTrust cmdlet on the Exchange Server in the domain that does not appear to be sharing calendar information displays the following errors:

[PS] C:\Windows\system32>Test-FederationTrust -UserIdentity administrator@domainABC.com

RunspaceId : 44741c0c-b08a-4979-abbc-9317481f9307
Id         : FederationTrustConfiguration
Type       : Success
Message    : FederationTrust object in ActiveDirectory is valid.

RunspaceId : 44741c0c-b08a-4979-abbc-9317481f9307
Id         : FederationMetadata
Type       : Error
Message    : The federation trust doesn't contain the same certificates published by the security token service in its
             federation metadata.

RunspaceId : 44741c0c-b08a-4979-abbc-9317481f9307
Id         : StsCertificate
Type       : Success
Message    : Valid certificate referenced by property TokenIssuerCertificate in the FederationTrust object.

RunspaceId : 44741c0c-b08a-4979-abbc-9317481f9307
Id         : StsPreviousCertificate
Type       : Success
Message    : Valid certificate referenced by property TokenIssuerPrevCertificate in the FederationTrust object.

RunspaceId : 44741c0c-b08a-4979-abbc-9317481f9307
Id         : OrganizationCertificate
Type       : Success
Message    : Valid certificate referenced by property OrgPrivCertificate in the FederationTrust object.

RunspaceId : 44741c0c-b08a-4979-abbc-9317481f9307
Id         : TokenRequest
Type       : Success
Message    : Request for delegation token succeeded.

RunspaceId : 44741c0c-b08a-4979-abbc-9317481f9307
Id         : TokenValidation
Type       : Error
Message    : Failed to validate delegation token.

[PS] C:\Windows\system32>


image

Solution

While there are probably various reasons why the errors above would be thrown, one of the environments I worked with that had this issue was fixed by rerunning the Manage Federation... wizard as such:

image

image

image

image

image

image

3 comments:

Jitendra Singh said...

I would like to fix exchange server corruption such as improper server shutdown, power issues, JET errors, drive errors, corrupt header errors, server down issues, and server crash incidents etc by third party edb repair software. It is most effective and hassle-free tool. http://www.repairexchange.org/

Kaye R. Jenkins said...

Functioning Exchange is required to mount or dismount an edb file and exporting mailboxes into pst too. As exchange server is no longer available then extraction of mailboxes from offline edb file into pst file format is totally dependent on external tools.

You can check these helpful tips:- http://www.recoverydeletedfiles.com/exchange-server-edb-recovery.html

johncthomas said...


You can easily recover Exchange EDB file data by using Exchange server recovery software resolve It also helps to get rid of Exchange corruption,power issues, JET errors, drive errors, corrupt header errors, server down issues, and server crash incidents etc without hassle.

Download now: http://www.softmagnat.com/exchange-server-recovery.html