Dcdiag: failed test frssysvol
Albert
One of my customers has a problem with one of his Dc's. On the Dc that
holds the fsmo roles, the NtFrs wil not start.
The stopping is succesful, but when i try to start it, the event log
says it is starting, but there wil no event show that it is started,
and that Sysvol and Netlogon are shared.
When i run the dcdiag command it generates this error:
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
The rest of the tests are succesful.
Any help would be appreciated.
Albert
There are 10 kinds op people, those who understand binary and those
who don't.
David Everett [MSFT]
When you try to start FRS in services.msc do you find the service says
Starting or Started?
If it shows as Started type "net share" at the command line and see if
Sysvol and Netlogon are shared out or not.
How many DCs are there in this domain and do any of them have Sysvol and
Netlogon shared? Are there any Errors in the File Replication event logs of
the FSMO holder and the DCs it has inbound connections from?
Is there DFS content replicated on these DCs?
If you run repadmin /showreps on the FSMO holder do you find that AD is
replicating correctly on this DC? If this is failing what is the date when
the last successful replication occurred?
Is this Windows 2000 or 2003? What Service Pack are the DCs at?
--
David Everett
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"Albert" <Leef...@technica.nl> wrote in message
news:95e155c5.04032...@posting.google.com...
Albert
Thnx for the fast reply. Here's some additional information about the
case i have.
There is 1 native windows 2000 domain with 1 head office and 3 branch
offices connected with WAN links. The head office contains 3 Dc's,
each branch office has 1 Dc's. All are also Gc's. The problem Dc is on
the head office. All servers run Sp4 with critical updates.
All other Dc's have the Sysvol and Netlogon shared, the problematic
one has not.
The problem server has no errors in the File replication event log. It
just states that Frs is starting, no event that it is started. In the
services.msc console the service is started. The servers with inbound
connections from this server have errors in the log. These are 13508,
Frs is having trouble enabling replication from S1(bad) to S2(good).
Active directory replication itself looks ok. repadmin /showreps shows
only succesful messages. I have also tried Replmon -> Search for
replication errors. This also stays blank.
DFS content is not used in the domain.
Although it is multi-master, could moving the Fsmo roles contribute to
the solution?
Albert.
"David Everett [MSFT]" <deve...@online.microsoft.com> wrote in message news:<OD5smsnF...@TK2MSFTNGP12.phx.gbl>...
David Everett [MSFT]
Moving FSMO roles will not help.
Was this DC upgraded from NT 4.0?
Open regedit.exe and regedt32.exe verify the information under
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters is the same in
both views. If they match then you might want to call the suport line and
request the latest FRS Rollup Hotfix. Once you have it, stop FRS on the
problem server and install the hotfix. After the reboot see if replication
starts to flow and Sysvol shares out. If not repeat these steps and install
the hotfix on the other DCs that replicate to this server.
If Sysvol still fails to share out you can stop FRS on the problem server
and only after FRS is stopped, set BurFlags to d2 (hex) on the problem
server. Once D2 is configured you can start FRS on the problem DC again and
wait to see if you get 13516 in the File Replication event log. BurFlags is
located under
HKLM\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Proce
ss at Startup
--
David Everett
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"Albert" <Leef...@technica.nl> wrote in message
news:95e155c5.04033...@posting.google.com...
Albert
The server is not upgraded from Windows Nt 4.0
The Regedit and Regedt32 are the same on both views.
About the FRS Rollup Hotfix, i have contacted MS. I can't get a fix
without a hotfix number. I've searched the sites, and can't find a
number. Do you know if it has a number, or do you have the correct
hotfix number?
I have tried the BurFlags register key, changing to d2, this doen't
work also.
Albert.
"David Everett [MSFT]" <deve...@online.microsoft.com> wrote in message news:<Oc5lyH1...@TK2MSFTNGP12.phx.gbl>...