file replication service warnings

Hi,

We are currently running SBS2K, and we tried promoting our file server
(windows advanced server 2k) to be an additional domain controller for
redundancy, and so that we can still log in while we upgrade the small
business server to 2k3 in the next few weeks.

We ran dcpromo on the file server and no problems were experienced. After
the promotion, we switched off our small business server and experienced the
following problems:

- some users don't get mapped drives when they log in
- some users cannot access the internet
- the file server itself cannot access the internet

Further, we are receiving the following warnings in the File Replication
Service event log:

EventID 13508:

The File Replication Service is having trouble enabling replication from
JSRSBS01 to JSRFS01 for c:\winnt\sysvol\domain using the DNS name
jsrsbs01.jsr.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.


[1] FRS can not correctly resolve the DNS name jsrsbs01.jsr.local from
this computer.

[2] FRS is not running on jsrsbs01.jsr.local.

[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers.


This event log message will appear once per connection, After the
problem is fixed you will see another event log message indicating that the
connection has been established.

and also

EventID 13565:

File Replication Service is initializing the system volume with data
from another domain controller. Computer JSRFS01 cannot become a domain
controller until this process is complete. The system volume will then
be shared as SYSVOL.

To check for the SYSVOL share, at the command prompt, type:

net share


When File Replication Service completes the initialization process, the
SYSVOL share will appear.


The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between
domain controllers.


I used the active directory replication monitor on the small business server
to see if there was anything wrong, but it reported that everything was
working well. Also, the Active Directory and Users on the file server seems
to have all the correct data contained within it. Could someone please tell
me what's wrong, or what I haven't completed in the dcpromo process...
Please help!

Many thanks in advance,

Victor.

Lanwench
Wed Sep 21 22:46:14 CDT 2005



In news:YH7Ye.4447$0E5.4297@news-server.bigpond.net.au,
victor <victorl@jsr.com.au> typed:
> Hi,
>
> We are currently running SBS2K, and we tried promoting our file server
> (windows advanced server 2k) to be an additional domain controller for
> redundancy, and so that we can still log in while we upgrade the small
> business server to 2k3 in the next few weeks.
>
> We ran dcpromo on the file server and no problems were experienced.

Did you make it a global catalog server? Do this...

> After the promotion, we switched off our small business server and
> experienced the following problems:
>
> - some users don't get mapped drives when they log in

How do they map drives - login script in the netlogon share? Is the file
there? where are the shares themselves?

> - some users cannot access the internet

What DNS server are they pointing to? If your SBS box is down, make sure the
DNS server is correct (the new DNS server)

> - the file server itself cannot access the internet

DNS again? Presuming you can ping something by IP.
>
> Further, we are receiving the following warnings in the File
> Replication Service event log:


>
> EventID 13508:
>
> The File Replication Service is having trouble enabling
> replication from JSRSBS01 to JSRFS01 for c:\winnt\sysvol\domain using
> the DNS name jsrsbs01.jsr.local. FRS will keep retrying.
> Following are some of the reasons you would see this warning.
>
>
> [1] FRS can not correctly resolve the DNS name jsrsbs01.jsr.local
> from this computer.
>
> [2] FRS is not running on jsrsbs01.jsr.local.
>
> [3] The topology information in the Active Directory for this
> replica has not yet replicated to all the Domain Controllers.
>
>
> This event log message will appear once per connection, After the
> problem is fixed you will see another event log message indicating
> that the connection has been established.
>
> and also
>
> EventID 13565:
>
> File Replication Service is initializing the system volume with
> data from another domain controller. Computer JSRFS01 cannot become a
> domain controller until this process is complete. The system
> volume will then be shared as SYSVOL.
>
> To check for the SYSVOL share, at the command prompt, type:
>
> net share
>
>
> When File Replication Service completes the initialization
> process, the SYSVOL share will appear.
>
>
> The initialization of the system volume can take some time. The
> time is dependent on the amount of data in the system volume, the
> availability of other domain controllers, and the
> replication interval between domain controllers.
>
>
> I used the active directory replication monitor on the small business
> server to see if there was anything wrong, but it reported that
> everything was working well. Also, the Active Directory and Users on
> the file server seems to have all the correct data contained within
> it. Could someone please tell me what's wrong, or what I haven't
> completed in the dcpromo process... Please help!
>
> Many thanks in advance,
>
> Victor.

Did you force replication before powering down the SBS box? Sounds like
replication didn't complete.
Download & run netdiag.exe and dcdiag.exe on this server...

victor
Thu Sep 22 18:34:51 CDT 2005

Thanks for the reply Lanwench, see below for answers to your questions and
more questions!

Cheers

Victor.

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:u29h0iyvFHA.2880@TK2MSFTNGP12.phx.gbl...
>
>
> In news:YH7Ye.4447$0E5.4297@news-server.bigpond.net.au,
> victor <victorl@jsr.com.au> typed:
> > Hi,
> >
> > We are currently running SBS2K, and we tried promoting our file server
> > (windows advanced server 2k) to be an additional domain controller for
> > redundancy, and so that we can still log in while we upgrade the small
> > business server to 2k3 in the next few weeks.
> >
> > We ran dcpromo on the file server and no problems were experienced.
>
> Did you make it a global catalog server? Do this...

I have made it a global catalog server. Why did i need to do that?

>
> > After the promotion, we switched off our small business server and
> > experienced the following problems:
> >
> > - some users don't get mapped drives when they log in
>
> How do they map drives - login script in the netlogon share? Is the file
> there? where are the shares themselves?

There is a login script on the small business server in the sysvol directory
which explains why people may not get mapped drives when that server is off
but (1) why is it not replicating? and (2) why do some people still get the
correct mappings?

In fact, the SYSVOL directory on the new domain controller is empty except
for some folder structures.

>
> > - some users cannot access the internet
>
> What DNS server are they pointing to? If your SBS box is down, make sure
the
> DNS server is correct (the new DNS server)

This has been fixed by adding the correct alternate DNS into the TCP/IP
settings


>
> > - the file server itself cannot access the internet
>
> DNS again? Presuming you can ping something by IP.

Yep. As above.


> >
> >
> >
> > I used the active directory replication monitor on the small business
> > server to see if there was anything wrong, but it reported that
> > everything was working well. Also, the Active Directory and Users on
> > the file server seems to have all the correct data contained within
> > it. Could someone please tell me what's wrong, or what I haven't
> > completed in the dcpromo process... Please help!
> >
> > Many thanks in advance,
> >
> > Victor.
>
> Did you force replication before powering down the SBS box? Sounds like
> replication didn't complete.
> Download & run netdiag.exe and dcdiag.exe on this server...

I tried forcing replication, but it seems like it doesn't do anything. The
replication complete dialog box appears almost immediately after clicking
replicate.

Lanwench
Fri Sep 23 22:49:14 CDT 2005



In news:vcHYe.10263$0E5.7918@news-server.bigpond.net.au,
victor <victorl@jsr.com.au> typed:
> Thanks for the reply Lanwench, see below for answers to your
> questions and more questions!
>
> Cheers
>
> Victor.
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
> message news:u29h0iyvFHA.2880@TK2MSFTNGP12.phx.gbl...
>>
>>
>> In news:YH7Ye.4447$0E5.4297@news-server.bigpond.net.au,
>> victor <victorl@jsr.com.au> typed:
>>> Hi,
>>>
>>> We are currently running SBS2K, and we tried promoting our file
>>> server (windows advanced server 2k) to be an additional domain
>>> controller for redundancy, and so that we can still log in while we
>>> upgrade the small business server to 2k3 in the next few weeks.
>>>
>>> We ran dcpromo on the file server and no problems were experienced.
>>
>> Did you make it a global catalog server? Do this...
>
> I have made it a global catalog server. Why did i need to do that?

Becaue you need at least one available all the time - it's a Good Thing, and
has no downside.
>
>>
>>> After the promotion, we switched off our small business server and
>>> experienced the following problems:
>>>
>>> - some users don't get mapped drives when they log in
>>
>> How do they map drives - login script in the netlogon share? Is the
>> file there? where are the shares themselves?
>
> There is a login script on the small business server in the sysvol
> directory which explains why people may not get mapped drives when
> that server is off but (1) why is it not replicating?

No idea - event logs? If you force replication in AD sites and services,
does it produce errors?

> and (2) why do
> some people still get the correct mappings?

Local mappings, perhaps?
>
> In fact, the SYSVOL directory on the new domain controller is empty
> except for some folder structures.

That's not good - indicative of a connectivity/replication problem.
>
>>
>>> - some users cannot access the internet
>>
>> What DNS server are they pointing to? If your SBS box is down, make
>> sure the DNS server is correct (the new DNS server)
>
> This has been fixed by adding the correct alternate DNS into the
> TCP/IP settings

OK - but it's an internal one, right?
>
>
>>
>>> - the file server itself cannot access the internet
>>
>> DNS again? Presuming you can ping something by IP.
>
> Yep. As above.
>
>
>>>
>>>
>>>
>>> I used the active directory replication monitor on the small
>>> business server to see if there was anything wrong, but it reported
>>> that everything was working well. Also, the Active Directory and
>>> Users on the file server seems to have all the correct data
>>> contained within it. Could someone please tell me what's wrong, or
>>> what I haven't completed in the dcpromo process... Please help!
>>>
>>> Many thanks in advance,
>>>
>>> Victor.
>>
>> Did you force replication before powering down the SBS box? Sounds
>> like replication didn't complete.
>> Download & run netdiag.exe and dcdiag.exe on this server...
>
> I tried forcing replication, but it seems like it doesn't do
> anything. The replication complete dialog box appears almost
> immediately after clicking replicate.

victor
Tue Sep 27 22:19:47 CDT 2005

Thanks Lanwench,

I found an error in the file replication service event log on the SBS
machine which related to a journal wrap error. I have found a few mskb
articles on it and I will try to troubleshoot it accordingly. I'll post back
on how it goes.

Victor.

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:%239SztyLwFHA.624@TK2MSFTNGP11.phx.gbl...
>
>
> In news:vcHYe.10263$0E5.7918@news-server.bigpond.net.au,
> victor <victorl@jsr.com.au> typed:
> > Thanks for the reply Lanwench, see below for answers to your
> > questions and more questions!
> >
> > Cheers
> >
> > Victor.
> >
> > "Lanwench [MVP - Exchange]"
> > <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
> > message news:u29h0iyvFHA.2880@TK2MSFTNGP12.phx.gbl...
> >>
> >>
> >> In news:YH7Ye.4447$0E5.4297@news-server.bigpond.net.au,
> >> victor <victorl@jsr.com.au> typed:
> >>> Hi,
> >>>
> >>> We are currently running SBS2K, and we tried promoting our file
> >>> server (windows advanced server 2k) to be an additional domain
> >>> controller for redundancy, and so that we can still log in while we
> >>> upgrade the small business server to 2k3 in the next few weeks.
> >>>
> >>> We ran dcpromo on the file server and no problems were experienced.
> >>
> >> Did you make it a global catalog server? Do this...
> >
> > I have made it a global catalog server. Why did i need to do that?
>
> Becaue you need at least one available all the time - it's a Good Thing,
and
> has no downside.
> >
> >>
> >>> After the promotion, we switched off our small business server and
> >>> experienced the following problems:
> >>>
> >>> - some users don't get mapped drives when they log in
> >>
> >> How do they map drives - login script in the netlogon share? Is the
> >> file there? where are the shares themselves?
> >
> > There is a login script on the small business server in the sysvol
> > directory which explains why people may not get mapped drives when
> > that server is off but (1) why is it not replicating?
>
> No idea - event logs? If you force replication in AD sites and services,
> does it produce errors?
>
> > and (2) why do
> > some people still get the correct mappings?
>
> Local mappings, perhaps?
> >
> > In fact, the SYSVOL directory on the new domain controller is empty
> > except for some folder structures.
>
> That's not good - indicative of a connectivity/replication problem.
> >
> >>
> >>> - some users cannot access the internet
> >>
> >> What DNS server are they pointing to? If your SBS box is down, make
> >> sure the DNS server is correct (the new DNS server)
> >
> > This has been fixed by adding the correct alternate DNS into the
> > TCP/IP settings
>
> OK - but it's an internal one, right?
> >
> >
> >>
> >>> - the file server itself cannot access the internet
> >>
> >> DNS again? Presuming you can ping something by IP.
> >
> > Yep. As above.
> >
> >
> >>>
> >>>
> >>>
> >>> I used the active directory replication monitor on the small
> >>> business server to see if there was anything wrong, but it reported
> >>> that everything was working well. Also, the Active Directory and
> >>> Users on the file server seems to have all the correct data
> >>> contained within it. Could someone please tell me what's wrong, or
> >>> what I haven't completed in the dcpromo process... Please help!
> >>>
> >>> Many thanks in advance,
> >>>
> >>> Victor.
> >>
> >> Did you force replication before powering down the SBS box? Sounds
> >> like replication didn't complete.
> >> Download & run netdiag.exe and dcdiag.exe on this server...
> >
> > I tried forcing replication, but it seems like it doesn't do
> > anything. The replication complete dialog box appears almost
> > immediately after clicking replicate.
>
>

Victor
Wed Sep 28 09:54:48 CDT 2005

Hi,

I followed the instructions as laid out by the mskb article regarding
journal wrap errors and set the burflags to d2 for a non-authoritative
restore.

This resolved the journal wrap error quite effectively, but now we are
experiencing much worse problems.

Exchange does not start any more because it cannot find the global catalog
server, even though it runs on the sbs machine which must be a GC. (I've had
to write this email from home)

Since exchange doesn't start, some drive mappings are going a little strange
and we are getting warnings from W3SVC to the effect that it cannot locate
some entities.

What i think has happened is that the non-authorative restore performed by
the sbs machine has now copied the sysvol from the file server, which was
EMPTY, and now all the computers think we have no domain...

AD sites and services works occasionally, although not 100% and AD users and
computers doesn't like to start either. both complain of not being able to
find the domain.

Is there a way to resolve this without reverting back to a previous backup?
if we restore a backup, we will be left with journal wrap errors as
before...

Any help is much appreciated. Cheers

Victor.


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:%239SztyLwFHA.624@TK2MSFTNGP11.phx.gbl...
>
>
> In news:vcHYe.10263$0E5.7918@news-server.bigpond.net.au,
> victor <victorl@jsr.com.au> typed:
>> Thanks for the reply Lanwench, see below for answers to your
>> questions and more questions!
>>
>> Cheers
>>
>> Victor.
>>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
>> message news:u29h0iyvFHA.2880@TK2MSFTNGP12.phx.gbl...
>>>
>>>
>>> In news:YH7Ye.4447$0E5.4297@news-server.bigpond.net.au,
>>> victor <victorl@jsr.com.au> typed:
>>>> Hi,
>>>>
>>>> We are currently running SBS2K, and we tried promoting our file
>>>> server (windows advanced server 2k) to be an additional domain
>>>> controller for redundancy, and so that we can still log in while we
>>>> upgrade the small business server to 2k3 in the next few weeks.
>>>>
>>>> We ran dcpromo on the file server and no problems were experienced.
>>>
>>> Did you make it a global catalog server? Do this...
>>
>> I have made it a global catalog server. Why did i need to do that?
>
> Becaue you need at least one available all the time - it's a Good Thing,
> and has no downside.
>>
>>>
>>>> After the promotion, we switched off our small business server and
>>>> experienced the following problems:
>>>>
>>>> - some users don't get mapped drives when they log in
>>>
>>> How do they map drives - login script in the netlogon share? Is the
>>> file there? where are the shares themselves?
>>
>> There is a login script on the small business server in the sysvol
>> directory which explains why people may not get mapped drives when
>> that server is off but (1) why is it not replicating?
>
> No idea - event logs? If you force replication in AD sites and services,
> does it produce errors?
>
>> and (2) why do
>> some people still get the correct mappings?
>
> Local mappings, perhaps?
>>
>> In fact, the SYSVOL directory on the new domain controller is empty
>> except for some folder structures.
>
> That's not good - indicative of a connectivity/replication problem.
>>
>>>
>>>> - some users cannot access the internet
>>>
>>> What DNS server are they pointing to? If your SBS box is down, make
>>> sure the DNS server is correct (the new DNS server)
>>
>> This has been fixed by adding the correct alternate DNS into the
>> TCP/IP settings
>
> OK - but it's an internal one, right?
>>
>>
>>>
>>>> - the file server itself cannot access the internet
>>>
>>> DNS again? Presuming you can ping something by IP.
>>
>> Yep. As above.
>>
>>
>>>>
>>>>
>>>>
>>>> I used the active directory replication monitor on the small
>>>> business server to see if there was anything wrong, but it reported
>>>> that everything was working well. Also, the Active Directory and
>>>> Users on the file server seems to have all the correct data
>>>> contained within it. Could someone please tell me what's wrong, or
>>>> what I haven't completed in the dcpromo process... Please help!
>>>>
>>>> Many thanks in advance,
>>>>
>>>> Victor.
>>>
>>> Did you force replication before powering down the SBS box? Sounds
>>> like replication didn't complete.
>>> Download & run netdiag.exe and dcdiag.exe on this server...
>>
>> I tried forcing replication, but it seems like it doesn't do
>> anything. The replication complete dialog box appears almost
>> immediately after clicking replicate.
>
>