Link to home
Start Free TrialLog in
Avatar of ltoen
ltoenFlag for Norway

asked on

JRNL_WRAP_ERROR event id 13568

Hi

I have 2 Windows 2000 servers, the primary server gets event id 13568 and journal wrap error in the NTFRS event viewer. It has login scripts and shared sysvol folder. The other server has not been able to share out sysvol share because of the error on the primary server. I have read about the Journal Wrap Automatic Restore, but what happens when I get the error on the the server thats holds the only working sysvol share ? Does it build a blank sysvol and how will this effect me? Does Sysvol contain active directory information or is it just for sharing policy and loginscripts ?



Hope someone can help

Best regards Lars

SOLUTION
Avatar of anil_u
anil_u

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ltoen

ASKER

Thanks anil_u

Good links but I still wonder what happens with the Automatic restore reg key if I deside to rund it, will all the group policies be reset or/and  will AD get destroyed ?


br lars

ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ltoen

ASKER

Hi LesHarley
Thank you for your response, did you do the automatic restore key?

Br lars
Avatar of ltoen

ASKER

As a comment to the issue, I didnt do anything about this for som weeks. Suddenly the domain controller crashed with  lsass.exe error. MS articles refered to ntds.dit file beeing corrupt and so on. I also got strange characters when logging inn. Example Preparing Network connections was filled with ???#"?"?"?"? and so on. I got the ad controller up in Active Directory Restore mode. The restore password did not work so i had to install win2k pro on a different partition. Booted this partition renamedthe SAM file. Restartet in Restore Mode for AD and logged inn with blank password. I then restored a Systemstate backup. After a reboot AD started and the errors I ad where gone.  After that I got an error regarding SAM database, I though this was because I replaced the orignal so i started the Win2k pro session again and restored the file. Same issue, I read at microsoft something about Metadata og sync of sam. Before i started with the whole recepie, I waited 15 minuttes, suddenly I looked in the event log and it said it had replicated the SAM database and everyting was ok.
This is just my experience that i would like to share in case someone gets the same strange errors.

BR lars