Can't create SMTP Internet Address on Member server w/Exchagne Tools

Posted on 2007-04-03
Last Modified: 2012-08-13
Working on a member server (2003 standard sp1) with Exchange Tools installed. Exchange environment is 2003 Server Enterprise, w/sp1. On the member server I am unable to create SMTP e-mail addresses in AD.
Message states:
The RPC server is too busy to complete this operation
Facility: Win32
ID no: c00706bb
Microsoft Acitive Directory - Exchange Extension
I can create the addresses from a Exchange Server w/o issue.
Question by:steiners
  • 4
  • 3
LVL 104

Expert Comment

ID: 18845677
Any reason you are still on Exchange 2003 SP1?
Have you updated the member server to the same service pack? All machines with the Exchange tools installed should be treated as full Exchange and kept patched.


Author Comment

ID: 18845995
The only thing i neglected to update on this member server was the Exchange DST patch about 1 month ago. I will apply this update and see if the problem is resolved.

Author Comment

ID: 18849864
The same account works fine on the Exchange SErver. I was thinking this may have been the Exchange DST patch, but I installed that yesterday and have since restarted and still can't add SMTP addresses to accounts.
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

LVL 104

Accepted Solution

Sembee earned 250 total points
ID: 18850080
If the server is up to date, then you would be on Exchange 2003 SP2, not SP1 as you have written above. Which is it?

The DST patch should not affect your ability to modify SMTP addresses on accounts. Exchange should be adding those addresses automatically, but after that, as long as you have the relevant permissions to make changes you should be able to do everything with Exchange tools on a non Exchange server that you can on the server itself.

The error message you are getting would tend to indicate a problem with accessing the domain controllers and not an issue with Exchange itself.

Have you tried this from another machine that is not an Exchange server?


Author Comment

ID: 18850186
Fair enough, let me rephrase. Up to date according to MS would be Exchange 2003 SP2. Up to date (obviously wrong wording) for my Exchange environment (meaning all Exchange servers FE/BE and servers running Exchange tools are all at the same level--Exchange SP1)

Thanks for the clarification on the DST patch. Exchange does add the addresses automatically, but we started adding an additional address manually after the default addresses were built by Exchange. I guess I could add/change my RUS policy to add the new address in.

I don't have another machine just running the Exchange Tools, but I was planning on setting one up to see if the issue still persists. MS has a hotfix for a RPC issue, just didn't want to apply hotfixes. Plus it address a RPC issue at Netlogon??

thanks for you feedback. I really apprecitate it.
LVL 104

Expert Comment

ID: 18850271
Your wording is wrong. Up to date to anyone outside of your environment would mean the latest updates - which as of right now is Exchange 2003 SP2, Windows 2003 SP2 along with a number of updates for Exchange 2003. There have been some updates that change the behaviour of Exchange with regards to permissions on accounts, which if someone says they are up to date external people would therefore take in to account when giving answers.

You are happy to be almost two years behind on updates? Exchange 2003 SP2 is rock solid and there are no known issues with its deployment.
That hot fix is part of Windows 2003 SP2, so I don't think you can get the hot fix separately now.


Author Comment

ID: 18850316
Yeah, I noted that in my last comments that I used the wrong wording.

 I will look into applying Exchange 2003 SP2. Thank you for your feedback.

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
how to add IIS SMTP to handle application/Scanner relays into office 365.

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now