Solved

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

Posted on 2007-04-03
9
468 Views
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.
0
Comment
Question by:steiners
  • 4
  • 3
9 Comments
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
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.

Simon.
0
 

Author Comment

by:steiners
Comment Utility
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.
0
 

Author Comment

by:steiners
Comment Utility
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.
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 
LVL 104

Accepted Solution

by:
Sembee earned 250 total points
Comment Utility
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?

Simon.
0
 

Author Comment

by:steiners
Comment Utility
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. first_last@domain.com??

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?? http://support.microsoft.com/kb/905700/en-us

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

Expert Comment

by:Sembee
Comment Utility
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.

Simon.
0
 

Author Comment

by:steiners
Comment Utility
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.
0

Featured Post

Are end users causing IT problems again?

You’ve taken the time to design and update all your end user’s email signatures, only to find out they’re messing up the HTML, changing the font and ruining the imagery. What can you do to prevent this? Find out how you can save your signatures from end users today.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

744 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

12 Experts available now in Live!

Get 1:1 Help Now