Re-indexing fails for regenerating the database and indexes.
Originally Published: 2001-08-17
Article Number
Applies To
Sentry CA 4.5.1
Microsoft Windows NT 4.0
Sun Solaris 2.6
Issue
When running re-indexing, after the temporary .ldif file (e.g. save.ldif or db.ldif) is generated, and trying to regenerate the database and indexes, on Windows NT, it will just hang there and nothing happened, on Solaris, it may hang there or you may get some errors such as the following:
(ERROR) ERROR:
ERROR 1
(ERROR) ERROR:
ERROR 1
Cause
setpin slot=1 password
in your <ca_install_dir>\Xudad\conf\xudad.conf. The problem will occur for re-indexing.
Resolution
You can keep a second copy of xudad.conf with setpin directives disabled, and point to the second copy of xudad.conf for regenerating the db and indexes (it is done through updating 'sentry_reindex.bat' file for Windows NT).
This problem is fixed in Keon Certificate Authority 5.7.
Related Articles
Unable to re-edit a RSA Identity Governance & Lifecycle condition containing IN for a rules definition Number of Views Disaster recovery - Re-imaging a RC Number of Views RSA Identity Governance & Lifecycle server attempts to apply the patch each time with the message "Patch will be (re-)appl… Number of Views AM8.1-Web tier Bootstrap service will not start after re-install Number of Views Access Manager CERTIFICATE authentication fails to re-authenticate after token decryption failed message Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU Disabling weak ciphers using port 1813 in RSA Authentication Manager 8.3 patch 1
Don't see what you're looking for?
