Exchange 2003 FE not starting MSExchangeSA
Hi,
I have an issue where our FE Exchange 2003 server is not delievering public folder emails. It received them perfectly well but then they sit there in the queue and eventually time out. Looking into this shows that the SA and IS services are not
starting. If you try to start them (by starting the IS service) you get the following:
----
Unexpected error There are no more endpoints available from the endpoint mapper. Facility: Win32 ID no: c00706d9 Microsoft Exchange System Attendant occurred.
Event ID 1005 - Src = MSExchangeSA
----
Now, if I try to start the SA service by iteslf it just starts and then immediately stops stating that sometimes services stop if they have nothing to do...
I also get an event (id 1053) with the following text:
----
Windows cannot determine the user or computer name. (Thre are no more endpoints available from the endpoint mapper.) Group policy processing aborted.
----
Now, a quick (or not so quick) search gave a few pointers. I ran one command as suggested: 'portqry -n servername -e 135' and this came back saying that there were 85 endpoints found. How many can I have? How many should be available.
I also checked the entries in the registry as suggested in a MS article (support.ms.com/kb/839880) and added two entries as they were not listed (ncacn_nb_tcp and ncacn_ip_udp) but there has been no change.
I have checked the exchange DBs using eseutil and both public and private are ok but I can't see this being exchange as RCP is outside of this.
Oh, I have removed the AV from this server too.
The FE box is sitting in a DMZ but nothing has changed rule wise to cause an issue.
Anyone have any ideas how to take this forward?
Thanks
there are errors in the event log
February 7th, 2011 11:28am
Hi,
1. Please check if the Port 1025/1026 is blocked on the third
party/Windows firewall. Please turn off the firewall in both Domian controller and Exchange
FE. Then trying to start MSExchangeSA.
2. Reboot the FE server to resolve any potential issue.
3. If the issue persists, please try to telnet the Domain controller on port 1025/1026, what's result?
Gen Lin
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks
Gen Lin-MSFT
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 1:46am
Hi,
Thanks for this. Have tried the above but still no joy. Get the same errors/events.
Have tried telnetting to the DC but get the following response: "Could not open connection to the host, on port 1025: Connect failed", however, I get that same response from a server on the same network segment as the DC.
Thanks for the help.
February 8th, 2011 5:42am
Aah,
Tried the telnet to another DC (the only 2003 we have remaining) and that appears to connect, I just get a thick underscore. This works from both the FE box and the other one I tried from.
We recently updated our DCs to 2008R2, perhaps I should have mentioned that.
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 5:45am