Microsoft KB Archive/892372

= After you restore Live Communications Server 2005 from a backup, users cannot connect to Live Communications Server, and event ID 30961 is logged in the Application log =

Article ID: 892372

Article Last Modified on 12/7/2006

-

APPLIES TO


 * Microsoft Office Live Communications Server 2005 Standard Edition

-





SYMPTOMS
Consider the following scenario. You follow the steps in the Live Communications Server 2005 Standard Edition Deployment Guide to back up Microsoft Office Live Communications Server 2005 Standard Edition. Later, you restore the Live Communications Server information by following the steps in the Live Communications Server 2005 Standard Edition Deployment Guide. After you do this, you experience all the following symptoms:  When a user tries to connect to Live Communications Server, he or she receives the following message:

Signing in to SIP Communications Service failed because the service is temporarily unavailable. Please try again later.

 If you try to view the properties of a user account by using the Live Communications Server 2005 Microsoft Management Console (MMC) snap-in, you receive the following error message:

MMC snap-in failed to read one or more propery from WMI. If this is a new user then it may not have been picked up the User Replicator yet. Please try again a few moments later.

Note In this error message, the word &quot;property&quot; is misspelled as &quot;propery.&quot; Additionally, the word &quot;by&quot; is missing between &quot;picked up&quot; and &quot;the User Replicator.&quot;  The following event is logged in the Application log on the Live Communications Server 2005 computer: Event Source: Live Communications User Services

Event Category: (1006)

Event ID: 30961

Date:

Time:

Type: Error

User: N/A

Computer:

Description: Failed to connect to backend database. Live Communications Server will continuously attempt to reconnect to the backend. While this condition persists, incoming messages will receive error responses.

Backend Server: (local)\rtc Database: rtc Connection string of:

driver={SQL Server};Trusted_Connection=yes;AutoTranslate=no;server=(local)\rtc;database=rtc;network=dbmslpcn;

Cause: Possible issues with backend database.

Resolution:

Ensure the backend is functioning correctly.

For more information, see Help and Support Center at

http://support.microsoft.com. 



CAUSE
This problem occurs if the Live Communications Server local groups are not mapped to the serveracct database role, the adminacct database role, and the roacct database role. This problem occurs because the reinstallation of Live Communications Server re-creates the Live Communications Server local groups. Therefore, when you restore the Microsoft SQL Server database information after you reinstall Live Communications Server 2005, the database permissions for the Live Communications Server local groups are not restored. Live Communications Server cannot connect to the database because the local groups do not have rights to the serveracct database role, the adminacct database role, and the roacct database role.



RESOLUTION
To resolve this problem, map the Live Communications Server local groups to the serveracct database role, the adminacct database role, and the roacct database role. To do this, follow these steps:  Insert the Live Communications Server CD into the CD drive or the DVD drive. Click Start, click Run, type cmd, and then click OK.</li> At the command prompt, type the following command, and then press ENTER:

cscript  \setup\i386\DBsetup\dbsetup.wsf /setsecurity /serveracct:&quot; \RTC Server Local Group&quot; /adminacct:&quot; \RTC Local User Administrators&quot; /roacct:&quot; \RTC ABS Service Local Group&quot;

Note In this command, replace the placeholders as follows:  Replace  with the letter of the drive that contains the Live Communications Server CD.</li> Replace  with the name of the Live Communications Server computer.</li></ul>

The following results are returned:

<pre class="fixed_text">Connecting to SQL Server on \rtc Successfully added account(s) to the specified database role(s).

Note The Dbsetup.wsf script is also located in the C:\Program Files\Common Files\Microsoft LC 2005\DBSetup\ folder.</li> Quit the command prompt.</li></ol>

Note You do not have to restart the Live Communications Server service after you follow these steps.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
After you restore the Live Communications Server database by using the Dbbackup command, you must manually restart the Live Communications Server service. The Dbbackup restore operation stops the Live Communications Server service, but does not restart the Live Communications Server service.

To obtain Live Communications Server 2005 deployment resources and other guides, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/products/FX011526591033.aspx

Additional query words: LCS LCS 2005 Livecom Livecomm chat RTC

Keywords: kbpending kbbug kbtshoot kbprb KB892372

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.