locked
Response group workflow cannot be saved RRS feed

  • Question

  • Log Name:      Lync Server

    Source:        LS User Replicator

    Date:          6/14/2017 4:08:57 PM

    Event ID:      30058

    Task Category: LS User Replicator

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      Sfb.contoso.com

    Description:

    msRTCSIP-UserRoutingGroupId attribute for a user is incorrect in Active Directory domain:contoso.com

    The user with these attributes has DN:CN={2c1adcc7-7bb4-4285-a3aa-5b4ab8bbf3ba},CN=Application Contacts,CN=RTC Service,CN=Services,CN=Configuration,DC=contoso,DC=com

    These incorrect attribute cannot be updated in the database.

    Source of replication is: AddressBookReplication.

    Resolution:

    This is usually caused due to home pool information change in Active Directory using unsupported tools or direct edits to AD. To resolve this condition, move all the affected user back to the original Pool using Move-CsUser and then move the user again to this Pool gracefully using Move-CsUser.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="LS User Replicator" />

        <EventID Qualifiers="33777">30058</EventID>

        <Level>3</Level>

        <Task>1009</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2017-06-14T12:08:57.000000000Z" />

        <EventRecordID>202441</EventRecordID>

        <Channel>Lync Server</Channel>

        <Computer>Sfb.contoso.com</Computer>

        <Security />

      </System>

      <EventData>

        <Data>contoso.com</Data>

        <Data>CN={2c1adcc7-7bb4-4285-a3aa-5b4ab8bbf3ba},CN=Application Contacts,CN=RTC Service,CN=Services,CN=Configuration,DC=contoso,DC=com</Data>

        <Data>AddressBookReplication</Data>

      </EventData>

    </Event>

    Thursday, June 15, 2017 7:13 AM

Answers

  • Finally It worked,...

    it was Simple ... but required guts.

    we used to get some errors in Topology builder regarding some trusted server with tye.... and tls.

    used ADSIedit and deleted those that were providing errors.

    re-published the Topology .. it created the Trusted server  again  without errors and that's it. ;)

    • Marked as answer by Khoj Sahiwala Sunday, June 18, 2017 12:10 PM
    Sunday, June 18, 2017 12:10 PM

All replies

  • Hi Khoj,

    To this issue, please refer to the following steps to renew the local databases, then check if the issue persist:

    1. First backup userData (just in case):
      Export-CsUserData -PoolFQDN <fqdn> -FileName <filename>
    2. Then run the following command on all FEs:
      Stop-CsWindowsServices
      Install-CsDatabase -LocalDatabases -Clean
      Restart-Server 

    Best Regards,
    Jim Xu
    TechNet Community Support


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 16, 2017 9:13 AM
  • Sure , Will do it and let you know.,

    Saturday, June 17, 2017 11:17 AM
  • I am afraid ,, it did not worked.

    it cleaned the resonse grou and we created another fresh one.. but got the same error ,.,, that the contact object uri is not in AD

    Sunday, June 18, 2017 8:53 AM
  • Finally It worked,...

    it was Simple ... but required guts.

    we used to get some errors in Topology builder regarding some trusted server with tye.... and tls.

    used ADSIedit and deleted those that were providing errors.

    re-published the Topology .. it created the Trusted server  again  without errors and that's it. ;)

    • Marked as answer by Khoj Sahiwala Sunday, June 18, 2017 12:10 PM
    Sunday, June 18, 2017 12:10 PM
  • Hi Khoj,

    We are glad to hear this issue has been solved, thanks for your sharing because it will help someone who has similar issue could find solution in this thread as soon as possible.


    Best Regards,
    Jim Xu
    TechNet Community Support


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 20, 2017 6:53 AM