cannot open database xds requested by the login. The login failed.

I was recently deploying a Microsoft Lync Server 2013 Standard Edition pool pair for a customer that was geographically dispersed. During the implementation, which was a migration from Lync Server 2010, I experienced an issue when running step 2 of the deployment wizard following the application of front end resiliency via the Topology Builder. On running the deployment wizard the following error was produced on the front end that was not responsible for holding the CMS.

The “Exception of type Microsoft.Rtc.Management.Deployment.DeploymentException” was being thrown every time I tried to run the deployment wizard, and additionally I noted the file and master replication services has been set to disabled in the services MMC snap-in which further indicated the process had not completed correctly. On further investigation, the Lync Server application event log also produced the following error:

Microsoft Lync Server 2013, Backup Service central management backup module failed to register with back-end database. The module will continuously attempt to reconnect to the back-end. While this condition persists, no backup will be done.

The Connection string: Data Source = (local)\rtc;
Database = xds;
Max Pool Size = 3;
Connection Timeout = 60;
Connection Reset = false;
Enlist = false;
Integrated Security = true;
Pooling = true;
Exception: [2000] Cannot open database “xds” requested by the login. The login failed.
Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’.
Cause: Possible issues with central management backup module back-end database.
Resolution: Ensure central management backup module back-end is functioning correctly.

On reviewing the error and confirming the backup service was started, in order to resolve the issue the following actions were performed.

1. In the Lync Topology Builder remove the front end resiliency settings that were previously applied and publish the topology.

2. Connect to each front end server that comprises the pool pairing and run step two of the deployment wizard, by performing this the replicator and backup services will be removed and essentially the pairing will be broken.

3. In the topology Builder re-apply the resiliency settings and publish the topology in order to recreate the pairing.

4. Connect to each front end server that comprises the pool pairing and run step two of the deployment wizard, by performing this the replicator and backup services will be added again. Once the deployment wizard is completed, ensure the backup services are started on each front end and ensure the Invoke-CSBackupServiceSync PowerShell commands are run as per the “What to do next” information.

5. In the Lync Server Mangement Shell run the “Get-CsBackupServiceStatus -PoolFqdn yourpool.domain.local” and ensure the services is operating in a normal state for both front end servers.

That’s it, the deployment wizard and associated xds database access error should now be cleared.

I recently experienced an issue when configuring an AudioCodes Mediant 1000 MSBG Survivable Branch Appliance for Lync Server 2010. When working through the SBA configuration wizard and getting to the “Backup Replica” stage, this would consistently fail with the following error:

cannot open database xds requested by the login. The login failed. Login failed for user ‘Domain\SBACOMPUTERNAME’

After performing some research on this issue and attempting fixes detailed in other blogs in regards to ensuring the RTCUniversalSBATechnicians Active Directory group was added to the local administrators group on the SBA, I was not having much joy. To work around the problem and get a replica of the CMS database onto the SBA, in order to proceed with the installation, the following was performed.

1. Connect to the server that hold the front end role in your Lync Server 2010 environment.

2. Open the Lync Management Shell and type the following command: Export-CsConfiguration -FileName “C:\Config.zip”

3. Once the command has completed, navigate to the C:\ of the front end server and then copy the generated “Config.zip” file to the root of the SBA’s C:\ drive. This can be acheieved by browsing to the C$ share of the SBA.

4. Once the Config.zip file has been copied to the SBA, make and RDP connection to the appliance and open the Lync Management Shell.

5. Once the Lync Management Shell has loaded, enter the following command: Import-CSConfiguration -Verbose -LocalStore -FileName ‘C:\config.zip”

6. Once the command has completed, a replica of the CMS will have been imported into the SBA. You can confirm if this was successful by opening the Lync Control Panel on your front end server, selecting the topology tab and confirming the SBA object has a green check next to replication. You can now complete the remainder of the SBA setup.

That’s it, the SBA should now work as intended and replicate correctly with the CMS.