Friday, October 1, 2010

Lync Server 2010 (RC) (Replication Issues)

clip_image002#lync #XDS Since two weeks now we are running Microsoft Lync Server 2010 (RC) in our demo environment. The entire install went smooth but after installing all the different components we ran into a issue which was hard to tackle. Good time to give you some insights. Our environment: we setup a Windows Server 2008 R2 DC + CA and setup a Microsoft Lync Server 2010 (RC) on a separate box connected in a private network. After installing the Microsoft Lync 2010 (RC) imageon the DC and installing the Lync 2010 (RC) on the Lync Server itself we were unable to sign in (see the printscreen in the first line). The fist thought came up in my mind was incorrect DNS entries. After checking that, that was ok. After that we went to the LSCP (Lync Server Control Panel) and checked if our users where provisioned correctly. We also checked the service state of our running components. All went up “green”. Also Mina Nagy suggestion did not work to change the domain name in a domain FQDN. 

If you would to know which users are provisioned you can do this by Powershell (LSMS) btw. To do this go start Lync Server Management Shell (LSMS) and type: get-csuser. After that you will see the entire list in your organization of SIP enabled users. After resetting the password multiple times and restarting the Lync 2010 (RC) client multiple times something changed in the logon procedure. We got a login prompt in the Lync 2010 (RC) client!  That really suggest that the user was there.


After setting up logging in the Lync 2010 (RC) client some interesting records showed up:

1. SIP/2.0 404 Not Found ms-diagnostics: 1003;reason="User does not exist";TargetUri="";source=""

2. SIP/2.0 401 Unauthorized (no specific ms-diagnostic message).

This information gives me the direction that maybe something with the XDS replication went wrong. Lets go back to the LSMS and put in the following commando (Get-CsManagementStoreReplicationStatus) PS C:\Users\administrator.DEMO-LS> Get CsManagementStoreReplicationStatus

UpToDate           : False (well there is it!)
ReplicaFqdn        :
LastStatusReport   :
LastUpdateCreation : 9/23/2010 2:39:25 PM
ProductVersion     : <empty>

The registrar is looking local for the User and can’t find it since replication has failed and most likely never populated the users from CMS. After setting up a trace with the LSLT (Lync Server Logging Tool) I monitored on XDS and then issue the Invoke-csManagementStoreReplication command in LSMS to find out what is going on. (here some lines from my extraction). On the specific share we got a access denied.

TL_ERROR (TF_COMPONENT) XDS_Master_Replicator (MasterReplicationAgent.QueryChang
esImpl:masterreplicationagent.cs(724))  [0]047C.04C0::09/23/2010-21:02:27.769.00
    Query changes operation failed. Exception [System.UnauthorizedAccessExceptio
n: Access to the path '\\demo-ls-ls\LyncShare\1-CentralMgmt-1\CMSFileStore\xds
-master\working\replication\tmp\e0285292-b325-4e06-aa74-97b32d2d0373' is denied.

We went back to the LSTB (Lync Server Topology Builder) and changed the specific share and re-populated the folder tree. Still no status change while logging in with Lync 2010 (RC). I was really smacking my head to the wall. After some nice conversations with Microsoft (thanks Geoff Clark) we re-installed the Lync Server System Components again from the Lync Server Deployment Wizard (LSDW). Back to LSMS:PS C:\Users\administrator.DEMO-LS> Get-CsManagementStoreReplicationStatus

UpToDate           : True
ReplicaFqdn        :
LastStatusReport   : 10/1/2010 11:16:40 AM
LastUpdateCreation : 10/1/2010 11:16:35 AM
ProductVersion     : 4.0.7457.0

This blogpost is possible a little bit scrambled for you but it really helps to understand how Microsoft Lync Server 2010 (RC) works and how you troubleshoot Lync. To be honest I really don’t no why the initial share I created during the install was not created correctly. If you have any questions feel free to contact me. After taking all these steps the environment is working perfectly.

No comments: