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

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.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.

steinersAuthor Commented:
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.
steinersAuthor Commented:
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.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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?


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
steinersAuthor Commented:
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.
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.

steinersAuthor Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.