RDS Clustered Broker Service may meet database error on a Windows Server 2008 R2

Article ID: 2678755 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Windows Server 2008 R2 RDS broker service, if setup as a clustered service, the service may meet database error intermittently.

In application event log, we can see:

Log Name: Application
Source: ESENT
Event ID: 104
Task Category: General
Level: Error
Computer: xxx.x.x
Description: tssdis (7764) The database engine stopped the instance (0) with error (-1090).

After the error is reported, broker service hangs and never recover and the cluster active node is NOT failed over to the other node.

CAUSE

This issue occurs because the broker service impersonate the cluster account when extending the ESE database log files and met access denied error.

WORKAROUND

Important This section contains steps that tell you how to modify the registry. However, serious problems might occur if you modifyhe registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows.

To resolve this issue,

1.  Click Start, click Run, type regedit in the Open box, and then click OK. 
2.  In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TSSDIS\Parameters
3.  Take a note of the folder specified in the WorkingDirectory key. We will use the folder name later in the steps.

Note: Default it is %systemroot%\system32\tssesdir folder.

4. The fix is to add full control permission to the folder we find in step #1. for following accounts:
  • Broker Cluster Name Account
  • Network Services
5. After changing the folder permission, Quit Registry Editor, and then restart the broker service on the server.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2678755 - Last Review: February 24, 2012 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
Keywords: 
KB2678755

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com