Group Chat–Unable to Add a User

I had a few users that are unable to join Lync 2010 Group Chat rooms after being re-hired. They had their accounts disabled, and then after being re-hired, they had new accounts created. After a great deal of research and testing, I found two scenarios and two solutions. The second scenario and solution seems to be the most likely.

Scenario #1:

  1. Add user to a room, and click apply. The name appears, but it disappears if you refresh the screen.
  2. Try to add the user to the room again, and you get an error message similar to this one:

Unable to save the memberlist:[3][322] Role <Member> for <ma-chan://DomainName.com/622cf214-de21-48f0-9f0d-80e096da67d1> already contains <These principals are already defined on the node: <sip:UserName@DomainName.com>>

  1. You can add the user to a different room, and it works fine.

The solution is to use the following steps:

1. Get the User information by running this SQL command.

SELECT *

     FROM [GroupChatDB].[dbo].[tblPrincipal]

     WHERE prinEmail=’mother.goose@infrastructurehelp.com’

Document the prinID, which will be a number. This number will be used in step 3 as the prinRolePrinID.

2. Get the Group Chat room information by running this SQL command.

SELECT *

     FROM [GroupChatDB].[dbo].[tblNode]

     WHERE nodeName=’NameOfChatRoom’

Document the nodeID, which will be a number. This number will be used in step 3 as the prinRoleNodeID.

3. Remove the association between the user and the room by running this SQL command.

DELETE FROM [GroupChatDB].[dbo].[tblPrincipalRole]

     WHERE prinRoleNodeID=14 and prinRolePrinID=21290

Scenario #2:

  1. Add user to a room, and click apply. The name appears, but it disappears if you refresh the screen.
  2. Try to add the user to the room again, and you get the error message:

Unable to save the memberlist:[3][322] Role <Member> for <ma-chan://DomainName.com/622cf214-de21-48f0-9f0d-80e096da67d1> already contains <These principals are already defined on the node: <sip:UserName@DomainName.com>>

Suspected Cause:

The user account was deleted, but the user came back to the company with the same name, same email address, and same SIP address. The Group Chat database basically sees that the user already exists and doesn’t like the new user account. Yes, I dumbed that down for me. 🙂

The solution is to use the following steps:

1. Get the User information by running this SQL command.

SELECT *

     FROM [GroupChatDB].[dbo].[tblPrincipal]

     WHERE prinEmail=’mother.goose@infrastructurehelp.com’

Document the prinUri which will be ‘sip:mother.goose@infrastructurehelp.com’

Document the prinEmail which will be ‘mother.goose@infrastructurehelp.com’

Document the prinADPath which will be the DN, i.e. ‘CN=Goose\, Mother,OU=People,DC=infrastructurehelp,DC=com’ IT WILL PROBABLY BE NULL

Document the prinDisabled which will be either 1 or 0, if it is 1, then the account needs to be enabled by changing it to 0.

2. Update the User’s Distinguished Name (DN) by running this SQL command.

UPDATE [GroupChatDB].[dbo].[tblPrincipal]

      SET prinADPath=’CN=Goose\, Mother,OU=People,DC=infrastructurehelp,DC=com’

     WHERE prinURI=’sip:mother.goose@infrastructurehelp.com’

3. Enable the account in Group Chat by running this SQL command.

UPDATE [GroupChatDB].[dbo].[tblPrincipal]

     SET prinDisabled=’0′

     WHERE prinUri=’sip:mother.goose@infrastructurehelp.com’

4. Update the User’s Email Address by running this SQL command (if needed).

UPDATE [GroupChatDB].[dbo].[tblPrincipal]

     SET prinEmail=’mother.goose@infrastructurehelp.com’

     WHERE prinUri=’sip:mother.goose@infrastructurehelp.com’

This is one situation where I just couldn’t find good information on how to fix the issue. I knew that it had to be fixed within the database, but I could not figure out how to fix the issue without having to try several different solutions.

Advertisements
This entry was posted in Lync. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s