Troubleshooting
Problem
After upgrading to DB2 Content Manager V8.4, you click the resource manager node from the system administration client. You then get the following error: DGL5162A: System Managed Storage (SMS) request to resource manager failed. However, you are sure that LDAP is not enabled in DB2 Content Manager. This setting can be verified from the system administration client. On the menu bar, click Tools -> LDAP Configuration. If LDAP is not enabled, the check box "Enable LDAP" is cleared.
Symptom
The following exceptions are written in the resource manager log:
[25/11/08 17:19:37:437 EST] 00000026 SystemOut O ICMRM:ERROR 2008-11-25 06:19:37.375000 context: [WebContainer : 0] - ICM9827: Naming exception : {0} - authenicate(RMLDAPValidator.java:318)
javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece ]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3000)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2946)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2747)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2661)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:298)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:190)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:208)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:81)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:679)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:259)
at javax.naming.InitialContext.init(InitialContext.java:235)
at javax.naming.InitialContext.<init>(InitialContext.java:209)
at com.ibm.mm.icmrm.util.RMLDAPValidator.authenicate(RMLDAPValidator.java:251)
at com.ibm.mm.icmrm.rmapi.sms.RMSMSDatastore.logon(RMSMSDatastore.java:1336)
at com.ibm.mm.icmrm.communication.RMSMSServer.doLogon(RMSMSServer.java:390)
at com.ibm.mm.icmrm.communication.RMSMSServer.handleRequest(RMSMSServer.java:293)
at com.ibm.mm.icmrm.communication.ICMResourceManager.handleRequest(ICMResourceManager.java:665)
at com.ibm.mm.icmrm.communication.ICMResourceManager.doPost(ICMResourceManager.java:573)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at com.ibm.mm.icmrm.communication.ICMResourceManager.service(ICMResourceManager.java:541)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:907)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:696)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:641)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:475)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3107)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:238)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1425)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:92)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:274)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:984)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:600)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1812)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:193)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:725)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:847)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
[25/11/08 17:19:37:437 EST] 00000026 SystemOut O ICMRM:ERROR 2008-11-25 06:19:37.390000 context: [WebContainer : 0] - INVALID_LOGON_PASSWORD_OR_USER: <userName>RMADMIN</userName>
<password>********</password>
<newPassword>********</newPassword> - logon(RMSMSDatastore.java:1340)
[25/11/08 17:19:37:453 EST] 00000026 SystemOut O ICMRM:ERROR 2008-11-25 06:19:37.390000 context: [WebContainer : 0] - com.ibm.mm.icmrm.exceptions.RMAPISecurityException: ICM9742: Resource manager administrative logon failed in SMS-logon order. - doLogon(RMSMSServer.java:392)
com.ibm.mm.icmrm.exceptions.RMAPISecurityException: ICM9742: Resource manager administrative logon failed in SMS-logon order.
at com.ibm.mm.icmrm.rmapi.sms.RMSMSDatastore.logon(RMSMSDatastore.java:1341)
at com.ibm.mm.icmrm.communication.RMSMSServer.doLogon(RMSMSServer.java:390)
at com.ibm.mm.icmrm.communication.RMSMSServer.handleRequest(RMSMSServer.java:293)
at com.ibm.mm.icmrm.communication.ICMResourceManager.handleRequest(ICMResourceManager.java:665)
at com.ibm.mm.icmrm.communication.ICMResourceManager.doPost(ICMResourceManager.java:573)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at com.ibm.mm.icmrm.communication.ICMResourceManager.service(ICMResourceManager.java:541)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
Cause
In DB2 Content Manger Version 8.4, the icmrm.properties configuration file is not used. Instead, a new RMCONFIGURATION table is used to keep resource manager configuration information. Therefore, when you are upgrading DB2 Content Manager V8.3 to DB2 Content Manager V8.4, the content in icmrm.properties is written into the RMCONFIGURATION table.
In your DB2 Content Manager V8.3 installation, you enabled the LDAP feature. Now in your DB2 Content Manager V8.4 installation, the resource manager gets this information from the old icmrm.properties file and inserts a row into the RMCONFIGURATION table, such as in the following example:
| PROPERTY | VALUE |
| CMCOMMON_LDAP | ENABLED |
The value for property "CMCOMMON_LDAP" is "ENABLED", which means that LDAP is enabled. Therefore, you will get the error described in this technote.
Resolving The Problem
1. Open the IBM DB2 command line processor and run the following command, where RMDB is your resource manager database, rmadmin is your resource manager administrator ID, and your_password is your resource manager password:
db2 connect to RMDB user rmadmin using your_password
2. Run the following command:
db2 update RMCONFIGURATION set propertyvalue='DISABLED' where property='CMCOMMON_LDAP'
3. Restart the DB2 Content Manager resource manager application.
Was this topic helpful?
Document Information
Modified date:
25 July 2019
UID
swg21328962