Quantcast
Channel: Lync Server 2013 - Management, Planning, and Deployment forum
Viewing all articles
Browse latest Browse all 5984

Few Lync 2013 users are unable to sign-in

$
0
0

I have an issue, where few users are unable to sign-in. This has specifically to do with the users who returned after long leave. And in our company the users who go for longleave the account gets disabled. Once they return, the User account is enabled back again. When they try to sign-in, they get an error incorrect credentials. 

We have Lync 2013 and 2010 in environment. All users are in Lync 2013. When we move users to Lync 2010, after some time the users would be able to sign-in. But once they are moved back to 2013, the issue turns up.

I get the following event in Lync FE Server:

Log Name:      Lync Server
Source:        LS User Replicator
Date:          <Date>
Event ID:      30020
Task Category: (1009)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <FE SERVER NAME>
Description:
A user URI is already being used by another valid user in the database. Resolve the conflict by using a URI that isn't already taken, or deleting one of the users from AD.

URI:
sip:<User sip address>
The DN of the user whose URI User Replicator tried to replicate is:
<DN of the user>
This update came from domain:
Lync Server Domain name 
The source of the replication is LocalRegistrarReplication.

Cause: Typically caused by having multiple user or contact objects in AD with identical msRTCSIP-PrimaryUserAddress attribute values.
Resolution:
Use a URI that isn't already taken, or delete one of the offending users. You may use Dbanalyze to diagnose the problem.

Furher which when I run the command: get-csclientcertificate, I get the following error:

User "SIP Address" is not validly homed on target <Server Pool Name>.

Need Help.



Viewing all articles
Browse latest Browse all 5984

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>