The problem was the domain settings. Our full domain is Corp.Local.
In the User Domains part of the Web Access Site Properties, we had only Corp.Local, so in the Password Management part Corp.Local was our only option when adding a password server. This isn't correct. I added "Corp" to the User Domains section, and changed password management server to use the "Corp" domain, and it all works now.
Note, i'm still getting this error in the logs when the password management service starts:
In the User Domains part of the web access site properties, we had Corp.Local. Therefore when adding the password management settings, our only domain option was corp.local, which isn't correct.
So i added "corp" to the user domains section, then was able to choose "Corp" as the domain in the password management settings, and it all worked.
Does the Password service actually start succesfully? If so do you get an error message when trying to change the password?
How many domains do you have in your environment? Are they trusted or untrusted (managed)? Does the server that runs the Password manager service (and broker) have access to run LDAP queries against all domains in your forest?
1) Yes, the password manager starts successfully (in that it's running), but as you can see from the logs it doesn't seem happy about it.
2) Yes I get an error, but more on this later
3) We only have 1 domain that we want to reset passwords on (CORP). We have at least one other domain (that I know of..). The password manager box / CB is a member of this CORP domain, and has access to perform LDAP queries against the CORP DCs.
I read that article, and while it doesn't exactly explain our issue, I tried giving the CB computer object full (except for delete) access to the System OU in the CORP domain. This got us a bit further - I'm now getting a different error in the logs:
When I try and change my password on the website, i get this error:
Connection failed (12175).
Nothing is written to the password manager logs when this happens, though. I saw THIS article, and my certificate on the password manager console didn't have a friendly name at all. I added it in, restarted the password manager service, but i still get the same above errors.
nicholas.fletch
31 Posts
1094
1
Posted March 26th, 2014 23:00
This is fixed.
The problem was the domain settings. Our full domain is Corp.Local.
In the User Domains part of the Web Access Site Properties, we had only Corp.Local, so in the Password Management part Corp.Local was our only option when adding a password server. This isn't correct. I added "Corp" to the User Domains section, and changed password management server to use the "Corp" domain, and it all works now.
Note, i'm still getting this error in the logs when the password management service starts:
03/27/14 16:32:57 - 10136 - 27-Mar-2014 16:32:57 - 10136 : 9180 - TrustedForestsLocal::getTrustedForestObjects: ERROR: ADsGetObject(strmForestSystemContainer, IID_IDirectorySearch) failed, hr = 0x8007200a
03/27/14 16:32:57 - 10136 - 27-Mar-2014 16:32:57 - 10136 : 9180 - TrustedForestsLocal::populateTrustedForests: Caught exception: err=-2147016694, msg = Failed to get trusted forest objects
But it doesn't seem to affect the ability of the service to change passwords - everything appears to work.
Thanks,
Nick.