Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
Hi,
We have attempted to clone a staging Windchill to Production and along with server names etc all has worked out except for the Enterprise LDAP which currently produces the below exception when trying to search the user directories.
Page could not respond: /ptc1/principalpicker/principalPickerCD_step
[LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1]
The credentials are tested and valid wtihin the Enterprise LDAP.
So, I suspect that the encrypted values stored in mapcredentials may need to be re-created?
If there is any insight that anyone can offer, that would be good.
Hi Kevin,
I've done that many times when testing our my development/test mirrored clone with new OS and infrastructure to be the new produciton when replacing horrible Winddows OS with Red Hat Linux and old infrastructure with server blades.
Did you try exporting the Windchill LDAP only using Windows Wordpad/Word try searching for the string DC=<old host=" alias=" name="> and <old host=" alias=">. "dot" after host name. (case sensitive)
You can try replacing them with the new server name then do a delete then import. Make sure you backup the export first. if you follow the rehost guide, you should not need to do this. Also, did you properly change apache authentication.
Good luck,
Patrick
In Reply to Kevin Sperring:
Hi,
We have attempted to clone a staging Windchill to Production and along with server names etc all has worked out except for the Enterprise LDAP which currently produces the below exception when trying to search the user directories.
Page could not respond: /ptc1/principalpicker/principalPickerCD_step
[LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1]The credentials are tested and valid wtihin the Enterprise LDAP.
So, I suspect that the encrypted values stored in mapcredentials may need to be re-created?
If there is any insight that anyone can offer, that would be good.
Hi Kevin,
Make sure you "clone" is a true mirror of production:
When ready to switch, don't forget:
Have fun,
Patrick
In Reply to Patrick Chin:
Hi Kevin,
I've done that many times when testing our my development/test mirrored clone with new OS and infrastructure to be the new produciton when replacing horrible Winddows OS with Red Hat Linux and old infrastructure with server blades.
Did you try exporting the Windchill LDAP only using Windows Wordpad/Word try searching for the string DC= and . "dot" after host name. (case sensitive)
You can try replacing them with the new server name then do a delete then import. Make sure you backup the export first. if you follow the rehost guide, you should not need to do this. Also, did you properly change apache authentication.
Good luck,
Patrick
In Reply to Kevin Sperring:Hi,
We have attempted to clone a staging Windchill to Production and along with server names etc all has worked out except for the Enterprise LDAP which currently produces the below exception when trying to search the user directories.
Page could not respond: /ptc1/principalpicker/principalPickerCD_step
[LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1]The credentials are tested and valid wtihin the Enterprise LDAP.
So, I suspect that the encrypted values stored in mapcredentials may need to be re-created?
If there is any insight that anyone can offer, that would be good.
Hi Kevin,
Since you are using Windchill 9.#, 8.# and 7.#, context names were stored in apheliion/WindchillDS LDAP. You have to do a complete mirror of both the database and Windchill LDAP. You may not need the vaults as of yet, which will cause vault read folder issues but not this.
Is your "clone" a complete mirror of the entire production system including the database?
It sounds like you are missing some entries in your LDAP of contexts that is not in sync with Windchill database.
Patrick
Hi Kevin
Which is why in the pre 9.1 M050 days. (I could be off by a few service packs). It was very imparative to have your Windchill LDAP backed up at the same time as your database in production. If they are not in sync, you can have issues where you can not start up Windchill from a recovery, restore, mirror or disaster recovery.
I still follow that lesson learned. I had experienced in the past where some admins and developers went to far with LDAP and I had to recover.
Just take a good export of both the production LDAP and database at exact the same time. Sometimes I've seen this error when someone has created acontext or renamed acontext and it is not in sync with the backup of LDAP. I could be wrong but it really resembles this issue.
Good luck,
Patrick
In Reply to Patrick Chin:
Hi Kevin,
Since you are using Windchill 9.#, 8.# and 7.#, context names were stored in apheliion/WindchillDS LDAP. You have to do a complete mirror of both the database and Windchill LDAP. You may not need the vaults as of yet, which will cause vault read folder issues but not this.
Is your "clone" a complete mirror of the entire production system including the database?
It sounds like you are missing some entries in your LDAP of contexts that is not in sync with Windchill database.
Patrick