I am seeing some issues on an AD driver that has password sycnchronized
both directions. When setting a password from an AD workstation in the
domain, I get a "cannot set password via platform call". Most of the
time the error code is 2245, this time it was 8206. The password does
meet the complexity rules.

What I see in the trace is that the password is being cleared. What
exactly is that doing? If it is null'ing out the password, is that why
the error is being thrown? After this error the password actually does
get set and sent to the Vault.

DirXML Log Event -------------------
Driver = \VAULT-TREE\acme\idmset\ActiveDirectory
Thread = Publisher Channel
Level = success
Message = <operation-data>
<password-publish-status>
<association>752e22e407fdab498f447bb442c1924f</association>
</password-publish-status>
</operation-data>
<application>DirXML</application>
<module>ActiveDirectory</module>
<object-dn>CN=user1,OU=People,DC=domain1,DC=domain2,DC=dom ain3
(acme\com\primary\people\user1)</object-dn>
<component>Publisher</component>
DirXML: [06/03/10 13:25:35.41]: ADDriver:
MadPublisherPassSync:rocessPassSyncEntries() clearing user user1
password
DirXML: [06/03/10 13:25:35.46]: Loader: Calling
subscriptionShim->execute()
DirXML: [06/03/10 13:25:35.53]:
DirXML Log Event -------------------
Driver = \VAULT-TREE\acme\idmset\ActiveDirectory
Thread = Subscriber Channel
Level = error
Message = Could not set password via platform call. Err=8206


--
jeff@linux1:~> glxgears
120308 frames in 5.0 seconds = 24061.553 FPS
------------------------------------------------------------------------
jedijeff's Profile: http://forums.novell.com/member.php?userid=4732
View this thread: http://forums.novell.com/showthread.php?t=412310