That's very odd. Could you attach your LDAP XML to this ficket?
Also, could you confirm whether or not you are running Cascade
Server in a load balanced environment, or if there may be another
instance of Cascade running somewhere? Please let me know what you
It was the clone. We use this method often, of creating a clone
and then banging on that for testing. Part of our standard
procedures is to disable all cron jobs when we first start up the
clone. Just didn't think about Cascade running its own scheduled
I've always wanted to be able to schedule the LDAP sync myself.
Doing this in cron would be great.