sld started giving error after installation of add...

former_member360410 · ‎08-02-2009

Hi Experts,

I had a BW server with dual stack (AS ABAP + AS Java only base u2013 No BI u2013 Java server). Everything was running fine and I have checked that http://server:port/nwa, http://server:port/useradmin and http://server:port/sld was browsable although I didn't configured SLD.

My BW developer team wanted to use BEX web reports and for the same I have installed following add on usage type as per note 883948 as I had only upto SPS9 as a default installation.

u201C

Components of EPC (UT_NAME = EPC) SAP NetWeaver 7.0 (2004s) >= SPS09 < SPS11:

|FILE NAME |DESCRIPTION

|EPBC*_.SCA |PORTAL CORE SERVICES 7.00

|EPBC2*_.SCA |PORTAL FRAMEWORK 7.00

|EPPSERV*_.SCA |PORTAL 7.00

|EPWDC*_.SCA |PORTAL WEB DYNPRO 7.00u201D

And

UTs of SAP NetWeaver 7.00 (2004s):

Components of BI (UT_NAME = BI):

|FILE NAME |DESCRIPTION

|BIIBC*_.SCA |BI INFORM. BROADCASTING 7.00

|BIWEBAPP*_.SCA |BI WEB APPLICATIONS 7.00 (SP <current

version>)

|BIBASES*_.SCA |BI BASE SERVICES 7.00 (SP <current version>)

|BIREPPLAN*_.SCA |BI REPORTING AND PLANNING 7.00

|BIWDALV*_.SCA |BI WEBDYNPRO ALV 7.00

|VCKITBI*_.SCA |VCKITBI

But after this I checked and found that browsing SLD (http://server:port/sld ) started giving erroru2026. The error says something like belowu2026.

The initial exception that caused the request to fail, was:

com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/tc_sldwd~main'' for

startup. Reason= Clusterwide exception: Failed to start application ''sap.com/tc_sldwd~main'': The referenced application ''sap.

com/tc_sldwd~businesssystem'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?

at at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)

at at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)

at at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)

at at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)

at at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)

... 8 more

See full exception chain for details.

The Full exception chain is like belowu2026.

System Environment

Client

Web Dynpro Client Type HTML Client

Server

Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:39:25[UTC], changelist=413534,

host=pwdfm101), build date: Tue Dec 23 13:37:24 IST 2008

J2EE Engine No information available

Java VM IBM J9SE VM, version:2.2, vendor: IBM Corporation

Operating system Linux, version: 2.6.16.60-0.39.3-smp, architecture: amd64

Session & Other

Session Locale en_US

Time of Failure Wed Jul 29 08:53:29 IST 2009 (Java Time: 1248837809764)

Web Dynpro Code Generation Infos

Detailed Error Information

Detailed Exception Chain

com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object sap.com/tc_sldwd~main.

at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.

java:404)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:317)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:143)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process

(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:207)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.StartStopException: Failed to start the deployable object

'sap.com/tc_sldwd~main'.

at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:184)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.

java:399)