Blog

Sometimes your system may display a message with event ID 13509 13508. This problem can have several causes.

Updated

1. Download ASR Pro

2. Run the program

3. Click "Scan Now" to find and remove any viruses on your computer

Speed up your computer today with this simple download.

g.This indicates that FRS is having trouble enabling replication with this partner and will continue to try to customize the installation. A single event ID 13508 no longer means something is broken or not working; Just look for Event ID 13509 to see if the issue is resolved.

g.

I have 13509, 13508 inconsistencies. How do I fix the following errors?

1. In general, check for FRS event ID 13508 to evaluate the computer that FRS was unable to communicate with.

2. Determine if the remote computer is working properly and check if FRS is running on it. At a command prompt on the computer that most often logs FRS event ID 13508, type the following command, and then press ENTER accordingly:

   ntfrsutl different

   If this fails, use the ping command to test the organization’s connectivity so that computers that have FRS event ID 13508 ping the full The business domain (FQDN) of the remote domain controller. If this fails, troubleshoot the errors primarily due to DNS or TCP / IP issues. If the application succeeds, make sure the frs service is running on the remote domain controller.

3. Determine if FRS workers have ever been able to communicate with each remote computer by viewing the FRS event ID 13509 in the event log. Therefore, check if the FRS issue for you is related to the latest change management for network, firewalls, DNS configuration, or Active Directory infrastructure.

4. Determine if two computers can frequently block RPC data traffic, such as a firewall or router.

5. 

   Make sure Active Directory replication is working. For more important troubleshooting information about Active Directory Replication, see the Troubleshooting Active Directory Replication section of this guide.

Thanks for the great help. I spent some time looking for pa before asking for help ~~ I’ve read a lot of articles but haven’t found most of the clues yet.

I have sites, 7 and a Windows 2003 DC server that have been building for 4 years now. Now, the all in one cool DC for the site does indeed have an event ID of 13508 (as of February). “The File Replication Service must have problems enabling replication from” Server A to Server B for d: domain windows sysvol using the most important DNS domain name …. FRS saves retries … etc. “.

At the time, I followed one method to test all of the above, including running repadmin / showreps and / or / showconn, netdiag, NTFRSUtl version ..etc, checking NTDS plan and enabling RPC, pinging DC friend friend look like this: good!

ERROR “serverA” forum backlog file: 63313 :: Problem if it is not programmed in your diary!

I also scan for viruses and malware, but found nothing. It looks like not all required ports have been blocked for a long time.

and jsi (the connection specified on the forum no longer works .

So what’s the downside? Hooray too, I also checked the staging area folder during staging, they are mostly empty on both servers. So what should I do ??

Here I announced that the forum found it could fix the problem by working on the JSI 5439 cheats … here is the original forum link

Speed up your computer today with this simple download.

이벤트 ID 13509 13508
Id Do Evento 13509 13508
Identifiant D’événement 13509 13508
Gebeurtenis-ID 13509 13508
Ereignis-ID 13509 13508
Идентификатор события 13509 13508
Identyfikator Zdarzenia 13509 13508
Händelse-id 13509 13508
Id. De Evento 13509 13508
ID Evento 13509 13508