The description for Event ID 3 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupt.

Environment Topology:
1 DC/GC and DNS running on Windows Server 2008 R2 with SP1
1 Lync Server 2013 installed on Windows Server 2012
1 Exchange Server 2010 SP3 with RU2
1 Client Windows 8 x64.
1 Office 2013 Lync Client and Office 2013 Basic Lync Client.
1 Certificate Authority and ADFS 2.0 Server
1 Forefront TMG Server 2010 SP2

I am not able to login to Lync 2013 client after the fresh
installation of Lync Server 2013 with CU2. I am getting the error
standard error message “The user name, password, or domain appears to be
incorrect.

Tried with different accounts as well, but still getting the same error message. I found an update for Lync 2013 client and installed it.

After the update, tried Login, still the same error message. Now I enable the logging on the client so that it will generate the event in case of failure. I found the Event ID 3, 1 and 12.

Now as per the event, there’s something wrong with the installation or the files of Lync Client 2013 which got installed. I installed the full version of Office 2013 Lync Client, now I tried with Lync Basic client and it failed with the same error message.

I decided to check the issue with Lync 2010 Client and installed the client after uninstalling the Lync 2013 client from the workstation.
Now I tried to login to the Test account and it worked, no more error with Lync 2010 client.



Resolution/Workaround: Install Lync 2010 client.
I am not sure, why is it failing to login with Lync 2013 client, I am still looking into the issue and will update the post once I find the solution.

Cheers,

About the Author

Gulab Prasad

Technology Consultant & Blogger

MCSE: Exchange Server 2016, 2013
MCSE: Skype for Business Server 2015
MCSE: Azure Productivity
MCSE: Windows Server 2016
MCSA: Windows Server 2012, Office 365
MCITP: Exchange Server 2010-2007 | Lync Server 2010
VMware: vSphere 6 Foundations

5 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *