Use the Burlaps.. I mean BurFlags

On December 30, 2007, in news, by

I was having a message indicating I had journal wrap errors.  When I did the edit for journal wrap errors, it got me into worse errors.


I had Userenv errors and dcdiag that indicated that it was not a happy camper…




Not good.  What I should have done what the BurFlags edit


http://support.microsoft.com/kb/290762


Authoritative FRS restore



loadTOCNode(3, ‘notice’);
Use authoritative restores only as a final option, such as in the case of directory collisions.

For example, you may require an authoritative restore if you must recover an FRS replica set where replication has completely stopped and requires a rebuild from scratch.

The following list of requirements must be met when before you perform an authoritative FRS restore:














1. The FRS service must be disabled on all downstream partners (direct and transitive) for the reinitialized replica sets before you restart the FRS service when the authoritative restore has been configured to occur.
2. Events 13553 and 13516 have been logged in the FRS event log. These events indicate that the membership to the replica set has been established on the computer that is configured for the authoritative restore.
3. The computer that is configured for the authoritative restore is configured to be authoritative for all the data that you want to replicate to replica set members. This is not the case if you are performing a join on an empty directory. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
266679 (http://support.microsoft.com/kb/266679/) Pre-staging the File Replication service replicated files on SYSVOL and Distributed file system shares for optimal synchronization
4. All other partners in the replica set must be reinitialized with a nonauthoritative restore.
To complete an authoritative restore, stop the FRS service, configure the BurFlags registry key, and then restart the FRS service. To do so:


































1. Click Start, and then click Run.
2. In the Open box, type cmd and then press ENTER.
3. In the Command box, type net stop ntfrs.
4. Click Start, and then click Run.
5. In the Open box, type regedit and then press ENTER.
6. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
7. In the right pane, double click BurFlags.
8. In the Edit DWORD Value dialog box, type D4 and then click OK.
9. Quit Registry Editor, and then switch to the Command box.
10. In the Command box, type net start ntfrs.
11. Quit the Command box.
When the FRS service is restarted, the following actions occur:
















The value for the BurFlags registry key is set back to 0.
An event 13566 is logged to signal that an authoritative restore is started.
Files in the reinitialized FRS replicated directories remain unchanged and become authoritative on direct replication. Additionally, the files become indirect replication partners through transitive replication.
The FRS database is rebuilt based on current file inventory.
When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.


Yup ..it sure did…….


Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13516
Date:  12/29/2007
Time:  10:54:28 PM
User:  N/A
Computer: KIKIBITZFINAL
Description:
The File Replication Service is no longer preventing the computer KIKIBITZFINAL from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
 
Type “net share” to check for the SYSVOL share.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


And now when I do DCDiag….


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.


C:\Documents and Settings\Administrator.KIKIBITZRTM>dcdiag


Domain Controller Diagnosis


Performing initial setup:
   Done gathering initial info.


Doing initial required tests


   Testing server: Default-First-Site-Name\KIKIBITZFINAL
      Starting test: Connectivity
         ……………………. KIKIBITZFINAL passed test Connectivity


Doing primary tests


   Testing server: Default-First-Site-Name\KIKIBITZFINAL
      Starting test: Replications
         ……………………. KIKIBITZFINAL passed test Replications
      Starting test: NCSecDesc
         ……………………. KIKIBITZFINAL passed test NCSecDesc
      Starting test: NetLogons
         ……………………. KIKIBITZFINAL passed test NetLogons
      Starting test: Advertising
         ……………………. KIKIBITZFINAL passed test Advertising
      Starting test: KnowsOfRoleHolders
         ……………………. KIKIBITZFINAL passed test KnowsOfRoleHolders
      Starting test: RidManager
         ……………………. KIKIBITZFINAL passed test RidManager
      Starting test: MachineAccount
         ……………………. KIKIBITZFINAL passed test MachineAccount
      Starting test: Services
            IsmServ Service is stopped on [KIKIBITZFINAL]
         ……………………. KIKIBITZFINAL failed test Services
      Starting test: ObjectsReplicated
         ……………………. KIKIBITZFINAL passed test ObjectsReplicated
      Starting test: frssysvol
         ……………………. KIKIBITZFINAL passed test frssysvol
      Starting test: frsevent
         ……………………. KIKIBITZFINAL passed test frsevent
      Starting test: kccevent
         ……………………. KIKIBITZFINAL passed test kccevent
      Starting test: systemlog
         ……………………. KIKIBITZFINAL passed test systemlog
      Starting test: VerifyReferences
         ……………………. KIKIBITZFINAL passed test VerifyReferences


   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ……………………. ForestDnsZones passed test CrossRefValidation


      Starting test: CheckSDRefDom
         ……………………. ForestDnsZones passed test CheckSDRefDom


   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ……………………. DomainDnsZones passed test CrossRefValidation


      Starting test: CheckSDRefDom
         ……………………. DomainDnsZones passed test CheckSDRefDom


   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ……………………. Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ……………………. Schema passed test CheckSDRefDom


   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ……………………. Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ……………………. Configuration passed test CheckSDRefDom


   Running partition tests on : Kikibitzrtm
      Starting test: CrossRefValidation
         ……………………. Kikibitzrtm passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ……………………. Kikibitzrtm passed test CheckSDRefDom


   Running enterprise tests on : Kikibitzrtm.local
      Starting test: Intersite
         ……………………. Kikibitzrtm.local passed test Intersite
      Starting test: FsmoCheck
         ……………………. Kikibitzrtm.local passed test FsmoCheck


C:\Documents and Settings\Administrator.KIKIBITZRTM>


A much much happier camper…


P.S.  …what does BurFlags get it’s name from anyway?

 

One Response to Use the Burlaps.. I mean BurFlags

  1. Chris Knight says:

    Back Up / Restore Flags?