Home > Lync Server/Skype for Business Server > Lync Rgs error “You are Not a Member of any Group. For Assistance, Contact Your Support Team”

Lync Rgs error “You are Not a Member of any Group. For Assistance, Contact Your Support Team”

While implementing some Response Groups, I noticed that users who went to Tools>Response Group Settings in the Lync client would land at a page that said “You are not a member of any group. For assistance, contact your support team“. The happened for all users of all response groups. It’s critical that users be able to access this page, especially if they are agents of a response group set for a formal participation policy, as this is the page a user goes to to sign into and out of a response group.

I found some info by Drago Totev, who mentioned that some settings in the topology builder file are now case sensitive. The RTM and later versions of Lync require “urn:application:RGS” – notice the case, but some RC versions used lower case. This environment never had RC code in place – migrating from OCS 2007 R2 directly to Lync RTM code. I exported the topology to a .tbxml file anyways, made a copy for backup, and opened it in XML Notepad 2007*, and I searched for and found several instances of “urn:application:Rgs” (see screenshot below). I replaced all four of the instances of the lower case “urn:application:Rgs” with the upper case RGS version.

XML Notepad

XML Notepad

Then I re-imported the file into Topology Builder and published it. Once I verified that replication had completed via Get-CsManagementStoreReplicationStatus, I restarted the Response Group service on my front end servers.

After restarting the Lync client, going to Tools>Response Group Settings now takes the user to the correct page showing the response groups that the user is a member of.

Response Groups

Response Groups


Users now also see the notification in the Lync client notifying them they’ve been added to a Response Group:

Response Group notification

Response Group notification

* Note: Do not use Notepad to edit the topology XML. Doing so can result in system instability.

  1. soder
    February 23rd, 2012 at 22:48 | #1

    Hi Pat,

    I wonder how this can go ever wrong suddenly by itself. If you didnt really do ANYTHING that may have caused it, this should scream for a PSS call.

    Yes I know, its hard to say it with 1000% confidence that “it wasnt one of my recent activities which broke the RGS” until you find out the real cause of this issue. Ususally thats the factory default answer of every IT admin: “No, I didnt make any changes!” But in the end it always turns out, they made SOMETHING that broke the system either directly or -which is much more difficult to investigate- indirectly.

  2. Pat Richard
    February 24th, 2012 at 00:57 | #2

    Actually, the Response Groups that I was configuring were the first in this environment. So it was evidently “broken” from the start.

  3. Markus
    August 3rd, 2016 at 07:56 | #3


    i have this issue with only ONE user. All other users work fine. The value in my topology is correct: urn:application:RGS (with capital letters)
    Any hints?

  1. No trackbacks yet.