Category Archives: Lync Server

Fix: Lync fails to connect with Exchange for calendar

On Exchange servers with Lync, when using Lync from outside the site using Lync Edge, you might have the problem that it works in case of instant messaging, but it will not connect to your Exchange setup to get the calendar or in some cases it will keep re-asking your credentials with no success.

This might be an issue of authentication which can easily be solved by changing the authentication method on the AutoDiscover folder on IIS.

Log into the Exchange server
Open IIS Manager
Expand the [Server Name]/Sites/Default Website
Click on AutoDiscover application
Click on Authentication
Right-Click on Digest Authentication and select Enable

(1363)

How to: Upgrade Lync server from evaluation to full

When you are evaluating the Lync server and you want to upgrade or install the full version, you can do it easily without re-installing or reconfigure the service. You can also upgrade when your evaluation has expired.

If your evaluation has expired, you will notice that you Lync Front-End Server doesn’t start and you will see the Windows could not start the Lync Server Front-End on local computer error showing. To confirm this, you must go on the Lync Server section on the Event Viewer and see that it is complaining about the license as below.

The evaluation period for Microsoft Lync Server 2010 has expired. Please upgrade from the evaluation version to the fully licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Cause: The evaluation period for Microsoft Lync Server 2010 has expired.

To upgrade to the full version you need to download the setup in your server. Then open the Lync Management Shell and enter the below.

Get-CsServerVersion (This will show the current version of the system)

Browse to the location of the installation of the full version example C:\LyncFull\Setup\AMD64\Setup and run the below command.

msiexec.exe /fvomus server.msi EVALTOFULL=1 /qb
Enable-CsComputer

Once ready enter again the Get-CSServerVersion to verify that the version has been updated.

Note: This must be done on all servers of Lync i.e. Director, Front-End and Edge

(1722)

Fix: Command execution failed: The supplied handle is invalid on Lync 2010 Edge

When deploying a Lync Edge setup and during the ‘Setup or Remove Lync Server Components’ you might get the error:

Command execution failed: The supplied handle is invalid. This can happen when trying to set an ACL on an anonymous kernel object.

This could be because the name of the computer/server exceed the 15 characters since the setup uses the NETBIOS name rather than the FQDN. To fix this, change the computer name to less or equal to 15 characters. Then you have reconfigure Lync Edge server by doing the below:

– Change computer name to less or equal to 15 characters and restart
– Remove any installed application on the Edge server
– On the Front-End Server open the Topology builder
– Remove the Edge Pool for media from the Standard or Enterprise Front End node
– Remove the Edge Pool you created under the Edge Pool node
– Publish Topology
– Re-Export the configuration with Export-csconfiguration –filename c:\topology_export.zip
– Copy topology_export.zip on Edge server
– Re-start Setup

That should fix the issue

(8227)

How to: Clean User’s Active Directory Schema from previous Lync installation

Sometimes when you install a Lync setup and change the server, you might have problems when adding the clients back to the newly created server. Some issues might be that that you cannot log in or mostly you get an error on the management panel on Lync when you enable a user as below:

"RegistrarPool" with identity "1234567890" assigned to "sip:sysadmin@noelpulis.com" has been removed from the configuration store.

You may also encounter the error,

Cannot move user in enable operation. Use the Move user cmdlet instead

To cleanup the user you will need to edit the Active Directory schema. Open the ADSI Edit from your domain controller. Connect as the Default naming context, find the user you need to change (in this case sysadmin) and select properties. Change the below properties to either blank or .

msRTCSIP-ArchivingEnabled
msRTCSIP-FederationEnabled
msRTCSIP-InternetAccessEnabled
msRTCSIP-OptionFlags
msRTCSIP-PrimaryHomeServer
msRTCSIP-PrimaryUserAddress
msRTCSIP-UserEnabled
msRTCSIP-UserPolicies

After you set the below, exit the ADSI Edit and retry on Lync. The user should be able to work.

(3823)

Fix: Insufficient Access Rights on Lync when adding new user

When adding a new Lync enabled user in the Lync Control Panel, you may have the following error message.

Active Directory operation failed on “DC01.MYDOMAIN.COM". You cannot retry this operation: “Insufficient access rights to perform the operation 00002098, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0″.

This is due to permissions on the Active Directory. Although you may have full Entrprise access, you will still fail to add new users. This can be fixes by below.

Open Active Directory Users and Computers
Click View and Selct Advanced Features
Right Click and select Properties on the users that you cannot add to Lync
Select Security and click Advanced.
Tick Include inheritable permissions from this object’s parent
Click OK and Click OK

Try to add the user again… ClickApu, it works.

(9675)

Fix: Cannot open database when publishing topology on Lync

When setting up the topology using the topology builder on the Lync server, you may get the below error.

Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Cannot open database "xds" requested by the login. The login failed.
Login failed for user 'MYDOMAIN\Administrator'."

Although your credentials are correct, the issue is a known bug if you are using Microsoft SQL 2008 R2. This may be fixed by installing the Microsoft SQL 2008 R2 SP 2.

Another option would also be to check the user in the error as it must have sysadmin role in the SQL server security.

Also you might need to check if you have the installed SQL Server Backward Compatibility. This is a requirment.

(4926)