This solution for error works also for 6.5 content server.
Symptoms
installed multiple docbases without problem, but first (global registry) docbase got corrupted (in this case due to DAB) and was uninstalled. This caused dm_bof_registry issues for all the current docbases and any others that were installed.
Cause
Removal of the global registry repository causes an issue with the dm_bof_registry user on all the docbases as it is no longer in existance.
Resolution
change the dm_bof_registry to point to one of the other docbases is the best resolution. But, in this instance the customer removed all the docbases already and was unable to install any more docbases due to the dm_bof_registry install step was hanging on any new install (which was cancelled, and thus the docbase had no dm_bof_registry user).
Cleaned up the system again, and this time when the server configure step got to the Global Registry step selected "Do Later"...the install continued this time. After the install verified taht the dm_bof_registry account existed, turned it active (set user_state to 0). Then did the java password encryption (after setting the dm_bof_registry password), and then updated the dfc.properties correctly. At this point DA could be installed correctly and all future docbases installed correctly on the server.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment