Application Broker - Initialization failed

[Former Member]

Hi,

after restarting the portal, i found the following errors in the std_server0.out:

May 5, 2006 7:26:51 AM com.sap.portal.prt.runtime [SAPEngine_Application_Thread[impl:3]_34] Fatal: [Portal.init] Application Broker - initialization failed

May 5, 2006 7:27:01 AM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_13] Fatal: Exception while starting: sap.com/com.sap.netweaver.bc.rf

May 5, 2006 7:27:02 AM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_13] Fatal: Exception while starting: sap.com/com.sap.netweaver.bc.sf.service

When I try to access the portal via browser I get the following message:

Servlet [prt] will be unavailable for undefined time.

Details: javax.servlet.UnavailableException: Initialization of Dispatcher failed The ID of this error is

Exception id: [001125081EFA0045000000280006909E00041303CE3C4115].

Any ideas how to resolve this?

regards,

Thomas.

[Former Member]

Did anybody find a solution for this issue? We are running into the same error.

[Former Member]

Hi,

I want to ask if someone has find a solution for our problem?

Kind Regards,

Mischa

[Former Member]

I too have exactly the same problem except after I had installed JDI and applied template configuration. the problem started after applying the template configuration

JDI-DTR-and-CBS.zip

If anybody find any solution, Please post.

Thanks

BasisYM

[Former Member]

Hi,

any news on that topic? I have the same effect in my EP 6.0 on WAS Java 640. After installing the latest support packages on the Java engine, I get exactly the same error as described above and I cannot login to the portal anymore.

Which log files (name / location) could be interesting to locate the problem?

Many thanks,

Michael

[Former Member]

Hi Michael,

if the engine doesn't start, check the dispatcher and server log files in the "work" directory.

Regards,

Pascal

[Former Member]

Hi Pascal,

it seems the engine is up and running. I had access to the system until I patched it to the highest current level. The patch is needed in order to access the portal content, which didnt work in the first place.

The message in the browser is:

Servlet [prt] will be unavailable for undefined time.

Details: javax.servlet.UnavailableException: Initialization of Dispatcher failed

The server-logfile says:

#1.5#000E0C3BEAAD00680000206400000728000414EF53711A9D#1148918037216#/System/Server#sap.com/com.saplabs.sisopt#com.sap.engine.services.rmi_p4#J2EE_ADMIN#39##sapcrm.hartung.de_CRM_5848850#Guest#56569d00ef2b11daa3de000e0c3beaad#Thread[Thread-69,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.rmi_p4#Plain###P4:Thread[Thread-69,5,SAPEngine_Application_Thread[impl:3]_Group]: P4 Call exception: Exception in execute <login>#

#1.5#000E0C3BEAAD00680000206500000728000414EF53711B39#1148918037216#/System/Server#sap.com/com.saplabs.sisopt#com.sap.engine.services.rmi_p4#J2EE_ADMIN#39##sapcrm.hartung.de_CRM_5848850#Guest#56569d00ef2b11daa3de000e0c3beaad#Thread[Thread-69,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.rmi_p4#Plain###Cannot authenticate the user.#

#1.5#000E0C3BEAAD00680000206600000728000414EF53712895#1148918037216#/System/Server#sap.com/com.saplabs.sisopt#com.sap.engine.services.jndi#J2EE_ADMIN#39##sapcrm.hartung.de_CRM_5848850#Guest#56569d00ef2b11daa3de000e0c3beaad#Thread[Thread-69,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning#1#com.sap.engine.services.jndi#Java#jndi_registry_0157#com.sap.engine.services.jndi.persistent.JNDIResourceBundle#Exception while trying to get InitialContext.

No SAP note available so far, my call is pending - any idea?

Regards,

Michael

[Former Member]

Hi Michael,

please post the dispatcher log files

Regards,

Pascal

[Former Member]

Hello,

I have the same problem (same error in the browser and in the std_server0.out).

Please let me know if someone find a solution for this problem.

I have open a sap message, too.

Kind Regards,

Mischa

[Former Member]

hey guys

i am also facing the same problem. if you guy's found the solution them please let me know also. i will be very thanful to you and rewards the points too..if your help make my problem solve.

Thanks and regards

virender

[Former Member]

Hi Thomas,

what about the dispatcher log files?

Regards,

Pascal