Select the product you need help with

Office Communications Server or Lync Server 2010 Front End Services fail after backend database move

Article ID: 968100 - View products that this article applies to.

SYMPTOMS

This problem occurs if one or more of the following conditions are true:

You use the SQL Server Management Studio to move the Office Communications Server or Lync Server 2010 backend databases to a new SQL
Server instance
You update the Office Communications Server or Lync Server 2010 front end server pool to point to the new SQL Server instance that
hosts the backend databases

The following Warning event will be logged in the Lync Server 2010 Event log:

Log Name: Lync Server
Source: LS User Services
Date: mm/dd/yyyy hh:mm:ss AM|PM
Event ID: 32118
Task Category: (1006)
Level: Warning
Keywords: Classic
User: N/A
Computer: server01.contoso.com
Description:
SQL server cross database chaining option is disabled for either rtc or rtcdyn database. This may be caused by attaching or restoring
an existing database. Since this condition causes performance issues, database will not be acquired until the issue is resolved.

Back-end Server: server01.contoso.com\lync Database: rtc Connection string of:
driver={SQL Server Native Client 10.0};Trusted_Connection=yes;AutoTranslate=no;server=server01.contoso.com\lync;database=rtc;
Cause: Check the eventlog description.

Resolution:
Please enable cross database chaining option (using "sp_dboption '<dbname>', 'db chaining', TRUE") for both rtc and rtcdyn databases.
Once this is done, Service will automatically reconnect to the backend.

The following Error event will be logged in the Office Communications Server Event log:

Log Name: Communications Server
Source: OCS Server
Date: mm/dd/yyyy hh:mm:ss AM|PM
Event ID: 12304
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Computer: server01.contoso.com

Description:
The component Live Communications User Services (application: Default) reported a critical error: code C3EE7D3D (SQL server cross database chaining option is disabled for either rtc or rtcdyn database. This may be caused by attaching or restoring an existing database. Since this condition causes performance issues, service will be stopped and will not start until the problem is resolved.

The following error will be displayed by Office Communications Server:

Windows could not start the Office Communications Server Front-End on Local Computer. For more information review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service specific error code -1007780547

Back to the top | Give Feedback

CAUSE

This problem occurs if the cross-database chaining option has been disabled for the RTC database and for the RTCDyn database. The cross-database chaining option must always be enabled. However, this option is disabled when you detach and then reattach the databases.

Back to the top | Give Feedback

RESOLUTION

To resolve this problem, follow these steps to enable cross-database ownership chaining for the RTC database and for the RTCdyn database:

On a computer that is running Microsoft SQL Server, connect to the RTC database, and then run the following SQL command from SQL Server Management Studio:
"sp_dboption rtc, 'db chaining', TRUE"
Connect to the RTCdyn database, and then run the following SQL command from SQL Server Management Studio:
"sp_dboption rtcdyn, 'db chaining', TRUE"
Start the Front End services.

Back to the top | Give Feedback