[DFC_BOF_GLOBAL_REGISTRY_UNAVAILABLE] Unable to connect to the global registry xxxxxx

vikas.chaudhary@us.pwc.com

I recently came across an issue in which inline users not able to login to application, however ldap users were not impacted.

I searched the docbase logs and found out below error:

"[DFC_BOF_GLOBAL_REGISTRY_UNAVAILABLE] Unable to connect to the global registry xxxxxx"

After resetting the dm_bof_registry password and restart app server resolved this issue.

When i checked with EMC, they told that dfc.keystore file might have crashed.

Can someone tell me in what case dfc.keystore file could crash?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Anytime you change passwords, you need to delete dfc.keystore, so that the Content Server can generate a new one with the new password. I would not have used the term "crashed" as much as the keystore file was out of sync.

All comments

Anytime you change passwords, you need to delete dfc.keystore, so that the Content Server can generate a new one with the new password. I would not have used the term "crashed" as much as the keystore file was out of sync.

vikas.chaudhary@us.pwc.com

Thanks for replying. But we had to change the password because we were getting the error in the docbase logs. And all the inline users were not able to login. They were also getting the same error while login to webtop.

Are there any more scenarios where this error could come?

Dont know. Keystore shouldnt get out of sync unless you change the password for the install owner or bof registery user.

vikas.chaudhary@us.pwc.com

Yeah that may be the case during OS patching(however i am not aware if that happened). But the issue got resolved agter manually enter the password of dm_bof_registry user and restart of websphere application server.