Record update problem - L-Space Design Forums

Welcome to L-Space Design Forums Sign in | Join | Faq

DotNetNuke Modules

Started by Astro at 01-03-2007 13:17. Topic has 4 replies.

Sort Posts:

01-03-2007, 13:17

Astro

Joined on 01-04-2007
Posts 2

Record update problem

After having the LDAP Directory module work well for weeks, suddenly I'm finding that the records returned max out at 7,000 exactly (though it once was and should be more...) and people recently added to AD and who meet the group query criteria no longer make it into the results. I'm using version 01.46.00.

The scheduled updates complete "successfully", though when I run the Test link from inside the module View Options page I get an error on the page: "An operations error occurred" with no other info and the record count is 7,000.

What can I do to diagnose the problem? Thanks.

Report

01-15-2007, 22:58

admin

Joined on 06-16-2005
Auckland, New Zealand
Posts 62

Re: Record update problem

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.

Roger Willcocks
Software Engineer MSCD.NET
L-Space Design
http://www.l-space-design.com/
"Putting your experience to work"

Report

01-15-2007, 23:07

admin

Joined on 06-16-2005
Auckland, New Zealand
Posts 62

Re: Record update problem

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.

Roger Willcocks
Software Engineer MSCD.NET
L-Space Design
http://www.l-space-design.com/
"Putting your experience to work"

Report

01-17-2007, 13:14

Astro

Joined on 01-04-2007
Posts 2

Re: Record update problem

Roger,

Thanks for the tips. Turns out there was a bad page file on the domain controller (which eventually crashed completely) -- switiching to another server resolved the problem.

Report

02-06-2007, 1:58

admin

Joined on 06-16-2005
Auckland, New Zealand
Posts 62

Re: Record update problem

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

Roger Willcocks
Software Engineer MSCD.NET
L-Space Design
http://www.l-space-design.com/
"Putting your experience to work"

Report

L-Space Design ... » L-Space Design ... » DotNetNuke Modu... » Record update problem