Are you getting an error? Is there anything in the event viewer? Need a little more information before we can try to help you!
Main Topics
Browse All TopicsTrying to replmon.exe on a new 2003 server. It does not appear to even run on the 2nd DC or the 1st DC.
Thanks.
Joe
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
No error. Looks like the program opens and closes real fast though. Nothing in the event log regarding replmon.exe. The 1st DC is an NT 4.0 upgraded to 2003. The 2nd DC is a virgin install of 2003. The 1st DC is dishing out group policies fine so I think it is ok. Just not sure why replmon won’t run.
Thanks.
Joe
The following is in the event log under File Replication Service after a fresh reboot. Maybe a DNS issue?
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/25/2004
Time: 4:13:49 PM
User: N/A
Computer: FAMEDC2
Description:
The File Replication Service is having trouble enabling replication from \\famedc1.fame to FAMEDC2 for c:\windows\sysvol\domain using the DNS name \\famedc1.fame. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name \\famedc1.fame from this computer.
[2] FRS is not running on \\famedc1.fame.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
For more information, see Help and Support Center at http://go.microsoft.com/fw
There are a couple of causes for 13508 errors, but let's start with the least intrussive:
http://support.microsoft.c
first try the file replication diagnostics tool
http://www.microsoft.com/d
This is what the diag tool gave me. Access denied ? Still seems to have something to do with DNS.
FRSDiag v1.7 on 10/26/2004 8:08:03 AM
.\famedc1 on 2004-10-26 at 8.08.03 AM
--------------------------
Checking for errors/warnings in FRS Event Log .... passed
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size...
ERROR : File Backlog TO server "FAME\FAMEDC2$" is : 887 :: Unless this is due to your schedule, this is a problem!
ERROR : File Backlog TO server "FAME\FAMEDC2$" is : 887 :: Unless this is due to your schedule, this is a problem!
ERROR : File Backlog TO server "FAME\FAMEDC2$" is : 887 :: Unless this is due to your schedule, this is a problem!
ERROR : File Backlog TO server "FAME\FAMEDC2$" is : 887 :: Unless this is due to your schedule, this is a problem!
failed with 4 error(s) and 0 warning(s)
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <FrsDsGetComputer: 2140: 8983: S1: 10:22:34> :DS: WARN - Could not find computer in computers CN=Computers,DC=fame; WStatus ERROR_ACCESS_DENIED
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <FrsDsGetComputer: 2140: 8996: S1: 10:22:34> :DS: WARN - Could not find computer in defaultnc DC=fame; WStatus ERROR_ACCESS_DENIED
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <FrsDsGetComputer: 2140: 9011: S1: 10:22:34> :DS: WARN - Could not find computer in defaultnc USER DC=fame; WStatus ERROR_ACCESS_DENIED
Found 5 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
......... failed with 5 error entries
Checking NtFrs Service (and dependent services) state...passed
Checking NtFrs related Registry Keys for possible problems...passed
Checking Repadmin Showreps for errors...passed
Final Result = failed with 9 error(s)
see the permissions described in the
answer to the question "Can I enable FRS replication on a DFS link whose
targets are in different domains?" at
http://www.microsoft.com/w
The FRS objects in AD are illustrated in the FRS Technical Reference at
http://www.microsoft.com/r
Specifically, you'll want to search for the following graphic "FRS
Containers and Objects in Active Directory for DFS Replica Sets"
or else u must have these permissions:
• You must have Read and Create All Child Objects permissions for the computer object of each computer that will be part of the replica set.
• You must be a member of the local Administrators group on each computer that will be part of the replica set.
• You must have Read and Create All Child Objects permissions for the File Replication Service container and all its child objects. Although the File Replication Service container can exist in every domain, you must add these permissions to the File Replication Service container that is in the domain where the domain-based root is configured.
Hi jpasint
You can follow the instructions given in the below links to solve your problem.
http://www.microsoft.com/r
http://support.microsoft.c
Hope it will work
Sorry, been busy on other issues for the past few days. I thought it had run clean. Not sure what I ran that made me think it was clean but going back to it, this is the log….
So there still seems to be an issue somewhere. I don't understand why this should be so difficult. The DC was upgraded to 2003 from an NT 4.0 PDC. I know that is not good but we intend to do a fresh install once we get another DC on the network. Is it the fact that it was upgraded from NT? I have GP working fine with a few clients already. One thing that I can think of..
I have the NT4Emultaor key set in the registry of the DC so that all of the client don't automatically move to AD. I then have the NeutralizeNT4Emulator on the few clients that are using AD. Could that be a problem?
Thanks again.
Joe
NtFrs 10/25/2004 4:12:02 PM Warning 13565 File Replication Service is initializing the system volume with data from another domain controller. Computer FAMEDC2 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. To check for the SYSVOL share, at the command prompt, type: net share When File Replication Service completes the initialization process, the SYSVOL share will appear. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
NtFrs 10/25/2004 8:47:50 AM Warning 13565 File Replication Service is initializing the system volume with data from another domain controller. Computer FAMEDC2 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. To check for the SYSVOL share, at the command prompt, type: net share When File Replication Service completes the initialization process, the SYSVOL share will appear. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
NtFrs 10/25/2004 8:41:10 AM Warning 13562 Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller \\famedc1.fame for FRS replica set configuration information. This computer is not part of any valid replica set.
WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!
......... failed 8
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0004.log : "ERROR_ACCESS_DENIED" : <SndCsMain: 1968: 889: S0: 16:50:06> :SR: Cmd 01135be0, CxtG f699a550, WS ERROR_ACCESS_DENIED, To famedc1.fame Len: (368) [SndFail - Send Penalty]
ERROR on NtFrs_0004.log : "ERROR_ACCESS_DENIED" : <SndCsMain: 1968: 867: S0: 16:50:26> :SR: Cmd 01123190, CxtG f699a550, WS ERROR_ACCESS_DENIED, To famedc1.fame Len: (368) [SndFail - rpc call]
ERROR on NtFrs_0004.log : "ERROR_ACCESS_DENIED" : <SndCsMain: 1968: 889: S0: 16:50:26> :SR: Cmd 01123190, CxtG f699a550, WS ERROR_ACCESS_DENIED, To famedc1.fame Len: (368) [SndFail - Send Penalty]
ERROR on NtFrs_0005.log : "EPT_S_NOT_REGISTERED(This
ERROR on NtFrs_0005.log : "EPT_S_NOT_REGISTERED(This
ERROR on NtFrs_0005.log : "EPT_S_NOT_REGISTERED(This
ERROR on NtFrs_0005.log : "RPC_S_CALL_FAILED_DNE(Ind
ERROR on NtFrs_0005.log : "RPC_S_CALL_FAILED_DNE(Ind
ERROR on NtFrs_0005.log : "RPC_S_CALL_FAILED_DNE(Ind
ERROR on NtFrs_0004.log : "WS RPC_S_SERVER_TOO_BUSY(The target server may be overwhelmed, memory or CPU-wise. Is the target server a very busy bridgehead?)" : <SndCsMain: 1968: 874: S0: 16:50:57> :SR: Cmd 01135be0, CxtG f699a550, WS RPC_S_SERVER_TOO_BUSY, To famedc1.fame Len: (368) [SndFail - rpc exception]
ERROR on NtFrs_0004.log : "WS RPC_S_SERVER_TOO_BUSY(The target server may be overwhelmed, memory or CPU-wise. Is the target server a very busy bridgehead?)" : <SndCsMain: 1968: 889: S0: 16:50:57> :SR: Cmd 01135be0, CxtG f699a550, WS RPC_S_SERVER_TOO_BUSY, To famedc1.fame Len: (368) [SndFail - Send Penalty]
Found 6 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
Found 2966 EPT_S_NOT_REGISTERED error(s)! Latest ones (up to 3) listed above
Found 22 RPC_S_CALL_FAILED_DNE error(s)! Latest ones (up to 3) listed above
Found 2 WS RPC_S_SERVER_TOO_BUSY error(s)! Latest ones (up to 3) listed above
......... failed with 2996 error entries
Checking NtFrs Service (and dependent services) state...
ERROR : Cannot access SYSVOL share on FAMEDC2
ERROR : Cannot access NETLOGON share on FAMEDC2
......... failed 2
Checking NtFrs related Registry Keys for possible problems...
SYSTEM\CurrentControlSet\S
failed with 1 error(s) and 0 warning(s)
Checking Repadmin Showreps for errors...passed
Final Result = failed with 3007 error(s)
Business Accounts
Answer for Membership
by: jpasintPosted on 2004-10-25 at 13:02:31ID: 12404309
Above should read "Trying to run replmon.exe".
Joe