Re: Wierd RUS problem
From: Ben Winzenz [Exchange MVP] (ben_winzenz_at_NOSPAMdotmessageonedotcom)
Date: 09/22/04
- Next message: Susan: "Re: How to restore..."
- Previous message: Kurt: "Re: MX Records not showing correctly"
- In reply to: Chris Frank: "Re: Wierd RUS problem"
- Next in thread: Ben Winzenz [Exchange MVP]: "Re: Wierd RUS problem"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 22 Sep 2004 16:25:30 -0500
How many objects is RUS trying to modify? More than 1000? I'm just
throwing out bones here, but if so, have you tried modifying the max number
of ldap objects returned by a query? Default is 1000 on W2K (and I presume
W2K3, though I am checking). If this is the case, post back and I can
include steps for how to modify the max # of results. Again, I have no idea
if that is actually the issue or not, but I saw a post on another forum that
sounded related. Might be worth a shot.
-- Ben Winzenz Exchange MVP "Chris Frank" <cfrank@spheretechinc.com> wrote in message news:f384433d.0409221310.19f3a124@posting.google.com... >I am having the exact same error. I too have applied SP1 to my > Exchange 2003 servers but the errors still exist. Have you ever > resolved this issue? > > This is what we are getting: > > Event Type: Error > Event Source: MSExchangeAL > Event Category: LDAP Operations > Event ID: 8270 > Date: 9/22/2004 > Time: 3:21:50 PM > User: N/A > Computer: LTEXCH1A > Description: > LDAP returned the error [b] Administration Limit Exceeded when > importing the transaction > dn: <GUID=81D57A98E09FFF4CA1DDDFCA878F8A78> > changetype: Modify > showInAddressBook:add:CN=Default Global Address List,CN=All Global > Address Lists,CN=Address Lists Cont... > msExchALObjectVersion:282697 > objectGUID:81D57A98E09FFF4CA1DDDFCA878F8A78 > - > DC=ourdomain,DC=net > > > "John" <j.bishop@geminimedical.com.au> wrote in message > news:<22a901c49df2$a5ab9b30$a301280a@phx.gbl>... >> Thanks Bill... Sadly, SP1 didn't help in my situation. >> Anyone else got any ideas? :) >> >> >> >-----Original Message----- >> >I had this same problem for quite a while, Exchange 2003 >> SP1 resolved the >> >issue on our servers. >> > >> >bill
- Next message: Susan: "Re: How to restore..."
- Previous message: Kurt: "Re: MX Records not showing correctly"
- In reply to: Chris Frank: "Re: Wierd RUS problem"
- Next in thread: Ben Winzenz [Exchange MVP]: "Re: Wierd RUS problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|