Journal wrap problems with SBS 2003

Hi,
I am migrating SBS 2003 to SBS 2008 and have run the best practices scanner on the SBS 2003 box. I have fixed numerous problems except for 2. Been at it for 2 days.

1) The journal wrap problem. I have tried the suggested Burflaps solution; both the D4 and D2 regedit, but still the scanner reports the error. I also tried the enable journal wrap restore key solution pointed to by the scanner, (even though it's for W2000??)

2) NIC driver more than one year old

Questions:
Where to now?
and
Will the system migrate to SBS 2008 with the  Journal wrap error and / or the NIC driver error?
stoffel1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Larry Struckmeyer MVPCommented:
The JW error can be reported after it is fixed, depending on what report you are viewing.  Look in the event log view under File Replication Service.  If the condition still exists follow the steps in the detail of the event.  Also, look here:

http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Larry Struckmeyer MVPCommented:
More on this error:

Don't forget to net stop and net start the service from the command line:

net stop ntfrs
net start ntfrs

also, look here:

http://msmvps.com/blogs/bradley/archive/2009/11/27/burflags-and-journal-wrap.aspx
stoffel1Author Commented:
I finally fixed it by deleting the Event report which was from an error 6 months ago, then  re-running the scan. All fixed. Really odd the the BPA can't distinguish between a real fault and an old one??!!
Larry Struckmeyer MVPCommented:
It simply reads the event logs and picks up that error.  As you discovred, if you clear the event logs and run a new scan, the BPA won't see the JW error.

Good Job.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.