Hi Astro.
Sorry for the delay, I've been away on holiday.
There are two places a hard limit is imposed.
One is in the .NET ActiveDirectory searcher which defaults to 1,000 items, and 1.46 is coded to set the limit to 10,000 before searching.
The other place is in the Active Directory itself, where policies can be used to limit the number of items returned in a single query.
Given that the module hasn't been changed, the most likely answer is that there has been a change to the AD policies, either by the admin, or as a result of an update that has been installed.
I'll take a look at the microsoft site and let you know if I can find anything.
This page:
http://technet2.microsoft.com/WindowsServer/en/library/8196d68e-776a-4bbc-99a6-d8c19f36ded41033.mspx?mfr=true
provides information on how to check and set AD query limits.
Hopefully it can help you work out the problem.
"An operations error occurred" is a generic AD error for "I had a problem"
The error is usually not very informative.
It does suggest that there might be another cause, such as memory exhaustion, or a security error.
Glad to hear it.
Sorry for the delay in responding, some twit spambotted the forums, so I've had to disable anonymous posting, and have been busy cleaning up the posts.
Roger