Microsoft Lync 2013 and the MSSQL 18456 Event

November 26, 2013   //   Unified Communications, , , ,

Have you recently encountered the MSSQL 18456 Event? I’ve seen this come up in quite a few migrations after Microsoft Lync 2013 is installed and pools are paired. Since I couldn’t find much about MSSQL 18456 on the internet, I thought I would share my findings for everyone else who has experienced an endless number of MSSQL 18456 information events.

Once you encounter the MSSQL 18456 information event, fill the application event log with the message: “Login failed for user ‘DOMAINSQLSERVERNAME$’. Reason: Failed to open the explicitly specified database ‘xds’. [CLIENT: IP Address]”. This issue can occur if the Lync 2013 pools were set up and paired first, and the CMS moved later to one of the pools. If you see the message above related to your backup pool, the simplest thing you can do is remove the pairing from the topology, publish, then reestablish the pairing and republish. Another alternative is to create the database via the PowerShell using this command: Install-CsDatabase -CentralManagementDatabase -SQLServerFQDN-SQLInstanceName.

If you’d like assistance planning your path to Microsoft Unified Communications please contact SWC, connect with Anthony Caragol on LinkedIn or join us for our next Unified Communications event.

To learn more about Microsoft Lync, check out a few of Anthony’s technical blogs:

Microsoft Unified Communications: A Software Solution
Let Microsoft Lync Sweat The Small Stuff
Using Microsoft Lync As A Phone System
Microsoft Exchange, An Enterprise Ready Voicemail Solution
Using Microsoft Exchange As A Voicemail Platform
The End of Threat Management Gateway from a Unified Communications Perspective
We’re One Step Closer to Exchange 2013