Oct 16, 2013 11:13 PM|windump|LINK
I also had this issue and in a production enviroment. The error logged was, "A local error has occured".
This code was attempting to change password of AD users using a service account that had password change priviledge delegated in AD.
(the fact that we are using a delegated service account for this was a whole other solution we had to discover after realizing users with Force Change, or Expired Passwords are unable to change the password with their own user principal, oh well, kinda makes
In any case - the idea behind the fix described by muellech was similar, works in DEV, not in PROD - so I wrapped my AD Actions in the using() statement suggested by SecMaker
Unfortunately, this had no affect...
I was able to resolve the issue by changing the PROD service account username string from a DN format string to a "domain\username" string. Using this username format to establish the PrincipalContext with the delegated service account WORKED! I left the
using() in there... maybe they are doing something?
I do not know why username format matters? FUN STUFF!