When something went wrong during any Lync Installation, e.g. Topology was published with Errors and you tried to install a Lync Server, e.g. SBS, STD Edt, ...
You might see the following Error:
Cannot open database "xds" requested by the login.
The login failed.Login failed for user DOMAIN\ADMINUSER
If this is happened,
you fully need to uninstall:
1.) All Lync Server Components, beside:
- Administrative Tools, Core Components, Resources Kit (if ist installed)
2.) The entire local SQL Instance, including Client Tools !
- Ensure, also the local Folder: C:\Program Files\Microsoft SQL Server\MSSQL10.RTCLOCAL is entirely deleted!
3.) Restart your Server now.
If you are now going to reinstall Lync Server,
4.) make sure the Registry Key is clean:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
PendingFileRenameOperations
NOTE:
should the Lync Server Replica Replicator Agent should not have been proper uninstalled.
You Need to uninstall all Lync components including the exemptions listed above.
(RegKey: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\REPLICA)
The Replica Replicator Service is part from Lync Core Components!
and delete the following Folder:
C:\Program Files\Microsoft Lync Server
C:\Program Files\Common Files\Microsoft Lync Server 2010
Here you go and the Server can be reinstalled...!
Author: Thomas Pött Managing Consultant Microsoft UC
Information, Configuration and Advice for Microsoft Unified Communication. As a Managing Consultant @ACP IT Solutions AG, my specialties are in Unified Communication (LYNC), Messaging (EXCHANGE) and Dynamic Datacenter (HYPER-V, System Center). After launching my expertise with Microsoft Mail, I experienced Exchange 2000 Conferencing and now focus on Lync 2013, since the Lync TAP Program was released. Microsoft awarded me the MVP Lync Status for my professional work and community support.
Subscribe to:
Post Comments (Atom)
Thanks for explanation, it is pretty much simple.
ReplyDeleteThanks, we had to do this today. Lync 2013 FE Enterprise install with SQL 2008 R2 latest SP back end. Hope Microsoft will look into these repeated failures -- lots of people finding the same issue it seems.
ReplyDelete