Error - Invalid Partner Auth Client
can help!I had a windows 2000 server (SB-2) operating alone using AD. I added a w2k3server (SB-3). I adpreped the 2k server, and successfully added the w2k3server to the domain. All went fine. I then set the w2k3 server asoperations master, infrastructure master, PDC, GC etc.Now, what has happened is that SB-2 will not replicate SYSVOL from the SB-3,event log gives 13508 error, however none of the situations given in theerror description exists. I tried demoting SB-2 and then promoting usingDCPROMO. That worked fine, but didn't fix the problem. And now it won't actas a DC cause its waiting for SYSVOL.I've been through virtually every KB article, website article, newsgroup,whatever. Still no solution. I've upped the diagnostics on NTFRS and I thinkthe errors given in the logs should point to the problem, and thus solution,but I've been unable to find it.SB-2, the w2k server that will not replicate SYSVOL, has the followingrepeatedly in the NTFRS log -***************
20, 2004. Joep Verhaeg Guest Hello, Since a couple of day's the File Replication Service is not replicating the SYSVOL anymore with Event ID: 13508 on one domain controller, the other only logs the message "The File Replication Service is no longer preventing the computer server2 from becoming a domain controller...", the following actions I performed to try to fix it: 1. Verified name resolution, DNS is http://microsoft.public.windows.server.active-directory.narkive.com/HxLVfA3s/sysvol-replication-problem working fine on both DC's (using AD integrated DNS). 2. Verified the creation of SRV records for both DC's and this is also fine. 3. Restarted the NtFrs service on both DC's. 4. Verified the security (rights) on the SYSVOL folders (and subfolders) on both DC's, this is correct. 5. Reset the http://www.pcreview.co.uk/threads/file-replication-service-is-not-replicating-the-sysvol.1455294/ machine account following KB260575 for the DC which can not be connected to. 6. Netdiag reports everything is ok. 7. Replmon reports that AD replication is working fine. 8. Sonar reports LongJoinC for SERVER1 as "1" and for SERVER2 as "0", I don't know is this is normal or just my problem... 9. The system time is in sync on both DC's. 10. The SYSVOL share is available on both DC's (verified with the "net share" command). 11. There is enough harddisk space to replicate on both DC's. A snapshot from the logfiles created by the NtFrs service: -- Server1 NtFrs_0005.log: for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand https://www.experts-exchange.com/questions/21840079/DOMAIN-SYSTEM-VOLUME-SYSVOL-SHARE-in-state-STOPPED.html Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > DOMAIN SYSTEM VOLUME (SYSVOL SHARE) in state STOPPED Want to Advertise Here? Solved https://www.mail-archive.com/activedir@mail.activedir.org/msg09045.html DOMAIN SYSTEM VOLUME (SYSVOL SHARE) in state STOPPED Posted on 2006-05-05 Windows Server 2003 1 Verified Solution 12 Comments 2,599 Views Last Modified: 2009-08-06 I recently added 2 new Windows Server 2003 DCs to my topology. error - This brought my total DCs to 4. Everything was working fine. I then demoted my 2 old DCs (this was the reason for the whole thing, my DCs were 7 years old). After that, I've had SYSVOL replication problems. Following KB articles to repair it helped get most of the errors taken care of but still no replication. The error I keep getting when running "ntfrsutl sets" is: ACTIVE REPLICA SETS DOMAIN SYSTEM error - invalid VOLUME (SYSVOL SHARE) in state STOPPED DELETED REPLICA SETS If I check using adsiedit, I see that my servers are all listed just fine but the server with the problems is still missing the "frsMemberReferenceBL" setting. I can't modify this because I keep getting the error that this is owned by the system and can't be modified. The DC with the problem, shows up correctly everywhere else. It's only the fact that SYSVOL is not replicating and these errors that I'm getting. DCDiag just lets me know that there is a problem with replicating SYSVOL FRSDIAG Errors: C:\WINDOWS\debug\NtFrs_0005.log: 01, 2003 13:32 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] sysvol not replicating Yep, you have good AD replication at PSDC1 as well. This would tell me that the underpinnings should be ok and the problem is most likely strictly in FRS which sucks, I hate troubleshooting FRS. :op The duplicate connections I saw the error for would be visible in sites and services and you should see one connection that doesn't have a GUID name, it has a name of a domain controller. Err back to FRS, are there any errors in the FRS log besides the, SYSVOL is not shared out right now? If not we will have to start digging into the actual FRS debug logs located in %winnt%\debug - usually c:\winnt\debug. You will find logs that start with NTFRS and start scanning through looking for anything that could indicate an error. Possibly if the most recent one (should be named ntfrs_005.log) isn't too long you can post it so we can take a peek. Also Deji's post may have something to it in terms of the upgrade and something happening there. I am not a fan at all of in place upgrades, we did it once to the PDC for each of our domains to get the users and groups and then we quickly promoed a pure W2K machine and moved the fsmo's and wiped out the upgraded machine. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rittenhouse, Cindy Sent: Sunday, August 31, 2003 6:04 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] sysvol not replicating results from, repadmin on PSDC1 seems to indicate successful replication (lancco.root is an empty root domain for the forest). ECPDC is not listed as an outbound neighbor, I'm not sure what that implies. I did not see any duplicate connections. C:\Documents and Settings\Administrator.LC_POLICE>repadmin /showr Default-First-Site-Name\PSDC1 DSA Options : IS_GC objectGuid : 01dd65d5-caee-4e09-8cb3-85a7d4642ae9