Microsoft Knowledge Base Email Alertz

You receive DFSR event ID 2212, and DFSR stops after you restart Windows Server 2008

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 977518 - Last Review: November 20, 2009 - Revision: 1.1

You receive DFSR event ID 2212 after you restart the DFSR service in Windows Server 2008

SYMPTOMS

When you restart the Distributed File System Replication (DFSR) service on a server that is running Windows Server 2008, or you restart the server, the following event may be logged in the DFS Replication log:
Log Name: DFS Replication
Source: DFSR
Event ID: 2212
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MyDfsrMember.contoso.com
Description:
The DFS Replication service has detected an unexpected shutdown on volume Drive_Letter. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process. The service will rebuild the database if it determines it cannot reliably recover. No user action is required.
After some time has passed, DFSR logs event ID 2214. This event indicates that the database recovery process has finished. During database recovery, replication performance is slowed.

CAUSE

This issue occurs because the Service Control Manager (SCM) uses the default time-out value of 20 seconds for stopping a service. In some complex DFSR implementations, this time-out value may be too short, and DFSR stops before the appropriate database is closed. At service restart, DFSR detects this condition and performs the database recovery.

RESOLUTION

To resolve this issue, you can change the default time-out value that is used by the SCM by adding the following registry value:

Value Name WaitToKillServiceTimeout
Data Type REG_SZ
String 20000 milliseconds (default value)

To specify the wait time, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
  3. On the Edit menu, point to New, and then click String Value.
  4. Type WaitToKillServiceTimeout, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Type 60000, and then click OK.
  7. Exit Registry Editor.
  8. Restart the server.
If the time interval is something other than 60 seconds, you can set the value of the WaitToKillServiceTimeout registry value to the difference in time, in milliseconds, between the following two events in the DFSR event log:
  • 1006 - The DFS Replication service is stopping.
  • 1008 - The DFS Replication service has stopped.

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
146092  (http://kbalertz.com/Feedback.aspx?kbNumber=146092/ ) How to Increase shutdown time for services to close properly

APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
Keywords: 
kbtshoot kbexpertiseinter kbsurveynew kbprb KB977518
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate