cancel
Showing results for 
Search instead for 
Did you mean: 

Web Dynpro Applications Can Not Be Started... Very Urgent !!!

Amey-Mogare
Contributor
0 Kudos

Dear All,

I am not able to deploy/run any of web dynpro applications on my j2e server...

When I access it, it gives following error message:-

-


503 Service Unavailable

SAP J2EE Engine/6.40

Application cannot be started.

Details: com.sap.engine.services.deploy.container.ExceptionInfo: Clusterwide exception: Failed to prepare application ''sap.com/tcwddispwda'' for startup. Reason=

[WD container ] Error - portalapp.xml file not found ! Expected entry PORTAL-INF/portalapp.xml in .par file.

-


Please help me in resolving this issue as it has stopped all my Web Dynpro applications on the server..

regards,

Amey

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi check the Server is in up or not.Go to SAP Managemeent Console disable the J2ee Engine and then Enable it.Close the Nwds and then open it.It Will work.please rewards points if it useful

Amey-Mogare
Contributor
0 Kudos

Hi,

Server is up and running... I tried to log into Web Dynpro Console but its givin same error message on browser:-

-


503 Service Unavailable

SAP J2EE Engine/6.40

Application cannot be started.

Details: com.sap.engine.services.deploy.container.ExceptionInfo: Clusterwide exception: Failed to prepare application ''sap.com/tcwddispwda'' for startup. Reason=

[WD container ] Error - portalapp.xml file not found ! Expected entry PORTAL-INF/portalapp.xml in .par file.

-


regards,

Amey

Former Member
0 Kudos

Hi amey,

Check your configuration settings

1. Start the Visual Administrator and select the node Server <x> / Services / Web Services Security from the Cluster tab.

2. Within the tab Web Services in the right frame select Security Configuration / Web Service Clients / sap.com / tcwdpdfobject / com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.

The following attributes should have been set accordingly if no SLD is used (tab Transport Security):

i) Destination

ii) URL: Default or Custom, http://[host]:[port]/AdobeDocumentServices/Config?style=document (e.g. http://localhost:50000/...) or .. https://[host]:[port]/AdobeDocumentServicesSec/Config?style=document if the connecttion uses SSL.

iii) Authentication: select BASIC or X.509 Client Certificate

If BASIC is selected, Basic Authentication / Username and Basic Authentication / Password must refer to the user that has been assigned to the security role ADSCaller within the Web AS Java that hosts the document services.

If X.509 Client Certificate is marked, the fields Client Certificate Authentication / Keystore view and Client Certificate Authentication / Certificate have to be filled in with the appropriate values).

If the connection to the document services uses the SLD, the attributes should be set as follows:

i) Destination / URL: SLD

ii) Synchronize with System Landscape

iii) System Name: [SID].SystemHome.[host]

iv) WS Name: {com.adobe/AdobeDocumentServices}{AdobeDocumentServicesAssembly.jar}

v) WS Port: {com.adobe/AdobeDocumentServices}{AdobeDocumentServicesAssembly.jar}{Adobe

DocumentServices}ConfigPort_Document

The PDF Object has to be restarted if any changes have been applied to the web service proxy. Select the node Server <x> / Services / Deploy from the Cluster tab within the Visual Administrator and choose the Application option within the right frame. Mark sap.com/tcwdpdfobject and then stop and start this application using the appropriate buttons

Regards,

P.Manivannan.

Answers (2)

Answers (2)

venkatakalyan_karanam
Active Contributor
0 Kudos

Hi

The application may be not deployed properly.Restart SDM once again and try to deploy your application.If the project build is successful.

Also try to close NWDS once and start then deploy

Regards

Kalyan

Amey-Mogare
Contributor
0 Kudos

I did that and tried to deploy but ..>

Applications are giving following exceptions while deployment..

So not able to deploy successfully !!!!

-


Caught exception during application startup from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Error occurred while starting application asianpaints.com/fsitewd and wait.

Reason: Clusterwide exception: server ID 8216350:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''asianpaints.com/fsitewd'' for startup. Reason=

Clusterwide exception: Failed to start application ''asianpaints.com/fsitewd'': The referenced application ''sap.com/tcwddispwda'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?

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

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

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:187)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:327)

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:230)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4700)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4578)

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)

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(Native Method)

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

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

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

-


regards,

Amey.

Former Member
0 Kudos

Hi,

Check if the server on which you are trying to run your application is up and in running mode.

Hope it helps.

thanks & regards,

Manoj

Amey-Mogare
Contributor
0 Kudos

Yes Manoj, server is up and running and SDM and dispatcher are running too.

regards,

Amey