none
Lync 2013 User Presence Unknown in OCS 2007 R2 Client RRS feed

  • Question

  • Lync 2013 User Presence Unknown in OCS 2007 R2 Client

    OCS users had reported that they can’t view the presence status of some Lync 2013 users in OCS client, presence unknown. I found one of FE01 server that registration for those Lync 2013 users have that effect on OCS client. I shut down FE01 server to force Lync 2013 users to register to another FE02 server. After Lync 2013 users signed in again (Connected Lync Server has been changed to: FE02), OCS client can view their presence. However I still don't found the root cause, when I run Test-CsRegistration in both FE server. The FE02 passed, but FE01 show the following error. I checked the same certificate was imported to FE01/FE02.

    Target Fqdn   : ###########.com

    Result        : Failure

    Latency       : 00:00:00

    Error Message : Unable to perform authentication of credentials.

                    Inner Exception:NegotiateSecurityAssociation failed, error: -2146893053

    Diagnosis     :

    VERBOSE: Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STRegisterWorkflow' started.
    Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STRegisterWorkflow' completed in '6.26E-05' seconds.
    An exception 'Unable to perform authentication of credentials.' occurred during Workflow Microsoft.Rtc.SyntheticTransactions.Workflows.STRegisterWorkflow execution.
    Exception Call Stack:    at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()
       at Microsoft.Rtc.Collaboration.LocalEndpoint.EndEstablish(IAsyncResult result)
       at Microsoft.Rtc.SyntheticTransactions.Activities.RegisterActivity.InternalExecute(ActivityExecutionContext executionContext)
       at Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Execute(ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
       at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
       at System.Workflow.Runtime.Scheduler.Run()
       at Microsoft.Rtc.Internal.Sip.SipAuthenticationHelper.NegotiateSecurityAssociation(SecurityAssociationBase sa, String inputString, ContextFlags inContextAttributes, String& outputString)
       at Microsoft.Rtc.Internal.Sip.ProtocolAuth.DoProtocolOutgoingNegotiation(SecurityAssociation sa, SipMessage message, ChallengeData challengeData)
       at Microsoft.Rtc.Internal.Sip.AuthenticationControlModule.NegotiateSecurityAssociation(SecurityAssociation sa, SipMessage message, NegotiateArgs negotiateArguments)
    'RegisterActivity2' sequence activity started.
    'RegisterActivity2' sequence activity completed in '6.01E-05' seconds.
    'Register' activity started.
    Sending Registration request:
     Target Fqdn      = #######.com
     User Sip Address = sip:#####@####.com
     Registrar Port = 0.
    Authentication Type 'IWA' is selected.
    'UnRegister' activity started.
    'UnRegister' activity completed in '0.0004703' seconds.

    VERBOSE: Workflow Instance ID '4fb4f7ee-de24-432b-b758-c4abd2010794' completed.
    VERBOSE: Workflow run-time (sec): 0.2430276.

    Does anyone know what does the error code 2146893053 means? Many Thanks.



    • Edited by GemmySit Monday, March 31, 2014 3:24 AM
    Saturday, March 29, 2014 7:48 PM

Answers

  • Hi,

    Please check if all services started on FE01.

    It may cause by the issue of registrar authentication. Please also check if Registrar Setting click all authentication on FE01 Lync Server Control Panel.

    Best Regards,

    Eason Huang


    Eason Huang
    TechNet Community Support

    • Marked as answer by Lisa.zhengModerator Sunday, April 6, 2014 8:27 AM
    • Unmarked as answer by GemmySit Thursday, June 5, 2014 2:03 AM
    • Marked as answer by GemmySit Thursday, June 5, 2014 2:04 AM
    Wednesday, April 2, 2014 7:50 AM
    Moderator

All replies

  • Hi,

    Please check if all services started on FE01.

    It may cause by the issue of registrar authentication. Please also check if Registrar Setting click all authentication on FE01 Lync Server Control Panel.

    Best Regards,

    Eason Huang


    Eason Huang
    TechNet Community Support

    • Marked as answer by Lisa.zhengModerator Sunday, April 6, 2014 8:27 AM
    • Unmarked as answer by GemmySit Thursday, June 5, 2014 2:03 AM
    • Marked as answer by GemmySit Thursday, June 5, 2014 2:04 AM
    Wednesday, April 2, 2014 7:50 AM
    Moderator
  • Thanks, Eason.

    We found a duplicate SPN record in FE01 computer account, after rit has been removed, the issue was fixed.

    Thursday, June 5, 2014 2:07 AM