Main Topics
Browse All TopicsEverything with my mail server was going fine until the other day when I installed Windows 2003 Server SP1. Now my Exchange System Attendant service fails to start either upon booting or manually trying to start it.
I checked the Recipient Update Services DC and it was my old server. I changed it to my new server, did a Rebuild and Update Now on both records. The server is multi-homed but the second NIC has been disabled since this stuff started.
I get the following 4 errors in order of occurrence:
Event ID: 9317
Source: MSExchangeSA
Description: Failed to register Service Principal Name for exchangeRFR; error code was c00706d9
Event ID: 9317
Source: MSExchangeSA
Description: Failed to register Service Principal Name for exchangeMDB; error code was c00706d9
Event ID: 1005
Source: MSExchangeSA
Description: Unexpected error There are no more endpoints available from the endpoint mapper. Facility: Win32 ID no: c00706d9 Microsoft Exchange System Attendant occurred.
Event ID: 9152
Source: MSExchangeSA
Description: Microsoft Exchange System Attendant reported an error '0xc1034a70' in its DS Monitoring thread.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I checked out Computer Management and looked at the Administrators group. I have administrator and an orphaned guid. I tried adding the domain/administrator username, but I got the following message and it doesn't apply (similar to 3rd event log from first post):
There are no more endpoints available from the endpoint mapper.
I am at the console now for another 1-2 hours trying various things, so any ideas would be welcome now :).
Thanks
Business Accounts
Answer for Membership
by: eatmeimadanishPosted on 2005-06-23 at 07:38:25ID: 14284486
As per Microsoft: "Explanation: This event is indicating a failure to register SPN. This may prevent Outlook/OWA clients, running in a Kerberos-Only network, to get authenticated and logon to their mailbox. SPN "service principal name" gives a service running on a particular machine a global identity that allows it to authenticate via Kerberos. Exchange System Attendant is responsible for the SPN registrations of Exchange services.
User Action: SPNs are used by clients like Outlook to authenticate with the server. Verify that Outlook clients are able to log on and read mail, if not, try to restart MSExchangeSA. If that does not work, call Microsoft Product Support Services.
Users can also work around this problem by using a Windows utility called "setspn" that allows manual registration of SPNs on a machine. Exchange only registers "exchangeRFR" and "exchangeMDB" SPNs, which are used for Outlook authentication. By default, only domain administrators and local system can register SPNs. In some cases, Exchange administrators do not have any domain administrator rights; therefore they have to ask the domain administrator to run setspn".