{"id":1992,"date":"2010-08-04T17:15:46","date_gmt":"2010-08-04T21:15:46","guid":{"rendered":"http:\/\/onlineappsdba.com\/index.php\/2010\/08\/04\/osr-11g-account-management-failed-with-error-initialization-of-accounts-has-failed-contact-the-administrator-of-the-registry\/"},"modified":"2010-08-04T17:15:46","modified_gmt":"2010-08-04T21:15:46","slug":"osr-11g-account-management-failed-with-error-initialization-of-accounts-has-failed-contact-the-administrator-of-the-registry","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2010\/08\/04\/osr-11g-account-management-failed-with-error-initialization-of-accounts-has-failed-contact-the-administrator-of-the-registry\/","title":{"rendered":"OSR 11g : Account Management failed with Error ” Initialization of accounts has failed contact the administrator of the registry”"},"content":{"rendered":"

<\/a><\/p>\n

.
\nSteps to replicate Issue<\/strong> :<\/p>\n

1. <\/strong>Login to OSR (Oracle Service Registry) 11g Control http:\/\/servername:7101\/registry\/uddi\/web<\/strong>\u00a0 (7101 is default port for OSR 11g deployed on WebLogic Server)
\n2.<\/strong> Click on Registry Management<\/strong> -> Click on Account Management
\n_________________________________<\/strong><\/p>\n

Initialization of accounts has failed. For help please contact the administrator of the registry.
\n<\/font>____________________________________<\/font><\/p>\n

.<\/p>\n

<\/a><\/p>\n

.<\/p>\n

Setup:
\n<\/strong>OSR 11g deployed on WebLogic Server with Oracle Database as database repository and Integration with LDAP (OID) as Authentication Provider. \u00a0For list of supported Application Servers and database for OSR 11g check my post here<\/a><\/p>\n

.<\/p>\n

Possible Reasons for this issue<\/u><\/strong><\/p>\n

1.<\/strong>Unable to connect to OSR repository (Database) from\u00a0applications server (WebLogic in my case)
\n2.<\/strong> If you have integrated OSR with LDAP server (OID, AD, Sun Directory)\u00a0for authentication then there could be conflict with ADMIN<\/strong> user in OSR<\/strong> and similar user in LDAP Server<\/strong>.
\n3.<\/strong> Unable to connect to OID (LDAP) server<\/p>\n

.<\/p>\n

Where are logs in OSR<\/u><\/strong><\/p>\n

There are two main logs install time log ($INSTALL_DIR\/log – install.log & setup.log) and run time log (depending on application server on which you deploy OSR). For OSR 11g deployed on WebLogic logs will be at following locations<\/p>\n

a)<\/strong>$DOMAIN_HOME\/ servers\/ osr_server1\/ logs\/
\nb)<\/strong>$DOMAIN_HOME\/ servers\/ osr_server1\/ tmp\/ _WL_user\/ registry\/ [random_number]\/ public\/ serviceRegistry_errorEvents.log<\/strong> &\u00a0serviceRegistry_logEvents.log<\/strong><\/p>\n

Error in serviceRegistry_errorEvents.log<\/u><\/strong><\/p>\n

Checked in logs and following was recorded in Service Registry Error Event Log
\n_______________ <\/u><\/strong><\/p>\n

<2010-03-19 08:55:47,778> – <ID1279526140038> <ERROR> <USR4023> account.com.systinet.uddi.account.ldap.LdapBackendImpl – It is impossible to open connection to LDAP server. – EXCEPTION: javax.naming.OperationNotSupportedException: [LDAP: error code 53 – Password Policy Error :9001: cn=orcladmin : Your account is locked. Contact your OID administrator.]
\njavax.naming.OperationNotSupportedException: [LDAP: error code 53 – Password Policy Error :9001: cn=orcladmin : Your account is locked. Contact your OID administrator.]<\/font>ERROR: com.systinet.uddi.webui.WebUIRawService – Web Framework exception \u00a0EXCEPTION: com.systinet.uddi.webui.WebUIException: (18003) UDDI error occurred. javax.servlet.ServletException: com.systinet.uddi.webui.WebUIException: (18003) UDDI error occurred.
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 at com.systinet.webfw.servlet.WebFilterChain.doFilter(WebFilterChain.java:42)
\nERROR: com.systinet.uddi.webui.WebUIRawService –
\nEXCEPTION: Initialization of accounts has failed. For help please contact the administrator of the registry.
\n____________________<\/font>.<\/p>\n

<\/font>Issue Verification <\/u><\/strong><\/p>\n

<\/u><\/strong>As per logs it\u00a0was clear that user cn=orcladmin<\/strong>(used for OSR integration ) was locked. To verify I executed ldapbind on OID server.<\/p>\n

$ORACLE_HOME\/bin\/ldapbind -p 389 -D cn=orcladmin -w [orcladmin_password]<\/strong><\/p>\n

ldap_bind: DSA is unwilling to perform
\nldap_bind: additional info: Password Policy Error :9001: cn=orcladmin : Your account is locked. Contact your OID administrator.
\n<\/font>
\n\u00a0<\/p>\n

.<\/p>\n

Unlock Superuser (cn=orcladmin) in OID using oidpasswd<\/u><\/strong>\u00a0<\/p>\n

OIDPASSWD<\/strong>is command to unlock or reset super\u00a0user (cn=orcladmin) account in OID. More information here<\/a><\/p>\n

\u00a0Run below command in OID node<\/p>\n

export ORACLE_INSTANCE=\/u01\/oracle\/fmw11g\/oid1 <\/strong>
\nexport ORACLE_HOME=\/u01\/oracle\/fmw11g\/Oracle_IDM1
\n<\/strong>$ORACLE_HOME\/ldap\/bin\/oidpasswd connect=[tns_alias] unlock_su_acct=true<\/strong><\/p>\n

.<\/strong>
\nOIDPASSWD failed<\/u><\/strong><\/p>\n

OIDPASSWD command failed with below error<\/p>\n

ERROR * gsldpuUnlockSuAccount * ORA-12154:ORA-12154: TNS:could not resolve the connect identifier specified
\n\u00a0encountered Error in unlocking OID super user account.
\n<\/font><\/p>\n

\u00a0I got similar error even after creating\u00a0tnsalias in $ORACLE_HOME\/network\/admin\/tnsnames.ora. \u00a0Finally I found Oracle Support note 882360.1\u00a0which suggested that in 11g OID, tns alias is picked up\u00a0from $ORACLE_INSTANCE\/config\/tnsnames.ora<\/strong><\/font> <\/font><\/font><\/p>\n

Finally issue fixed by “unlocking orcladmin account and restarting WebLogic Server Managed Server (osr_server1) hosting OSR”.<\/strong><\/p>\n

.\u00a0<\/p>\n

.
\nRelated\/References Oracle My Support Notes<\/strong><\/u><\/p>\n