Operations Master Replication Issue Event ID 13562

  • Thread starter Thread starter bramblewood
  • Start date Start date
B

bramblewood

I have a Windows 2000 Server which is the Operations Master for the domain.
This server and others are having problems with replication.



This Operations Master server has an event ID 13562

Following is the summary of warnings and errors encountered by File
Replication Service while polling the Domain Controller
morecambe.screen-finance.com for FRS replica set configuration information.

Could not find computer object for this computer. Will try again at next
polling cycle.

I have run a DCDIAG from one of the other servers and get a failed test on

KnowOf RolesHolders as follows:

Starting test: KnowsOfRoleHolders
Warning: CN=NTDS
Settings\0ADEL:f145dbfc-1ec1-4098-94e4-5e97bad60bc1,CN=MORECAMBE,CN=Servers,CN=2ndFloorLeatherheadHouse,CN=Sites,CN=Configuration,DC=screen-finance,DC=com
is the Domain Owner, but is deleted.......................... REEVES failed
test KnowsOfRoleHolders

If I try and change the role via Domains and Trusts 'Change Operations
Master', I get the error message

"The transfer of the operations master role cannot be performed because the
requested FSMO operation failed. The current FSMO holder could not be
contacted.

I really do not want to seize the role because I need to keep this server in
the domain. Can I use ADSI Editor? Does anyone have any ideas on how to fix?

Thanks
 
Have you had problems with this machine before where you lost it and just
rebuilt it without doing any type of metadata cleanup? It sounds like this
one possibilty for you to have gotten in ths position.

Check out this link and see if there is any help in it.
http://support.microsoft.com/default.aspx?scid=kb;en-us;312862

How about trying a dcpromo to remove the dc as a dc? Removing it from the
domain, rename the server, seize the roles and then rejoin the domain and
dcpromo it?

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hello,

Thank you for posting.

From your post, my understanding of this issue is: The FRS replica fails
with Event ID 13562, and you cannot transfer the FSMO to another server.
If this is not correct, please feel free to let me know.

First, I appreciate Paul's kind inputs. He has provided useful information
for us, and I do agree with him.

From the error messages, it seems that the DC object has been deleted from
the domain. It could be caused by many factors, and the troubleshooting
process may be somewhat time-consuming. Based on my knowledge, the more
efficient method to resolve this issue is that we first use NTDSutil.exe to
seize the FSMO roles to other domain controller and then refer to KB312862
to troubleshoot the FRS problem, and then forcefully demote and then
promote the problematic DC.

312862: Recovering missing FRS objects and FRS attributes in Active
Directory
http://support.microsoft.com/?id=312862

By following this method, I believe the problem should be resolved more
efficiently. If anything is unclear or you have any concerns, please feel
free to post back, and I will do my best to be of assistance. I look
forward to your update.

Have a nice day!

Steven Wang (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
 
Thanks you for you input. I just have some concerns using NTDSUTIL to seize
role as follows:

Current FSMO roles

FSMO Role Server OS

PDC Emulator WISE Windows 2000
SP4 Domain Controller

Infrastructure Master WISE Windows 2000 SP4
Domain Controller

Relative ID (RID) WISE " " "

Schema Master WISE " " "

Domain Naming Master MORECAMBE Windows 2000 SP4 Domain
Controller

Other Servers

HARDY
Windows 2003 SP1

REEVES
Windows 2003 SP1 Domain Controller

The problem is with the Domain Naming Master. This server is running SQL and
an important system. What I have read about NTDSUTIL and seizing roles is
that the domain controller which has its role seized needs to come off the
network and re-install operating system which is rather drastic!

If I'm reading your reply correctly, can I seize the role from another
server. Then on the MORECAMBE server, demote using DCPROMO, do a metabase
cleanup and then make the MORECAMBE server a domain controller again using
DCPROMO. Should I need to do anything else? Would any applications and this
server be effected?

Kind Regards

Phil
 
If you take the server out of the domain and put it back in the sid will
change, this will help with preventing any problems with the clash on the
replication, but as a sql server you may have user domain credentials
supplied. This could create major problems for you.

I think you should consider demoting and finding a new server to be a dc.
Although you can use a dc for other purposes, as you can see, it is best to
segregate dc from other services.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
This posting is provided "AS IS" with no warranties, and confers no rights.
 
We are about to do this work and need to clarfy something.

If we force role to another DC and demote the old role server from a DC and
leave it as a member server, will this be ok?

Many Thanks
Phil
 
If you seize the RID, Schema or Domain Naming master roles you must never
bring the original online. If the original role holder is online, you
should transfer these roles. If it offline, or unavailable, you should
seize the roles and metadata cleanup the old system.
 
Let me get this right...Are you saying that the DC that has the Domain
Naming Role which is currently online, I then Seize the role, then demote it
from a DC, I still have to keep it offline? Are you saying that the old
Domain Naming Server which demotes from DC an is still online as a member
server, would have to be taken offline, and Operating System rebuild whith a
different name for the server?

Regards,

Phil
 
I have a Windows 2000 Server which is the Operations Master
for the domain.
This server and others are having problems with replication.



This Operations Master server has an event ID 13562

Following is the summary of warnings and errors encountered by
File
Replication Service while polling the Domain Controller
morecambe.screen-finance.com for FRS replica set configuration
information.

Could not find computer object for this computer. Will try
again at next
polling cycle.

I have run a DCDIAG from one of the other servers and get a
failed test on

KnowOf RolesHolders as follows:

Starting test: KnowsOfRoleHolders
Warning: CN=NTDS
Settings\0ADEL:f145dbfc-1ec1-4098-94e4-5e97bad60bc1,CN=MORECAM
BE,CN=Servers,CN=2ndFloorLeatherheadHouse,CN=Sites,CN=Configur
ation,DC=screen-finance,DC=com

is the Domain Owner, but is deleted..........................
REEVES failed
test KnowsOfRoleHolders

If I try and change the role via Domains and Trusts 'Change
Operations
Master', I get the error message

"The transfer of the operations master role cannot be
performed because the
requested FSMO operation failed. The current FSMO holder could
not be
contacted.

I really do not want to seize the role because I need to keep
this server in
the domain. Can I use ADSI Editor? Does anyone have any ideas
on how to fix?

Thank
Click to expand...

The case here is that the domain naming master fsmo for some reason
has been removed. As the role was not transfered before the remove it
has been orphaned. The solution here is to seize the domain naming
fsmo to another healthy DC. I don’t understand what you mean with "I
really do not want to seize the role because I need to keep this
server in
the domain" Can you explain that?
 
Back
Top