Common internet error while launching webdynpro application in Portal

Hi
We are facing issues with the development components of WD type deployed on a server with more than one instances.
We have build up a custom development component & deployed on the server. Created a Portal page for the deployed component & when trying to launch that page in Portal, we are facing a common internet error as  "The Page Cannot be Displayed" .
"The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
To attempt fixing network connectivity problems, click Tools, and then click "Diagnose Connection Problems..."
When trying to lauch the same page from specified instances, the applications launches successfully but fails when tried through central instance.
Has any one faced this issue earlier? Please share the experience.
Thanks,
Archana

Hi Archana
Please check that where you are delpoying application central instance or other instance.
Go to CMS >> landscape configuraiton >> see Runtime details..
Hope it helps
Regards
Arun

Similar Messages

  • Error while creating webdynpro iview after  portal upgrade to ehp1

    Hello  All
    We have upgraded  our portal from 7.0  sp  15   to  portal  7.01  sp  3    .
    After upgrade we can create  iviews using portal components  but we are not able to create  iview using Iview template
    We are getting following  error  while creating  webdynpro java  iview
    java.lang.NoSuchMethodError: com.sapportals.portal.pcd.gl.PcdSearchControls.addExplicitAttributeCheck(Lcom/sapportals/portal/pcd/gl/IPcdAttribute;)V
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getPCDCatalog(TemplatesCacheSrv.java:184)
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.refresh(TemplatesCacheSrv.java:589)
         at com.sap.newpage.pagewizardpanes.PageTemplateSelection.initTemplates(PageTemplateSelection.java:229)
         at com.sap.newpage.pagewizardpanes.PageTemplateSelection.wdDoModifyView(PageTemplateSelection.java:172)
         at com.sap.newpage.pagewizardpanes.wdp.InternalPageTemplateSelection.wdDoModifyView(InternalPageTemplateSelection.java:305)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:488)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1300)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Regards
    Rajendra

    Hello Rajendra,
    please can you tell me, if you finally get a Solution for this Problem about  iviews creation with template Error after upgrade.
    Thanks and take Care
    Gedeon

  • Error while running webdynpro application with an Interactive form

    Hi all,
    I am getting the following defect when I run a adobe interactive form (webdynpro application). Any pointers?
    Regards,
    Deepak
    500   Internal Server Error
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:464)
        ... 47 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1)
    Version null
    DOM version null
    Client Type msie7
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Oct 10 10:17:00 EDT 2007
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en_US
    Time of Failure Thu Oct 18 17:39:22 EDT 2007 (Java Time: 1192743562661)
    Web Dynpro Code Generation Infos
    local/NIBCOSecurityFormWD
    SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:06[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates (unknown)
    SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:13:54[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:11[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:42[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:35[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:23:29[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:28:49[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:21[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to  UPDATEDATAINPDF
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:418)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         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:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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)
    Caused by: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process Render Request.
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:100)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:123)
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:340)
         ... 29 more
    Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
         java.net.ConnectException: Connection refused: connect
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:408)
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.render(PDFObject.java:3948)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:148)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
         ... 32 more
    Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
         java.net.ConnectException: Connection refused: connect
         at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:85)
         at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:385)
         ... 35 more
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
         at java.net.Socket.connect(Socket.java:464)
         at java.net.Socket.connect(Socket.java:414)
         at java.net.Socket.<init>(Socket.java:310)
         at java.net.Socket.<init>(Socket.java:125)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:648)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:470)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:427)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:355)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
         at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
         ... 37 more

    Hi Deepak,
    If you have solved the issue could you kindly close the thread with the solution as this will help others as well. If not kindly update the thread with the status.

  • Error while deploying Webdynpro Application in CE 7.1.1

    Hi,
    Im developing Webdynpro DC application in CE 7.1.1. ( Composite Environment 7.1 Enhancement Pack 1)  While deploying the application im getting error saying ,
    Error: "Application error occurred during the request processing."
      Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home
    Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'demo.sap.com/firstdc' is not deployed on the server. Please check the used URL for typos.
    +     at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:364)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:566)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:504)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:169)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:230)+
    +     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)+
    +     at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)+
    +     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)+
    +     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)+
    +     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)+
    +     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)+
    +     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)+
    +     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
    +     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)+
    +     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)+
    +     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)+
    +     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)+
    +     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)+
    +     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)+
    +     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)+
    +     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)+
    +     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)+
    +     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)+
    +     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)+
    +     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)+
    +     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)+
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'demo.sap.com/firstdc' since it is not a Web Dynpro object.
    +     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:87)+
    +     at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:37)+
    +     at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:362)+
    +     ... 50 more+
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name demo.sap.com/firstdc exists.
    +     at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:264)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:85)+
    +     ... 52 more+
    Pls provide me the solution.
    thanks in advance,
    raji

    Hi Veera/Abhi
    I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
    On my NWDS PDA  Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
    2009-02-11 13:02:40 ...  (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
    Madhu--
    Please find my ans to the following points mentioned by you
    1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
    It is assigned
    2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
    Rule is activated
    3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
    Rule is activated
    4) Make sure that you have installed the following components in the following sequence in the PDA
    - Creme
    - MinDB/DB2e
    - PDA_eswt_container
    - PDA Runtime.
    Client is  installed in this sequence only. I referrred to help.sap.com while installing
    the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking  up the data. giving the above mentioned error.
    Regards
    Priya

  • Error while building Webdynpro application

    Hi all,
    I am getting error while building web dynpro application.
    Error is as :
    Error               Web Dynpro Generation: Metadata constraint of Component ExtraShifts is violated: ViewElementAggregation "//WebDynpro/View:dk.cph.sec.wd.extrashifts.application.ExtraShiftsView/RootUIElementContainer/Child:OuterGroup/Child:TuesdayGroup/Child:TuesdayTable/OutgoingAggregation:GroupedColumns", Role "Definition": A minimum of 1 object(s) is required     ExtraShifts.wdcomponent     WD_CPH_SEC_ExtraShift/src/packages/dk/cph/sec/wd/extrashifts/application     
    Please help me to resolve it.
    Thanks,
    Devender V

    Hi,
    Please have a look at this thread,
    Re: Error in CompatibilityMode
    Regards,
    Saravanan K

  • Error while Deploy Webdynpro  application

    hi experts,
    while Deploying my Webdynpro application i am getting the following error.
    Jul 25, 2007 12:05:54 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [002]Deployment aborted
    Settings
    SDM host : portal
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS1/Temp/temp33259tcs.comadmis.ear
    Deployment exception : Server portal did not accept login request as apiadmin on port 50018 - Cannot log in. There are already active sessions:
    Session id 87 / An administrator logged in via API /
    Inner exception was :
    Server portal did not accept login request as apiadmin on port 50018 - Cannot log in. There are already active sessions:
    Session id 87 / An administrator logged in via API /
    pls could anybody help me on this issues.
    vijai

    It seems that some user is already logged into the system and using the services.
    I don't how can you increase the number of session allowed in server.
    But for now. You can just check who else is using server and ask them to stop.
    You can restart the server and then try deployment. It will work then for you
    Regards,
    Ashwani Kr Sharma

  • Error while executing webdynpro application : he URL does not contain full

    Dear All,
    I had installed SAP in my system.But when I am testing webdynpro application I am getting the belwo error. Please let me knwo what setting I need to do to avoid this error.
    Error when processing your request
    What has happened?
    The URL http://hari:8000/sap/bc/webdynpro/sap/z_test_pg was not called due to an error.
    Note
    The following error text was processed in the system DEV : The URL does not contain full domain specification (hari statt hari.<domain>.<ext>).
    The error occurred on the application server HARI_DEV_00 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: CHECK of program CX_FQDN=======================CP
    Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
    Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
    Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system DEV in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server HARI_DEV_00 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server HARI_DEV_00 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 800 -u: SAPUSER -l: E -s: DEV -i: HARI_DEV_00 -w: 0 -d: 20080109 -t: 073032 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team

    Hello,
    Little extract from the SAP online help :
    In Web Dynpro ABAP it is imperative that a client browser with a fully qualified domain name (FQDN) has access to the AS-ABAP. For this reason the full URL must be assigned to a Web Dynpro ABAP application when it is called. The URL must not be shortened (for instance, no domain specification).
    More info on how you should do this can be found here :
    [Click|http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm]
    This will solve your problem.
    Success.
    Wim

  • Error while executing WebDynpro Application with Adobe interactive forms.

    I have created a webDynpro application which involves an adobe interactive form. When i deploy and run the application, i am able to deploy it on the J2EE engine on the EP server but while executing it, i get the following exception -
    <b>Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error during call to AdobeDocumentServer: Processing exception during a "UsageRights" operation. Request start time: Thu Oct 12 17:30:39 GMT+05:30 2006
        at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:486)
        at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:185)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1154)
        at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:402)
        at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
        ... 21 more</b>
    I would appreciate any help in this matter.
    Thanks...

    Hi,
    Check the note in this site...
    https://websmp204.sap-ag.de/notes
    Regards,
    <i><b>Raja Sekhar</b></i>

  • Errors while running Webdynpro applications..

    Hi,
    While running an application in WebDynpro, i encountered following errors.
    Please help me what can be the poosible way out?
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.IllegalArgumentException: -1
        at com.sap.tc.webdynpro.clientimpl.html.uielements.adaptbase.IndexedItemsIterator.advanceIndex(IndexedItemsIterator.java:104)
        at com.sap.tc.webdynpro.clientimpl.html.uielib.standard.uradapter.GridLayoutAdapter$Cells.doNext(GridLayoutAdapter.java:363)
        at com.sap.tc.webdynpro.clientimpl.html.uielements.adaptbase.IndexedItemsIterator.next(IndexedItemsIterator.java:54)
        at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:385)
        at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GridLayoutRenderer.renderGridLayoutFragment(GridLayoutRenderer.java:310)
        ... 37 more
    Thanks
    Snehal R Patil

    Hi,
    You have not described your application scenario here.
    Any way the problem at first glance seems to be at some element where you have applied GridLayout.
    Have you enetered any unacceptable values for some of the properties , there?
    Regards,
    Harisg
    (Please award points for helpful answers)

  • Error while launching Webdynpro Console

    Hello Gurus,
    I am trying to launch webdynpro console from the
    url
    http://<HOST>:50000/webdynpro/welcome/Welcome.jsp
    and its giving me error
       Internal Server Error
      SAP J2EE Engine/7.00 
      Application error occurred during request processing.
      Details:   java.lang.NullPointerException: null
    Exception id: [001A4B063BBE0066000000210000556500045A9A6DA83C10]
    can you help in diagnosig it, where can i check the logs for this and what steps can i take to correct this.
    Precise answers will be rewarded.
    -Thanks
    Sam

    Hello Koti
    I checked defaultTrace0.trc
    and found some entries related to webdynpro
    #1.5 #001A4B063BBE00130000000100004E8900045A6ABC0BD07A#1225314374759#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper#######SAPEngine_System_Thread[impl:5]_16##0#0#Error##Plain###Service webdynpro error com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to access Web Dynpro container. during shutdown.#
    #1.5 #001A4B063BBE00130000000300004E8900045A6ABC0BD7B2#1225314374761#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper.ServiceStopper.run#######SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#/System/Server#Plain###Failed to access Web Dynpro container.#
    #1.5 #001A4B063BBE00130000000400004E8900045A6ABC0BD810#1225314374761#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper.ServiceStopper.run#######SAPEngine_System_Thread[impl:5]_16##0#0#Error##Plain###com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to access Web Dynpro container.#
    #1.5 #001A4B063BBE00130000000500004E8900045A6ABC0BD869#1225314374762#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper.ServiceStopper.run#######SAPEngine_System_Thread[impl:5]_16##0#0#Error##Plain###com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to access Web Dynpro container.
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DOContainerHook.stop(DOContainerHook.java:76)
         at com.sap.engine.services.webdynpro.WebDynproFrame.stopInternal(WebDynproFrame.java:218)
         at com.sap.engine.services.webdynpro.WebDynproFrame.stop(WebDynproFrame.java:202)
         at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DOContainerHook.stop(DOContainerHook.java:73)
         ... 6 more
    any suggestion on that
    Thanks
    Sam

  • " User not authorized" error while deploying webdynpro application on WAS

    I am getting following error while deploying dyn pro application on WAS
    Error
    May 17, 2005 6:37:21 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [002]Deployment aborted
    Settings
    SDM host : DYNPRO
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/720359/LOCALS1/Temp/temp50603PVTOSAP.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/720359/LOCALS1/Temp/temp50603PVTOSAP.ear
    Aborted: development component 'PVTOSAP'/'local'/'LOKAL'/'0.2005.05.17.18.37.08':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [DYNPRO] with user name: [J2EE_ADMIN]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: User not authorized.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment exception : The deployment of at least one item aborted
    Additional Log :
    May 17, 2005 6:37:21 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
    [002]Additional log information about the deployment
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7162 - 630_SP]/>
    <!NAME[D:\usr\sap\DYN\DVEBMGS00\SDM\program\log\sdmcl20050517131312.log]/>
    <!PATTERN[sdmcl20050517131312.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    May 17, 2005 6:43:12 PM  Info: -
    Starting deployment -
    May 17, 2005 6:43:12 PM  Info: Loading selected archives...
    May 17, 2005 6:43:12 PM  Info: Loading archive 'D:\usr\sap\DYN\DVEBMGS00\SDM\program\temp\temp50603PVTOSAP.ear'
    May 17, 2005 6:43:14 PM  Info: Selected archives successfully loaded.
    May 17, 2005 6:43:14 PM  Info: Actions per selected component:
    May 17, 2005 6:43:14 PM  Info: Update: Selected development component 'PVTOSAP'/'local'/'LOKAL'/'0.2005.05.17.18.37.08' updates currently deployed development component 'PVTOSAP'/'local'/'LOKAL'/'0.2005.05.17.09.04.27'.
    May 17, 2005 6:43:15 PM  Info: Error handling strategy: OnErrorStop
    May 17, 2005 6:43:15 PM  Info: Update strategy: UpdateAllVersions
    May 17, 2005 6:43:15 PM  Info: Starting: Update: Selected development component 'PVTOSAP'/'local'/'LOKAL'/'0.2005.05.17.18.37.08' updates currently deployed development component 'PVTOSAP'/'local'/'LOKAL'/'0.2005.05.17.09.04.27'.
    May 17, 2005 6:43:15 PM  Info: SDA to be deployed: D:\usr\sap\DYN\DVEBMGS00\SDM\root\origin\local\PVtoSAP\LOKAL\0.2005.05.17.18.37.08\temp50603PVTOSAP.ear
    May 17, 2005 6:43:15 PM  Info: Software type of SDA: J2EE
    May 17, 2005 6:43:15 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 17, 2005 6:43:15 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 17, 2005 6:43:15 PM  Error: Aborted: development component 'PVTOSAP'/'local'/'LOKAL'/'0.2005.05.17.18.37.08':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [DYNPRO] with user name: [J2EE_ADMIN]
                        Check your login information.
                        Exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: User not authorized.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    May 17, 2005 6:43:17 PM  Error: -
    At least one of the Deployments failed -

    Hi Abhijeet,
    1. Execute the remoteGUI
    <<Installed drive>>:\usr\sap\J2E\JC00\SDM\program\RemoteGui.bat
    2. Click the "Connect to SDM server" (Menu "SDM GUI --> Login")
    3. Give the hostname (DYNPRO) and port (50018)
    4. Enter the password and click login.
    Check whether you are able to login or not. If you are not able to login through the RemoteGUI, then the password might be wrong. Check the password.
    Regards,
    Santhosh.C

  • Java Security Error while Launching the Application through JNLP

    Hi!,
    I have a problem in launching my Application through JNLP. It is giving the Error dialog as "Unable to lauch application" with the dialog title as "Java Security Error".
    I don't know why this problem is coming but when I have reset my profile on my system & then I tried to launch the same application & I got success.
    Can anyone suggest me what was the problem?
    Pradeep Gupta

    hi,
    usually it is the web dynpro launch system that is causing the issue, OR there is a misconfiguration in the backend like the tasks are set up with com.sap/esslea in the backend and the xml file is referencing sap.com <SWITCH>/esslea and the dynpro is showing this as not deployed.
    Regards
    Sharanya Rajagopal

  • Error while running Webdynpro Application

    Hi,
    I have configured the J2EE engine details correctly in my NWDS. Now i'm trying to run Webdynpro Applications. When I click on Run, it is asking SDM password.
    I'm entering it. Then I'm getting an error like "Deployment Aborted".
    The error details are
    Deployment exception : Server <xxx> did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server <xxx> at port 50118: <xxx>
    Please suggest me what may be the error and how to resolve it...
    Thanks in advance..
    Regards,
    Naresh

    Hi Naresh,
    Either your admin password is expired or you have changed the administrator password.
    Do the following Steps,
    Use the Config Tool to change the entry in secure storage as follows:
    1. Start the Config Tool.
    (Execute <SAPj2eeEngine_install_dir> configtoolconfigtool.bat.)
    2. Select the secure store node.
    The configuration for the secure storage in the file system appears.
    3. Select the admin/password/<SID> entry.
    4. Enter the administrator user's new password in the "Value" field and choose "Add".
    5. Choose "File" --> "Apply" to save the data.
    Note: Contrary to the message that appears, you do not need to restart the server or cluster for this change to take effect.
    6. Finally restart SDM server.Then deploy.
    SAP note <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_jas/~form/handler">701654</a>
    Regards,
    Mithu

  • Error while deploying webdynpro applications on sdm

    hi all,we are having a server with ip address 172.25.5.115.but recently due to some reasons the is is changed to 172.25.4.114.earlier with previous ip we were able to use all the services like portal SDM...SDM for deploying web dynpro applications etc..very fine....but after the change of ip address we r still able to access the portal fine but not able to deploy the  webdynpro applications.getting the error message.if some one have any ideas please help....

    The error details are as shown below:
    Apr 7, 2008 4:16:27 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [004]Deployment aborted
    Settings
    SDM host : infpw01622
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/283382/LOCALS1/Temp/temp593WD_ExcelExport_NW04s.ear
    Deployment exception : Server infpw01622 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server infpw01622 at port 50118: Connection timed out: connect
    Inner exception was :
    Server infpw01622 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server infpw01622 at port 50118: Connection timed out: connect

  • Error in launching webdynpro applications

    I am trying to run webdynpro applications but this is the error i get:
    The following error text was processed in the system PAD : Die URL enthält keine vollständige Domainangabe (tcspadev statt tcspadev.
    can anyone plz suggest the solution.

    Hi Rohit,
        Please goto transaction ST22 and check the source code extract.
    This is commom error in Web dynpro ABAP but reason could vary. Check the source code and here you get the exact line where your error has occured. If its a system code then kindly check all you types and data declaration. There could be type mismatch. Paste the ST22 dump the source code extract so that I can help you.
    Cheers,
    Darshna.

Maybe you are looking for

  • Hyperlink on Crystal Report: how to popup a window without menubar?

    Hyperlink on Crystal Report: how to popup a window without menubar? Hello Experts! I'm using VS2003 with Crystal Reports for VS2003. I need to show a popup window clicking a hyperlink text object on my crystal report. On the CrystalReportViewer I hav

  • Outlook 2011 won't work

    Since upgrading to os X my Outlook wont work, I tried to reinstall and now I get errors and cant get in at all!

  • Bex Browser

    If we want to create a new query how do we do it to Bex Browser and do we need to transport it or we make changes in the clients only? Thanks

  • Row spacing in tableLayout

    I have a <tableLayout> which has two <rowLayout>. One for data heading, and one for data. There are two much space between these two rows. I tried <spacer> between two <rowLaouts>. No luck. I need to cut the space bwtween them. But I do not want use

  • How to capture applet class ?

    When you see an HTML page containing an applet, the applet code is downloaded to your browser; is it possible to save it in a .class file ? Thank you.