W2k3S:/FRS replication & sharing problem
W2k3S:/FRS replication & sharing problem
Number : SOX041011700076
Created : 10/11/2004
Region : US
TITLE: W2k3S:/FRS replication & sharing problem
**Problem** Windows Server 2003 Standard
ID: SOX041011700076 CRT: Oct 11 2004 MOD: Oct 11 2004
Problem Description
Even though the sysvol folder was shared out, you would not get a NTFrs 13516 event
after restarting FRS. You only got the messages which said that the FRS service
started and stopped. The other server trying to replicate with this server was not
able to replicate, getting 13508 events.
Additionally, the following was logged in the FRS debug logs:
EBI was the server name that the logs were taken on & having problems
MAKI was the DC who was trying to replicate with EBI
WAVE5 is the domain name
Server_FRSrpcSendCommPkt: ... Error - Invalid Partner: authclient: WAVE5\MAKI$
<FrsDsVerifyPromotionParent: 1424: 5582: S0: 21:31:18> :S: ERROR - DOMAIN
SYSTEM VOLUME (SYSVOL SHARE) does not exist on EBI!
<LOCAL_FrsRpcVerifyPromotionParent:1424: 1724: S0: 21:31:18> ++ ERROR - verifying
set DOMAIN SYSTEM VOLUME (SYSVOL SHARE) on parent EBI; WStatus: ERROR_NOT_FOUND
<SERVER_FrsRpcStartPromotionParent:1424: 1867: S0: 21:31:18> ++ ERROR - verify;
WStatus: FRS_ERR_SYSVOL_POPULATE
Resolution
The following registry key was completely missing:
HKLM\System\CCS\Services\NTFRS\Parameters\Sysvol
Once we added this key and restarted the file replication service, we got
additional messages other than the service start and stop messages. The following
errors above were no longer present in the FRS debug logs.
Leave a comment