Showing results for 
Show  only  | Search instead for 
Did you mean: 

Broken scanning of AD

Engaged Sweeper III
We seem incapable of scanning our domain anymore. It happened apparently a while ago, somewhere in September (judging from the completed scan indicators under Scan Targets), but I don't have any idea why that might be, as we haven't made any updates or configuration changes. We've now tried recreating targets, credentials, etc. - but nothing happens.

I now enabled debugging on the log and restarted the server, where it's making references to something that hasn't been part of our setup for months. It's as if there's a cache somewhere, that it is still processing, even when we try to clear the queue or restart the service. It also, after having been up and running for an hour, mentioned deleting a user that was no longer found in AD - but that user was never part of the OUs we're filtering on, so why he would even be processed, I have no clue whatsoever.

I even reinstalled the service and the website, no dice.

Clicking "Clear Queue" shows that it's processing, but it never stops. The indicator just keeps going around.

As far as I can tell, there's a queue for the AD somewhere, which is not cleared with restarting the service, and it's stuck in it somehow. Any ideas?

Engaged Sweeper
Did you ever resolve this....I have a similar issue which I've posted about.