When troubleshooting this kind of script, I like to verify a few things:
1) After this part
' Bind to user object using LDAP port.
Set objUser = objLDAP.OpenDsObject(strPath, _
vbNullString, vbNullString, _
lngAuth)
I like to make sure that I have the user object successfully. It's likely you do else you'd have other issues pop up, but just to be sure, use a wscript echo to pop the objUser's name or some other attribute in the cache to the screen.
Set objUser = objLDAP.OpenDsObject(strPath, _
vbNullString, vbNullString, _
lngAuth)
I like to make sure that I have the user object successfully. It's likely you do else you'd have other issues pop up, but just to be sure, use a wscript echo to pop the objUser's name or some other attribute in the cache to the screen.
2) I also like to remove the on error resume next statement to find out if there's a problem earlier in the script. Sometimes that's needed for normal operation, but for troubleshooting, I like to be thorough and check.
3) Another thing that comes to mind is to check and make sure you have the permissions to reset this particular user's password.
4) Ensure that you have a password that's complex enough to be accepted.
For the last two, check the ADAM logs and increase diagnostic logging if needed.
Al
On 1/31/06, Mr Oteece <[EMAIL PROTECTED]> wrote:
I am using the code sample provided in http://msdn.microsoft.com/library/default.asp?url="" . I have a working SSL cert on the R2 ADAM and all other settings are at the default. I tried to modify the script to use SSL and it fails. I set the port to the SSL port and changed the lngAuth to ADS_USE_SSL | ADS_SECURE_AUTHENTICATION. The SetPassword operation is failing with 8000500D (The directory property cannot be found in the cache).What am I missing in the modification to the script to enable it to run over SSL? Does someone have a working _vbscript_ to update ADAM password over SSL?
