Event ID 9153 and Event ID 8213

Hello All,

After reseting our server as a dc, we have been getting hundreds of these exchange errors, namely    MSExchangeSA 9153 and    MSExchangeFBPublish 8213. We were getting FRS errors, namely

Event Type:      Error
Event Source:      NtFrs
Event Category:      None
Event ID:      13559
Date:            4/13/2010
Time:            10:38:50 PM
User:            N/A
Computer:      SERVERMAIN
The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set:
Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.
 [1] At the first poll which will occur in 60 minutes this computer will be deleted from the replica set.
 [2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not.

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

However after follwoing this resolution:

Resolution - - Stopped NTFRS service “net stop ntfrs”
- Modified HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Cumulative Replica sets
- Modified “ BurFlags “ value = D4
- Started ntfrs service “Net start ntfrs”
- Checked Sysvol and Netlogon was shared now using net share.

The server was back up as a domain controller and we began getting these exchange errors, any help would be appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shreedhar EtteCommented:
From eventid.net:
This happened when a domain controller was demoted and it was the primary internal DNS for the Exchange server box. Changing the primary DNS address to another DC resolved the issue.
Wytech_WireAuthor Commented:
A restart of the MS Exchange system attendant seem to resolve this issue, the reference that shreedhar supplied was applied to the system as well as changed Exchange from mixed-mode to native mode. It is hard to determine which if any solutions resolved this issue. I will award partial points to Shreedhar, for the referenced link.
Wytech_WireAuthor Commented:
Although this was applied to the server after the errors occurred, we still received the errors until a restart of the MS system attendant.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.