-----Original Message-----
It should zip a lot given that it is just txt. Just zip it up and email it
over.
~Eric
--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Eric,
Well, I created an ldf dump file and it's over 4mb - is
there an 'abbreviated' file I could generate? I'd love to
share it with you, offline, but I don't want to choke up
the system with this thing!
-----Original Message-----
Totally understood.
You can also send me that ldif file offline (remove
online from my email
address) and I can take a look if you would like me to.
~Eric
--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm
in message
I think I'm going to pass on sharing the ldif in this
forum.....I'll turn up the logging and wade through the
ldif myself and see if it makes sense.
-----Original Message-----
Typically when you see this sort of an error that
clues
me in that we have a
site topology problem.
In a nutshell we would want to inspect our site links
to
ensure that they
form a complete map of the sites we have defined.
If you give us a full ldif dump of the config
container
(ldifde -f
foo.ldf -d "cn=configuration,dc=X" - where X is your
domain actually
spelled out in standard syntax with dc=foo,dc=bar
etc.)
we could probably
tell you more specifically. I understand you may not
want to share this over
a public newsgroup though.
Also enabling kcc logging
(hklm\system\currentcontrolset\services\ntds\parameters
is the reg key that
has this setting) and turning it to 4 will also spew
extra data to the
directory services event log.
~Eric
--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no warranties,
and
confers no rights
Use of included script samples are subject to the
terms
specified at
http://www.microsoft.com/info/cpyright.htm
"Sandy Wood" <
[email protected]>
wrote
in message
I've done some further checking and found that I've
got
one site that can't seem to communicate with the
other
sites correctly. I've got a central office with six
satellite offices. Each office is a site with 1 DC
that
has DCHP, DNS, GC and is a ISTG. Users can log in
and
everything works fine - I can even force
replication in
replmon and it comes back sucessful.
I'm getting NDTS KCC / 1566 errors on 5 out of the 6
sites that say:
=====================================================
All servers in site CN=DA-
WOC,CN=Sites,CN=Configuration,DC=da,DC=ocgov,DC=com
that
can replicate partition
DC=dev,DC=da,DC=ocgov,DC=com over transport
CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=da,DC=ocgov,DC=com
are
currently unavailable.
This happens 4 times for each partition DA-WOC is
trying
to replicate.
After each 1566 I get a 1311...
========================================
The Directory Service consistency checker has
determined
that either (a) there
is not enough physical connectivity published via
the
Active Directory Sites and
Services Manager to create a spanning tree
connecting
all
the sites containing
the Partition DC=dev,DC=da,DC=ocgov,DC=com, or (b)
replication cannot be performed with one or more
critical servers in order for changes to propagate
across
all sites (most often
due to the servers being unreachable).
For (a), please use the Active Directory Sites and
Services Manager to do one
of the following:
1. Publish sufficient site connectivity information
such
that the system can
infer a route by which this Partition can reach this
site. This option is
preferred.
2. Add an ntdsConnection object to a Domain
Controller
that contains the
Partition DC=dev,DC=da,DC=ocgov,DC=com in this site
from
a Domain Controller that contains the same
Partition in another site.
For (b), please see previous events logged by the
NTDS
KCC source that
identify the servers that could not be contacted.
Again, 4 times. My Sites and Services appear to have
all
site links ok and this just started happening a week
ago
after smooth running for months.
Any ideas?
-----Original Message-----
If I may suggest that enabling KCC is a good idea.
There
is usually little
reason to disable KCC unless you are in a large
environment (more than 100
sites with w2k, no real limit with w2k03). For the
1311's if you gave us the
full errors, maybe with other related ones
(possibly
1126's?), we could
probably get to the bottom of this.
Thanks!
~Eric
--
Eric Fleischman [MSFT]
This posting is provided "AS IS" with no
warranties,
and
confers no rights
Use of included script samples are subject to the
terms
specified at
http://www.microsoft.com/info/cpyright.htm
"Matjaz Ladava [MVP]"
