Windows 2000 Replication Issue (Error ID 1311) & (Endpoint Mapper)

  • Thread starter Thread starter deckydee
  • Start date Start date
D

deckydee

Hi,

I am hoping that someone can help me out here as I am in a spot of
bother! :o)

I am consultant that has to go to a company next week because they are
getting an error in their Windows 2000 Replication Monitor:

'Replication Failure: The reason is: There are no more endpoints
available from the endpoint mapper'

That is not all; when I go to the Directory Service Event viewer I get
this error as well:

Event Type: Error
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1311
Date: 14-9-2005
Time: 16:05:37
User: N/A
Computer: IBADC00
Description:
The description for Event ID (1311) in Source ( NTDS KCC ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: DC=UPP,DC=XXX.

So as you can imagine, down the right left hand side, I have three
servers that have a red 'X' on them and the rest are ok.

The first thing that I did was I researched the 'Endpoint Mapper'
problem, I was directed to this site:

http://support.microsoft.com/?kbid=839880

I can already tell you at this stage that the correct entries are in
the registry and that Port 135 is listening.

Then after not having much success with that I moved to research the
'1311' problem.

There were several discussion groups about this error, but none that I
fell can solve my problem.

I also tried this site, but even though it said that it was for
'Troubleshooting error 1311, it does not have the same error as I do.
Even if I did, I don't understand it too well. You see the other
error messages don't have "The local computer may not have the
necessary registry information or message DLL files to display messages
from a remote computer"

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q214745

My real problem is that because of the two separate errors, I am not
sure if the problem is RPC or KCC!

I also checked this site:

http://support.microsoft.com/?id=244368

And found nothing of much use.

To be 100% sure about what I am doing I have read this site:

http://support.microsoft.com/kb/199174/en-us

But before you start, I am guessing that I have to do the following:


1 - Verify that DNS is working by going to the main DC and typing:

(NSLookup [FQDN of the DC in remote site, e.g. dc3.domain.local])


2 - Check whether Time Service is synchronizing on the problematic
servers

Could someone please be so kind as to help me out here and tell me what
the problem is? I would greatly appreciate it

Declan D
 
Try running netdiag, repadmin and dcdiag. Look for fail, error and warning
errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /s:DC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt


See for more details

http://www.microsoft.com/technet/pr...Ref/1d4ce93c-54f2-4069-a708-251509c38837.mspx



Endpoint mapper specific KB article
http://support.microsoft.com/?kbid=839880

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


deckydee said:
Hi,

I am hoping that someone can help me out here as I am in a spot of
bother! :o)

I am consultant that has to go to a company next week because they are
getting an error in their Windows 2000 Replication Monitor:

'Replication Failure: The reason is: There are no more endpoints
available from the endpoint mapper'

That is not all; when I go to the Directory Service Event viewer I get
this error as well:

Event Type: Error
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1311
Date: 14-9-2005
Time: 16:05:37
User: N/A
Computer: IBADC00
Description:
The description for Event ID (1311) in Source ( NTDS KCC ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: DC=UPP,DC=XXX.

So as you can imagine, down the right left hand side, I have three
servers that have a red 'X' on them and the rest are ok.

The first thing that I did was I researched the 'Endpoint Mapper'
problem, I was directed to this site:

http://support.microsoft.com/?kbid=839880

I can already tell you at this stage that the correct entries are in
the registry and that Port 135 is listening.

Then after not having much success with that I moved to research the
'1311' problem.

There were several discussion groups about this error, but none that I
fell can solve my problem.

I also tried this site, but even though it said that it was for
'Troubleshooting error 1311, it does not have the same error as I do.
Even if I did, I don't understand it too well. You see the other
error messages don't have "The local computer may not have the
necessary registry information or message DLL files to display messages
from a remote computer"

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q214745

My real problem is that because of the two separate errors, I am not
sure if the problem is RPC or KCC!

I also checked this site:

http://support.microsoft.com/?id=244368

And found nothing of much use.

To be 100% sure about what I am doing I have read this site:

http://support.microsoft.com/kb/199174/en-us

But before you start, I am guessing that I have to do the following:


1 - Verify that DNS is working by going to the main DC and typing:

(NSLookup [FQDN of the DC in remote site, e.g. dc3.domain.local])


2 - Check whether Time Service is synchronizing on the problematic
servers

Could someone please be so kind as to help me out here and tell me what
the problem is? I would greatly appreciate it

Declan D
Click to expand...
 
the "end point mapper" error ususally occurs when the ports are blocks you
can use portqry for checking to ports closed.

Also check whether the tcp/ip stack is working fine.

Paul Bergson said:
Try running netdiag, repadmin and dcdiag. Look for fail, error and warning
errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /s:DC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt


See for more details

http://www.microsoft.com/technet/pr...Ref/1d4ce93c-54f2-4069-a708-251509c38837.mspx



Endpoint mapper specific KB article
http://support.microsoft.com/?kbid=839880

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


deckydee said:
Hi,

I am hoping that someone can help me out here as I am in a spot of
bother! :o)

I am consultant that has to go to a company next week because they are
getting an error in their Windows 2000 Replication Monitor:

'Replication Failure: The reason is: There are no more endpoints
available from the endpoint mapper'

That is not all; when I go to the Directory Service Event viewer I get
this error as well:

Event Type: Error
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1311
Date: 14-9-2005
Time: 16:05:37
User: N/A
Computer: IBADC00
Description:
The description for Event ID (1311) in Source ( NTDS KCC ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: DC=UPP,DC=XXX.

So as you can imagine, down the right left hand side, I have three
servers that have a red 'X' on them and the rest are ok.

The first thing that I did was I researched the 'Endpoint Mapper'
problem, I was directed to this site:

http://support.microsoft.com/?kbid=839880

I can already tell you at this stage that the correct entries are in
the registry and that Port 135 is listening.

Then after not having much success with that I moved to research the
'1311' problem.

There were several discussion groups about this error, but none that I
fell can solve my problem.

I also tried this site, but even though it said that it was for
'Troubleshooting error 1311, it does not have the same error as I do.
Even if I did, I don't understand it too well. You see the other
error messages don't have "The local computer may not have the
necessary registry information or message DLL files to display messages
from a remote computer"

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q214745

My real problem is that because of the two separate errors, I am not
sure if the problem is RPC or KCC!

I also checked this site:

http://support.microsoft.com/?id=244368

And found nothing of much use.

To be 100% sure about what I am doing I have read this site:

http://support.microsoft.com/kb/199174/en-us

But before you start, I am guessing that I have to do the following:


1 - Verify that DNS is working by going to the main DC and typing:

(NSLookup [FQDN of the DC in remote site, e.g. dc3.domain.local])


2 - Check whether Time Service is synchronizing on the problematic
servers

Could someone please be so kind as to help me out here and tell me what
the problem is? I would greatly appreciate it

Declan D
Click to expand...
Click to expand...
 
Thanks for the update guys! - I ran some scans on-site and this is the
output i have from them:

I ran repadmin /showreps and it showed me that there was a replication
problem with only 1 server if though the problem is with three!

I ran repadmin /showism and i have no problem with my sites

The I ran dcdiag /test:intersite /e /q and i go the following errors:

[SERVER1] LDAP connection failed with error 58, The specified server
cannot perform the requested operation..
***Error: The machine, SERVER1 could not be contacted, because of a bad
net response. Check to make sure that this machine is a Domain
Controller. ......................... SERVER1 failed test Connectivity

The error above is for the first server, then this came for the second
server:

Although the Guid DNS name
(5af395b4-6b7e-4d13-a76f-ac072d30eed6._msdcs.XXX) resolved to the IP
address (192.168.10.10), which could not be pinged, the server name
(SERVER2.XXX.XXX) resolved to the IP address (192.168.10.100) and could
be pinged. Check that the IP address is registered correctly with the
DNS server.

The the same as the first error for the third server:

[SERVER3] LDAP connection failed with error 58, The specified server
cannot perform the requested operation..
***Error: The machine, SERVER3 could not be contacted, because of a bad
net response. Check to make sure that this machine is a Domain
Controller. ......................... SERVER3 failed test Connectivity

The more errors came:

*Warning: Remote bridgehead CN-BEI\SERVER1 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted into
the local site BE-Fleurus.
Remote bridgehead CN-BEI\SERVER1 also couldn't be contacted by dcdiag.
Check this server.

*Warning: Remote bridgehead US-JAX\SERVER2 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted into
the local site BE-Fleurus.
Remote bridgehead CN-BEI\SERVER2 also couldn't be contacted by dcdiag.
Check this server.

*Warning: Remote bridgehead US-SEO\SERVER3 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted into
the local site BE-Fleurus.
Remote bridgehead CN-BEI\SERVER3 also couldn't be contacted by dcdiag.
Check this server.

I also got this error:

***Error: The remote site BE-LLN, has no servers that can act
asbridgeheads between the BE-LLN and the local site BE-Fleurus forthe
writeable NC IBA.
Replication will not continue until this is resolved.

I also got this error for SERVER2:

[SERVER2] DsBind() failed with error 1753, There are no more endpoints
available from the endpoint mapper

MORE ERRORS/

***Error: The current ISTG is down in site BE-SEO and further dcdaig
could not contact any other servers in the site that could
take the ISTG role. Ensure there is at least one up DC. Must abandon
inbound intersite replication test for this site.

[SERVER1] LDAP connection failed with error 58, The specified server
cannot perform the requested operation..

[SERVER1] DsBind() failed with error 1722, The RPC server is
unavailable..

[SERVER3] DsBind() failed with error 1753, There are no more endpoints
available from the endpoint mapper..
***Error: The current ISTG is down in site US-JAX and further dcdaig
could not contact any other servers in the site that could take the
ISTG role. Ensure there is at least one up DC. Must abandon inbound
intersite replication test for this site.
***ERROR: There is an inconsistency in the DS, suggest you run dcdiag
in a few moments, perhaps on a different DC.

......................... XXX failed test Intersite


Please help if you can! :o)

Decky Dee

kapil schreef:
the "end point mapper" error ususally occurs when the ports are blocks you
can use portqry for checking to ports closed.

Also check whether the tcp/ip stack is working fine.

Paul Bergson said:
Try running netdiag, repadmin and dcdiag. Look for fail, error and warning
errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /s:DC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt


See for more details

http://www.microsoft.com/technet/pr...Ref/1d4ce93c-54f2-4069-a708-251509c38837.mspx



Endpoint mapper specific KB article
http://support.microsoft.com/?kbid=839880

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


deckydee said:
Hi,

I am hoping that someone can help me out here as I am in a spot of
bother! :o)

I am consultant that has to go to a company next week because they are
getting an error in their Windows 2000 Replication Monitor:

'Replication Failure: The reason is: There are no more endpoints
available from the endpoint mapper'

That is not all; when I go to the Directory Service Event viewer I get
this error as well:

Event Type: Error
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1311
Date: 14-9-2005
Time: 16:05:37
User: N/A
Computer: IBADC00
Description:
The description for Event ID (1311) in Source ( NTDS KCC ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: DC=UPP,DC=XXX.

So as you can imagine, down the right left hand side, I have three
servers that have a red 'X' on them and the rest are ok.

The first thing that I did was I researched the 'Endpoint Mapper'
problem, I was directed to this site:

http://support.microsoft.com/?kbid=839880

I can already tell you at this stage that the correct entries are in
the registry and that Port 135 is listening.

Then after not having much success with that I moved to research the
'1311' problem.

There were several discussion groups about this error, but none that I
fell can solve my problem.

I also tried this site, but even though it said that it was for
'Troubleshooting error 1311, it does not have the same error as I do.
Even if I did, I don't understand it too well. You see the other
error messages don't have "The local computer may not have the
necessary registry information or message DLL files to display messages
from a remote computer"

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q214745

My real problem is that because of the two separate errors, I am not
sure if the problem is RPC or KCC!

I also checked this site:

http://support.microsoft.com/?id=244368

And found nothing of much use.

To be 100% sure about what I am doing I have read this site:

http://support.microsoft.com/kb/199174/en-us

But before you start, I am guessing that I have to do the following:


1 - Verify that DNS is working by going to the main DC and typing:

(NSLookup [FQDN of the DC in remote site, e.g. dc3.domain.local])


2 - Check whether Time Service is synchronizing on the problematic
servers

Could someone please be so kind as to help me out here and tell me what
the problem is? I would greatly appreciate it

Declan D
Click to expand...
Click to expand...
Click to expand...
 
It sounds like for starters the forward and reverse IP addresses are
incorrect. Open up dns and look at your dns records, forward and reverse.
With out DNS properly configured nothing is going to work right. You aren't
using dhcp on your dns servers are you?

Once you have gone through the dns and cleaned up any errors, visit each
machine and do a netdiag /fix (Or reboot each DC) this will re-register all
your dns service records.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


deckydee said:
Thanks for the update guys! - I ran some scans on-site and this is the
output i have from them:

I ran repadmin /showreps and it showed me that there was a replication
problem with only 1 server if though the problem is with three!

I ran repadmin /showism and i have no problem with my sites

The I ran dcdiag /test:intersite /e /q and i go the following errors:

[SERVER1] LDAP connection failed with error 58, The specified server
cannot perform the requested operation..
***Error: The machine, SERVER1 could not be contacted, because of a bad
net response. Check to make sure that this machine is a Domain
Controller. ......................... SERVER1 failed test Connectivity

The error above is for the first server, then this came for the second
server:

Although the Guid DNS name
(5af395b4-6b7e-4d13-a76f-ac072d30eed6._msdcs.XXX) resolved to the IP
address (192.168.10.10), which could not be pinged, the server name
(SERVER2.XXX.XXX) resolved to the IP address (192.168.10.100) and could
be pinged. Check that the IP address is registered correctly with the
DNS server.

The the same as the first error for the third server:

[SERVER3] LDAP connection failed with error 58, The specified server
cannot perform the requested operation..
***Error: The machine, SERVER3 could not be contacted, because of a bad
net response. Check to make sure that this machine is a Domain
Controller. ......................... SERVER3 failed test Connectivity

The more errors came:

*Warning: Remote bridgehead CN-BEI\SERVER1 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted into
the local site BE-Fleurus.
Remote bridgehead CN-BEI\SERVER1 also couldn't be contacted by dcdiag.
Check this server.

*Warning: Remote bridgehead US-JAX\SERVER2 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted into
the local site BE-Fleurus.
Remote bridgehead CN-BEI\SERVER2 also couldn't be contacted by dcdiag.
Check this server.

*Warning: Remote bridgehead US-SEO\SERVER3 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted into
the local site BE-Fleurus.
Remote bridgehead CN-BEI\SERVER3 also couldn't be contacted by dcdiag.
Check this server.

I also got this error:

***Error: The remote site BE-LLN, has no servers that can act
asbridgeheads between the BE-LLN and the local site BE-Fleurus forthe
writeable NC IBA.
Replication will not continue until this is resolved.

I also got this error for SERVER2:

[SERVER2] DsBind() failed with error 1753, There are no more endpoints
available from the endpoint mapper

MORE ERRORS/

***Error: The current ISTG is down in site BE-SEO and further dcdaig
could not contact any other servers in the site that could
take the ISTG role. Ensure there is at least one up DC. Must abandon
inbound intersite replication test for this site.

[SERVER1] LDAP connection failed with error 58, The specified server
cannot perform the requested operation..

[SERVER1] DsBind() failed with error 1722, The RPC server is
unavailable..

[SERVER3] DsBind() failed with error 1753, There are no more endpoints
available from the endpoint mapper..
***Error: The current ISTG is down in site US-JAX and further dcdaig
could not contact any other servers in the site that could take the
ISTG role. Ensure there is at least one up DC. Must abandon inbound
intersite replication test for this site.
***ERROR: There is an inconsistency in the DS, suggest you run dcdiag
in a few moments, perhaps on a different DC.

......................... XXX failed test Intersite


Please help if you can! :o)

Decky Dee

kapil schreef:
the "end point mapper" error ususally occurs when the ports are blocks
you
can use portqry for checking to ports closed.

Also check whether the tcp/ip stack is working fine.

Paul Bergson said:
Try running netdiag, repadmin and dcdiag. Look for fail, error and
warning
errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure
you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /s:DC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt


See for more details

http://www.microsoft.com/technet/pr...Ref/1d4ce93c-54f2-4069-a708-251509c38837.mspx



Endpoint mapper specific KB article
http://support.microsoft.com/?kbid=839880

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no
rights.


Hi,

I am hoping that someone can help me out here as I am in a spot of
bother! :o)

I am consultant that has to go to a company next week because they
are
getting an error in their Windows 2000 Replication Monitor:

'Replication Failure: The reason is: There are no more endpoints
available from the endpoint mapper'

That is not all; when I go to the Directory Service Event viewer I
get
this error as well:

Event Type: Error
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1311
Date: 14-9-2005
Time: 16:05:37
User: N/A
Computer: IBADC00
Description:
The description for Event ID (1311) in Source ( NTDS KCC ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve
this
description; see Help and Support for details. The following
information is part of the event: DC=UPP,DC=XXX.

So as you can imagine, down the right left hand side, I have three
servers that have a red 'X' on them and the rest are ok.

The first thing that I did was I researched the 'Endpoint Mapper'
problem, I was directed to this site:

http://support.microsoft.com/?kbid=839880

I can already tell you at this stage that the correct entries are in
the registry and that Port 135 is listening.

Then after not having much success with that I moved to research the
'1311' problem.

There were several discussion groups about this error, but none that
I
fell can solve my problem.

I also tried this site, but even though it said that it was for
'Troubleshooting error 1311, it does not have the same error as I do.
Even if I did, I don't understand it too well. You see the other
error messages don't have "The local computer may not have the
necessary registry information or message DLL files to display
messages
from a remote computer"

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q214745

My real problem is that because of the two separate errors, I am not
sure if the problem is RPC or KCC!

I also checked this site:

http://support.microsoft.com/?id=244368

And found nothing of much use.

To be 100% sure about what I am doing I have read this site:

http://support.microsoft.com/kb/199174/en-us

But before you start, I am guessing that I have to do the following:


1 - Verify that DNS is working by going to the main DC and typing:

(NSLookup [FQDN of the DC in remote site, e.g. dc3.domain.local])


2 - Check whether Time Service is synchronizing on the problematic
servers

Could someone please be so kind as to help me out here and tell me
what
the problem is? I would greatly appreciate it

Declan D
Click to expand...
Click to expand...
Click to expand...
 
No, our DNS servers are not using DHCP. I will check the Forward
Lookup Zones and Reverse Lookup Zones and see if they are good.

It could be an idea to compare them to the Forward Lookup Zones and
Reverse Lookup Zones of the other servers, as i have four other servers
in four other sites who do not have this problem.

What do you think?
 
They should all be using the same DNS zone. They are aren't they.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top