locked
The Test-OrganizationRelationship function on Exchange 2010 SP3 Rollup4 error RRS feed

  • Question

  • Hi

      If I run Test-OrganizationRelationship function on Exchange 2010 SP3 Rollup4 the fallowing error appear:

    [PS] C:\WINDOWS\system32>Test-OrganizationRelationship -Identity "emag" -UserIdentity marian.nica@flanco.ro -verbose
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Active Directory session settings for
    'Test-OrganizationRelationship' are: View Entire Forest: 'False', Default Scope: 'hq.flanco.ro', Configuration Domain
    Controller: 'CALYPSO.hq.flanco.ro', Preferred Global Catalog: 'CALYPSO.hq.flanco.ro', Preferred Domain Controllers: '{
    CALYPSO.hq.flanco.ro }'
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Runspace context: Executing user: hq.flanco.ro/FLANCO -
    Users/HQ/IT/Marian NICA, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Beginning processing &
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Instantiating handler with index 0 for cmdlet extension
    agent "Admin Audit Log Agent".
    VERBOSE: [12:24:44.391 GMT] Test-OrganizationRelationship : Current ScopeSet is: { Recipient Read Scope: {{, }},
    Recipient Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive
    Recipient Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [12:24:44.391 GMT] Test-OrganizationRelationship : Searching objects "marian.nica@flanco.ro" of type "ADUser"
    under the root "$null".
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Previous operation run on global catalog server
    'CALYPSO.hq.flanco.ro'.
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Searching objects "emag" of type "OrganizationRelationship"
    under the root "$null".
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Previous operation run on domain controller
    'CALYPSO.hq.flanco.ro'.
    VERBOSE: Test that organization relationships are properly configured.
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Resolved current organization: .
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Calling the Microsoft Exchange Autodiscover service for the
    remote federation information.
    VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
    https://autodiscover.emag.ro/autodiscover/autodiscover.svc.
    VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
    https://autodiscover.emag.ro/autodiscover/autodiscover.svc.
    VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : Generating delegation token for user marian.nica@flanco.ro
    for application FYDIBOHF25SPDLT.exchangedelegation.emag.ro.
    VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The delegation token was successfully generated.
    VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service is being called
    to determine the remote organization relationship settings.
    VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The Client will call the Microsoft Exchange Autodiscover
    service using the following URL: https://autodiscover.emag.ro/autodiscover/autodiscover.svc/WSSecurity.
    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service failed to be
    called at 'https://autodiscover.emag.ro/autodiscover/autodiscover.svc/WSSecurity' because the following error occurred:
    SoapException.Code =
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd:InvalidSecurityToken
    Exception:
    System.Web.Services.Protocols.SoapHeaderException: An error occurred when processing the security tokens in the
    message.
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse
    response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.Exchange.SoapWebClient.CustomSoapHttpClientProtocol.<>c__DisplayClass4.<Invoke>b__3()
       at
    Microsoft.Exchange.SoapWebClient.HttpAuthenticator.NoHttpAuthenticator.AuthenticateAndExecute[T](SoapHttpClientProtocol
    client, AuthenticateAndExecuteHandler`1 handler)
       at Microsoft.Exchange.SoapWebClient.SoapHttpClientAuthenticator.AuthenticateAndExecute[T](SoapHttpClientProtocol
    client, AuthenticateAndExecuteHandler`1 handler)
       at
    Microsoft.Exchange.SoapWebClient.AutoDiscover.DefaultBinding_Autodiscover.GetOrganizationRelationshipSettings(GetOrgani
    zationRelationshipSettingsRequest Request)
       at
    Microsoft.Exchange.Management.Sharing.TestOrganizationRelationship.<>c__DisplayClass8.<GetInvokeDelegate>b__7(DefaultBi
    nding_Autodiscover binding)
       at
    Microsoft.Exchange.SoapWebClient.AutodiscoverClient.<>c__DisplayClassf.<InvokeAndFollowSecureRedirects>b__c(IWebProxy
    webProxy)
       at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeWithWebProxy(String url, InvokeWithWebProxyDelegate
    invokeWithWebProxy)
       at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeAndFollowSecureRedirects(InvokeDelegate invokeDelegate,
    Uri url)
       at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeForUrl(InvokeDelegate invokeDelegate, Uri url)

    .
    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : The Autodiscover call failed.


    RunspaceId  : b3b378f5-d912-4042-b578-e949b54da4c1
    Identity    :
    Id          : AutodiscoverServiceCallFailed
    Status      : Error
    Description : The Autodiscover call failed.
    IsValid     : True

    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : Admin Audit Log: Entered Handler:OnComplete.
    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : Ending processing &

        
    Sunday, January 12, 2014 12:12 AM

All replies