Error during quering\Operations Error

[GoogleCodeExporter]

Hi there,

I've read through the other issues, and it sounds like some have had a similar 
problem, but not quite identical.  When I change the password of a test user on 
the DC that the filter is installed on, i get this error in the log:

"setting write permission for user schools\jfnelson(my account)
write permission for user schools\jfnelson set
error during quering sAMAccountName=bmctest: Operations Error
Change failed for user "bmctest"

As mentioned my account, which has domain admin rights, is running this 
process...with no luck.

Here's my ini file:

[Main]
;name of you google apps
appsDomain=hillwoodhigh.org
;name and password of an administrator accoutn of google apps
appsAdmin=jfnelson@hillwoodhigh.org
appsPasswd=password
;DN and password of an AD user that can write the “hashedPassword” field
ldapAdminBindDn="CN=James Nelson,CN=Users,DC=schools,DC=mnpsk12,DC=local"
ldapAdminPasswd=AD Password
;LDAP query to find your AD users
ldapSearchBaseDn="DC=schools,DC=mnpsk12,DC=local"
;path of sync application executable (GoogleHashUpdater.exe)
processPath=C:\windows\GoogleHashUpdater.exe
;name and password of a local account to use to run the sync application
processUser=schools\jfnelson(has all admin priviledges on DC's)
processPasswd=AD Password
;settings for the proxy to use to connect to google apps
;leave blank if not needed
proxyAddress=
proxyUser=
proxyPassword=


Any ideas?  We're really excited to get this working and do away with a 
problematic "middleman" SSO solution we're currently using.  This seems like 
just what we're looking for, if we can get it going!

Thanks in advance

Original issue reported on code.google.com by JaFNel...@gmail.com on 19 Jul 2010 at 9:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

okay, in the course of my own troubleshooting, I figured out the problem...sort 
of.

I have my base search DN set as the root of the domain.  When it attempts to 
query AD for the user, it returns the ops error.  If I set the base search as a 
particular OU, the one in which the test account is housed, it works fine.  
This is something of a problem, since our users are spread over 4 OUs.  is 
there a way to make it look at more than just a single "base" OU, or does 
anyone have a suggestion for making it capture all 4 of those OUs at once?  I'm 
sooo close!!

Original comment by JaFNel...@gmail.com on 20 Jul 2010 at 2:11

[GoogleCodeExporter]

RC4 should solve this problem, please give us some feedbacks!

Original comment by giorgio....@gmail.com on 21 Jul 2010 at 12:41

• Changed state: Started

[GoogleCodeExporter]

Yes RC4 has fixed this problem for me. 

Original comment by troy.ran...@gmail.com on 22 Jul 2010 at 6:46

[GoogleCodeExporter]

To confirm, RC4 *DID* fix the issue for me!  Thanks so much to giorgio and 
enrico!

Original comment by JaFNel...@gmail.com on 22 Jul 2010 at 8:59

[GoogleCodeExporter]

Original comment by giorgio....@gmail.com on 30 Aug 2010 at 9:58

• Changed state: Fixed