Link to home
Start Free TrialLog in
Avatar of mrsmileyns
mrsmileyns

asked on

The administrative limit for this request was exceeded Active Directory Error

Running Windows 2003 and 2000 DC's in a multi site environment.  For 1 specific user I have noticed when we try to move, change the password, or perform any other type of AD action on the object I receive the error "The administrative limit for this request was exceeded."  It seems to be only this user the issue is happening to.  I have searched this forum as well as the net and have not been able to find any useful information other than delete and recreate the user object.  Any ideas?
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

There is some comment on http://hellomate.typepad.com/exchange/2003/09/message_filteri.html but I have to say I'm not much wiser after reading it
Avatar of mrsmileyns
mrsmileyns

ASKER

hmm...I understand what it is saying although I am not sure if this user has 850+ blocked senders in their junk mail filter since we are using spam filtering via Exchange - I am a bit skeptical this is the cause but its worth a try - thanks
I may have seen this when there was a mail disk quota on someones mail box was exceded. When the quota was reached, the person's mail account would no longer work. I am looking at this and haven't determined if this even pertains to your situation. I don't know if you are working within a mail server environment.


Just gueswork. I hope it helps.
ASKER CERTIFIED SOLUTION
Avatar of mrsmileyns
mrsmileyns

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
I have seen this occur when the Notes connector for Exchange 2003 is being used.  Check the user's email addresses properties (in ADUC) for too many NOTES: proxy addresses.  Also look for event ID 2008 in the Directory Service event log.  For the fix refer refer to Microsoft  KB 913676.