Initialisation of connection pool failed for UACC

[tj_wilkinson2]

Hello, I am receiving the error below when trying to start the portal, has anyone seen this before or have any suggestions? I can get into the configtool and connect to the LDAP without any problems. I can also successfully test the authentication to the LDAP. However when I try to start the portal, I get a message about no connection to the LDAP. Thank you.

~TJ

com.sap.engine.frame.ServiceException: Initialisation of connection poolfailed for UACC

poolname perrigo.com:389_UACC

java.naming.provider.url= ldap://perrigo.com:389/DC%3Dperrigo%2CDC%3Dcom

java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory

java.naming.ldap.version= 3

com.sun.jndi.ldap.connect.timeout= 25000

connection_pool_name= perrigo.com:389_UACC

java.naming.security.principal= CN=SAPPortalAdm,OU=Administration

Users,OU=Administration,DC=perrigo,DC=com

java.naming.security.authentication= simple

java.naming.security.credentials= ******

[EXCEPTION: No connection to the ldap server]

at java.lang.Throwable.<init>(Throwable.java:180)

at java.lang.Exception.<init>(Exception.java:29)

at com.sap.exception.BaseException.<init>(BaseException.java:76)

at com.sap.engine.frame.ServiceException.<init>(ServiceException.java:34)

at

com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:573)

at

com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at

com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at

com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at

com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by:

com.sap.security.core.persistence.datasource.PersistenceException:

Initialisation of connection pool failed for UACC

poolname perrigo.com:389_UACC

java.naming.provider.url= ldap://perrigo.com:389/DC%3Dperrigo%2CDC%3Dcom

java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory

java.naming.ldap.version= 3

com.sun.jndi.ldap.connect.timeout= 25000

connection_pool_name= perrigo.com:389_UACC

java.naming.security.principal= CN=SAPPortalAdm,OU=Administration

Users,OU=Administration,DC=perrigo,DC=com

java.naming.security.authentication= simple

java.naming.security.credentials= ******

[EXCEPTION: No connection to the ldap server]

at java.lang.Throwable.<init>(Throwable.java:195)

at java.lang.Exception.<init>(Exception.java:41)

at com.sap.security.api.UMException.<init>(UMException.java:53)

at

com.sap.security.core.persistence.datasource.PersistenceException.<init>(PersistenceException.java:16)

at

com.sap.security.core.persistence.datasource.imp.LDAPPersistence.init(LDAPPersistence.java:464)

at

com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:302)

at

com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)

at

com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:570)

... 6 more

[MichaelShea]

Hi TJ,

I am not much of an expert on LDAPs, but the newer configuration UI in 7.0 enables you to test the connection. It seems that your connection is not working from the output you are getting. Reconfigure the UME to database only and try this procedure:

http://help.sap.com/saphelp_nw04s/helpdata/en/12/7678123c96814bada2c8632d825443/frameset.htm

-Michael

[tj_wilkinson2]

I am able to successfully test the connection when the portal is down - using the config tool.

This has been working for us for months, and then all of the sudden when we tried to restart the portal it fails. We haven't changed the configuration in the portal at all, and we're trying to track down if any LDAP configuration was changed.

I will look at the information in the link you provided to see if this will help isolate the error. Thank you.

~TJ

[MichaelShea]

Sorry, I thought you were setting up a system.

-Michael