Replication errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Basically, we have a root domain with a child. I have setup an additional
site in the root domain. This site does not need to know about the child
domain as it will have no interaction with it at all. I setup the links
between the domain and replication is fine. However, I receive errors as the
child domains entries cannot be written. Do I have to setup a link here or
am I missing something? I really dont need this site to have the child
domains info. Thanks.
 
I'm a little confused. What is your problem here?

Sites are stored in the configuration partition, which means all domains
know about the sites.

If you've configured multiple domains in the forest, they all know about
each other (there's default trusts in there ;-)

If you're having permission errors, what are you trying to do when you get
them? You'll need to delegate some extra permissions to child-domain admins
if you want to make changes to the parent.

www.eventid.net is a great resource for info. on those errors.

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Basically, we have a root domain with a child. I have setup an additional
site in the root domain. This site does not need to know about the child
domain as it will have no interaction with it at all. I setup the links
between the domain and replication is fine. However, I receive errors as
the
child domains entries cannot be written. Do I have to setup a link here or
am I missing something? I really dont need this site to have the child
domains info. Thanks.
 
Actually, I think I figured it out. It is a little confusing I agree. What
basically happened was that when I created the new site, it added this to a
site link going to the other domain. The site I happen to have added is
physically connected to the root via a vpn tunnel and cannot see the other
network. That is why the error seems to have happened. So far its ok but it
will take some more testing to make sure.
 
There's a connection object because the enterprise partitions (schema and
configuration) replicate between all domains. If there's not a direct line,
you should configure SMTP replication (as opposed to MS-RPC (IP)).

If there's not a path for replication you will see lots of KCC warnings and
errors.

You need to correct this...

--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Actually, I think I figured it out. It is a little confusing I agree. What
basically happened was that when I created the new site, it added this to a
site link going to the other domain. The site I happen to have added is
physically connected to the root via a vpn tunnel and cannot see the other
network. That is why the error seems to have happened. So far its ok but
it
will take some more testing to make sure.
 
Back
Top