Unable to load portal page but dispatcher and server0 are running

[Former Member]

Hi Experts,

Need your advice please.

We're not able to launch portal page for our QA portal system eventhough as seen in jcmon the dispatcher and server0 are running.

When I call up the portal page http://XX.XX.XXX.XX:52600/irj/portal I got error: The connection has timed out.

This is on dialog server which runs on Linux.

The portal page on CI/DB server works fine.

From my inexpert eyes, I found no fault in dev_dispatcher and dev_server0.

But I saw this in std_server0.out:

Error 1:

SAP J2EE Engine Version 6.40   PatchLevel 105424.313 is starting...

Error occurred while preloading classes of security providers from jre/lib/ext f

older: java.util.zip.ZipException: No such file or directory

Loading: LogManager ... 1772 ms.

I'm not sure if this is considered an error as further down, it mention:

ServiceManager started for 42607 ms.

Framework started for 51069 ms.

SAP J2EE Engine Version 6.40   PatchLevel 105424.313 is running!

PatchLevel 105424.313 August 15, 2006 18:56 GMT

However there's another error nearing the end of the file:

Error 2:

Mar 25, 2012 4:04:14 AM         com.sap.security.core.persistence [Thread[JMSPolling,5,SAPEngine_Application_Thread[impl:3]_Group]] Fatal: No connection to the ldap server, recheck configuration or availability of directory server

While browsing scn forums, another guy encountered the same error as Error 1, and the recommendation is to check on note Note 965451 - Error, while preloading security provider classes however the guy's issue is he's not able to bring up j2ee engine altogether while mine appears to be up & running. Thus I'm not sure if the note is relevant to my issue.

Any ideas/feedback are appreciated.

Thanks in advance for taking the time to go through this message

Regards,

[Former Member]

Hi,

The global variables were being overwritten by the local variables.  In the configtool for server service com.sap.security.ume.service set the correct ldap password and in the instance server for this service delete any local defined variables for ldap password and that should fix the problem.

in the configtool for UME settings you'll notice in the bottom half of the screen the details of any customized variables.  So make sure you are in the global configuration tab and edit your settings there, this way when you restart the engine the server variables will be overwritten by the correct config.

Regards,

Vipin