The Web Dynpro application was called up with the wrong URL parameters

Hi all,
I am using the systems below:
ERP STACK :16
EHP : 4
EHP SP Stack :4
EA-HR * : 604(SP12)
SAP-HR * :604(SP12)
XSS JAVA components : SAP ESS 603 SP05
SAP MSS 600 SP16
PCUI_GP 603 SP05
Business Package : BP ERP05 ESS 1.41 SP04
BP ERP05 MSS 1.41 SP04
BP ERP05 COMMON PARTS 1.41 SP04
I am getting below error after clicking on the appraisal document:
App. Called Up Incorrectly
The Web Dynpro application was called up with the wrong URL parameters.
Note
Enter the URL parameters and their use.
You can find more information on the functions that you can perform in the catalog for appraisal templates in the Implementation Guide (IMG) for Objective Setting and Appraisals under Edit Forms.
I already applied the below notes also:
1468466 Performance Management Launchpad Configuration
1463821 Performance Management Portal Configuration
1416756 OBN Configuration in Performance Management
1408243 Configuration for object-based navigation
Plz advise me??
Thanks,
Anumit

can you paste the exact error. also you can take a HTTP trace and see which resourse or UWL is being launched!

Similar Messages

The Web Dynpro application 'UWL' has expired

Hi ALL,
We are using Enterprise portal 7.0. and backend SRM server
When the user login into portal it will take him to the UWL page
in that the user click for any "Approve shopping cart" the error message showing
" The web dynpro application *'UWL' has expired. restart the application. choose 'refresh' in the iview tray or use the*
*browser 'refresh' button to restart the iview"*
user not getting the error message every time. error coming occasionally
we suggest the user to clear the cookies and restart the browser and relogin.
but some times it works some times not
Can any one know the exact problem (any parameters has to be change or any other solution)?
Regards,
Abdul Razzaq
SAP NW.BASIS Consultant

Dear Abdul ,
Hope you are doing good.
We have seen similar cases of WD Session Expired error message when the jsessionid cookie issued by the server with the initial requests was not returned from the client with subsequent requets to the server. The only way to ascertain whether this is the case in your system will be by checking the HTTP watch trace (note 1558903 - How To Trace a Portal Scenario Using HttpWatch).
As the jsessionid cookie is used for session management, when it is missing from the request headers the correct session could not be retrieved and as result new session will be created for that user. Set the parameter JSESSIONID.CookieDomain to "NONE" as mentioned in the sap note: 791765 and see if the issue persists. This configuration should be accessible in
Config Tool -> expand the tree "cluster-data" -> "Global Server Configuration" -> "services" -> "servlet_jsp" -> Go to "Global
Properties". Do make the changes, save the customization and then restart the complete SAP server (not just the JAVA server nodes).
Kindly go through the note completely.
Also make sure that the SystemCookiesDataProtection and SystemCookieHTTPProtection is set in the HTTP Provider Service on
the server nodes.
Do make the changes,save the customization and then restart the complete SAP server.
Thank you and have a nice day :).
Kind Regards,
Hemanth
SAP AGS

How to make use of Portal service in the web dynpro application

hi
I have some portal service and how to use that in the web dynpro application.
and also what is the main diff between Portal Component and web dynpro application.
do we required portal to run web dynpro application.
thanks
mmukesh

Hi,
>> I have some portal service and how to use that in the web dynpro application.
Yes. U can use Portal service in webdynpro. Check the link given by subathra.
>> and also what is the main diff between Portal Component and web dynpro application
Portal Components are components designed to run in portal server while webdynpro application can run in J2EE WebAS.
>> do we required portal to run web dynpro application.
No for general cases. Just WebAS is sufficient to run webdynpro appl. But if u use portal service in ur webdynpro appl, then make sure both (portal service and webdynpro appl) run on same J2EE engine. That is mandatory.
Regards,
Vijai

The Web Dynpro Application 'XssMenu' has expired

Hi,
we implement an ESS Scenario, with One Enterprise Portal 6.0 SP17, a mySAP ECC 5.0 System with ERP2004 and a seperate server with a java stack, because our customer don´t want to install and use a java stack on their HR/ERP systems. They want to minimize the performance.
After some configurations, we get the startpage for ESS. If I click on a service like travel management it has no effect. If I click the second time, I got an error "500 Internal Server Error" with the message
The Web Dynpro Application 'XssMenu' has expired. Please restart the application either with the refresh button or click the following link XssMenu.
Same error comes, if I choose travel management in the second navigation level and click the service. And same message on every service.
Now I tried anotehr way. I call the ess startpage directly on the external java stack. And here´s no problem. All WebDynpro-Services works fine.
Can anyone help me, why the WebDynpro Service doesn´t work in the Portal?
Best regards
Christian

We had exactly the same problem. We had multiple java servers and our switch was not retaining stickiness. So it would send the user to a different java server which hadn't got any session data for that user.
If this could be it, get something like httplook to do a trace of what is happening. We saw it switching java servers.
If you do not have multiple servers it could be switches chopping out cookies, causing the same issue.
Paul

The Web Dynpro application 'PageBuilder' has expired

Hi Alll,
We are implementing ESS/MSS and the Portal was working fine.
We set it up for SSL/https and it was working just fine. However when we call it from reverse proxy server the web dynro applications through the following error:
The Web Dynpro application 'PageBuilder' has expired. Restart the application. Choose 'Refresh' in the iView tray or use the browser 'Refresh' button to restart the iView
Details: No details available
When I tested this with a transaction iview they work just. Also when tested directly from Portal they work fine.
Can anyone assist on this please?
Thanks,
Mike

Hello Mike,
After a user is logged in and requested an ESS/MSS application. The pagebuilder service is requested to built the page.
When the user is still logged in but is not working with this application the pagebuilder receives a timeout after a while and the session is expired. The pagebuilder has sometimes the status stopped, you can see this in the Netweaver Administrator. (Search for the pb in the application area)
If an other user is requesting an application the pb service is started again and the page built again.
If you want to get rid of the warning you could set the "timeout" parameter to a higher value in the configtool.
Kind regards,
Marcel

500Internal Server Error The Web Dynpro application PageBuilder has expired

hi all ,
i am using public url domain to access my portal through internet . i have done a reverse proxy using apache . from my server url i am able to get every page . from public url i am not able to view my webdynpro applications . its showing the following error
500 Internal Server Error
SAP J2EE Engine/7.01
The Web Dynpro application 'PageBuilder' has expired. Restart the application. Choose 'Refresh' in the iView tray or use the browser 'Refresh' button to restart the iView
Details: No details available
i got this log file in the portal
Full Message Text
Session unknown: Request with URI=/webdynpro/dispatcher/sap.com/pb/PageBuilder was sent to unknown session. Either request with wrong session parameters was sent, or session has expired before Wed Oct 20 21:47:46 IST 2010. Current request parameters={sap-ext-sid=DL7cHVE6DiKdbE9gwYkSdg5A6q8C_OKOzgxi0HoLa2iw, sap-wd-cltwndid=WID1287644121668, sap-wd-norefresh=X, sap-ep-version=7.0104.20090422102234.0000}. Is termination request=false. Request was sent from host with IP=172.31.11.95/name=172.31.11.95. Hint: see SAP note 842635 for more details on session expiration. RID=a16ac995dcdf11dfb3e70021281821ee
[EXCEPTION]
com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Session has expired (current request: follow-up request). Please restart the application. Hint: HttpSession seems to be expired due to user inactivity or application is called with wrong URL parameter (sap-wd-norefresh=X).
at com.sap.tc.webdynpro.clientserver.session.RequestManager.findClientSession(RequestManager.java:258)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:146)
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)
can anybody helpme in this issue

Hello,
Please see this post:
The Web Dynpro application 'PageBuilder' has expired
I think the problem is solved in this post.
Regards.

How to display the error message during the web dynpro application runtime

hi,
    I'm a java developer,During i 'deploy and run ' a web dynpro application on server-1,if the application have some runtime errors. there are displayed many infomation about the runtime error,such as exception track,etc.
    But when i do the same on server-2,there just show something like:
            500   Internal Server Error
                                SAP NetWeaver Application Server 7.00/Java AS 7.00
            Failed to process request. Please contact your system administrator.
but the server-1 will stop the j2ee engine.
how can do i make server-2 show detail error message as server-1. when i debug web dynpro application need these infomation.
Appreciate your inputs...
(Note:server-1 and server-2 have same software version)
Edited by: BingLin Zhong on Feb 18, 2008 2:13 AM

The Sap-Notes 962319:
1. Check in the Visual Administrator, "Licensing Adapter" -> "General" -> "SystemType" !
If it is set to "DEVELOPMENT_MODE", verbose error messages are shown.
If it is undefined, proceed with the next step.
If it is set to something else, only exception IDs are shown. In this case the only chance is to search for this exception ID in the default traces.
2. If the system type is undefined, then in the Config Tool "Configurations" -> "webdynpro" -> "sap.com" -> "tcwddispwda" -> "Propertysheet default" -> "DevelopmentMode" is evaluated. If it is "true", verbose error messages are shown.
3. If verbose error messages are required but still the short version is shown, you probably face an error message that is not raised by Web Dynpro but by other components of the NetWeaver. In the Visual Administrator set "Properties" -> "HTTP Provider" -> "DetailedErrorResponse" to "true".
4. In addition to the error page shown in the browser or client, important messages - including error messages and stack traces - are written to the log and trace files, e.g. to the default traces usr\sap\<SID>\<instance>\j2ee\cluster\server<number>\log\defaulttrace.trc.<number>.
a) In some cases, when an exception ID is included in the error message, the detailed error message can easily be retrieved in the log file.
b) When no exception ID is given, you have to search for the detailed error message in the log specifying time stamp and/or user ID.
Always consider restarting the system after making changes on the settings.
It is not recommended to switch the "SystemType" to an inappropriate value just for viewing verbose error messages. The system type potentially affects framework, applications and licensing in an perhaps unintended way.
In the past there was no distinction between different system types regarding error messages. For security reasons this distiction has been introduced. It is not intended to show stack traces in non-development systems in the future. SAP does not provide workarounds or patches to enable such a behaviour again.

The Web Dynpro Application for LeaveRequest has expired

My problem with the portals is that when users apply for leave they get the message. The Web Dynpro Application for LeaveRequest has expired. On another machine the user is working fine. But sometimes users get that message. I ve been in contact with oss calls but these guys are not helping. Even checking salary statement give the same problem. So has anybody experienced this problem that can help me or even can give advise please help
Naziem Mahomed

hi
just go through the follwing link
http://help.sap.com/erp2005_ehp_04/helpdata/DE/2d/292391fa6745488f3e0e0d4b03c64e/frameset.htm
may be it will help u.
Thanks
Bharathi.ch

The Web Dynpro Application 'PcrApplication' has expired.

Hi,
I am getting below error:-
500 Internal Server Error:
The Web Dynpro Application 'PcrApplication' has expired. Please restart the application either with the refresh button or click the following link PcrApplication.
Can anyone help me on this.
Best regards
Ali

Hi Rali,
I think you have not been using this application from long time. So the Portal session time must have expired. Well, Let us know if the problem persist even after RESTART of the browser.
Regards
<i><b>Raja Sekhar</b></i>

The Web Dynpro Application 'Appl' has expired.

Hallo altogether,
i am a newbie in this area.
I maked a simple Web Dynpro with two views,
only for navigation test
and without data transport.
Everybody view consist of two elements:
one TXV_Field and one BTN_Element.
V_ONE:
TXV_ONE with a text "View one",
BTN_GO + action GO,
OP_TO_TWO,
IP_FROM_TWO
V_TWO:
TXV_TWO with a text "View two",
BTN_BACK + action BACK,
OP_TO_ONE
IP_FROM_ONE.
There are two links between views builds.
I cann my application APPL deploy without problem and without error messages.
I see my V_ONE im browser.
If i click the button BTN_GO ==>
The Web Dynpro Application 'Appl' has expired.
I controlled the file default.properties
the timeout = 3600.
what cann i do????
Thank,
vmath.

1. check ur server configuration windw> preference->j2ee-engine.
I have DeveloperStudio local on my PC.
There are following settings for j2ee-engine:
SAP J2EE-engine is installed on local host
System name: J2E
J2EE Instance: 0
SCS Instance: 1
BEN_1\sapmnt\J2E\SYS\profile\J2E_JC00_ben_1
BEN_1\sapmnt\J2E\SYS\profile\J2E_SCS01_ben_1
vmath

The Web Dynpro Application 'WebAdminApp' has expired.

Hello all,
I am getting this error when I click on anything from /nwa.
The Web Dynpro Application 'WebAdminApp' has expired. Restart the application using the Refresh button or via the following link WebAdminApp.
I have to configure LogOn Group for the WebDispatcher ( to be able to see the logon group from the java system) and from this link:
Logon Group Configuration - System Landscape Administration with SAP NetWeaver Administrator - SAP Library
I got the solution:
Activities
You can display the overview page of the existing logon groups if you choose System Management → Configuration → Logon Groups. The Logon Groups frame on the right contains a table that lists all logon groups on all registered systems.
So, I started /nwa and when I click on Configuration, I am getting:
The Web Dynpro Application 'WebAdminApp' has expired. Restart the application using the Refresh button or via the following link WebAdminApp.
Can you suggest me a solution?
thx
Chris

Solution:
1907152 - Web Dynpro Application 'WebAdminApp' has expired when access NWA

The Web Dynpro application XssMenuArea is expired

Some of our clients when click tab "Employee Self Service" the
information menu wonu2019t be displayed and the screen has the following
error message: the Web Dynpro application "XssMenuArea" is expired,
please use the refresh button or restart the application.
When manually click the "restart" hyper-link, the screen leaves
blank. But the above phenomenon differs from clients. The Same account
in one PC is OK but in another has the error. We donu2019t know the Client PC
should install what kind of software or plug-in to run the "ESS"
application.

Please check the following posts.
Regarding Error : Web Dynpro Application 'XssMenu' has expired.
The Web Dynpro Application 'XssMenu' has expired
'XssMenu' appication expiration
ESS XSSMenu Error

The Web Dynpro Application 'Explorer' has expired

hi,
when I am trying to open the deployed content in the
Content Administrator in the sap portal I am getting the following error
"500   Internal Server Error The Web Dynpro Application 'Explorer' has expired. Restart the application using the Refresh button or via the following link Explorer.
Details:
No details available"
what can I do?
I have read here at sdn that I should increase the expiration time but where can I do this?

Hi Thorsten,
Close your explorer, open a new explorer and run the application from the new browser.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b52de690-0201-0010-c5a6-b4bde0a12e44
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_ep_sys/~form/handler">SAP Note Number: 519191</a>
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_fes/~form/handler">SAP Note Number: 856741</a>
Regards,
Mithu

The Web Dynpro Application 'WebUI' has expired,

Hi experts,
We are using Netweaver 7.01 portal , I have done some change to the portal for configuring idle timeout .
Now currently we are not using that in portal ,so i removed all the configurations
When i am using the all the other portal applications it is working fine, but when i am using webdynpro java applications it is giving the following error in a couple of mins (less then 5 mins)
The Web Dynpro Application 'WebUI' has expired. Restart the application using the Refresh button or via the following link WebUI.
Please let me know how to resolve this is issue .
Thanks & Regards,
Pavan Marla

Hi,
Check this link and below settings
DefaultExpirationTime
=================
http://help.sap.com/saphelp_nw04s/helpdata/en/43/8a1a8ece230c8ce10000000a11466f/content.htm
Check the time for session timeout by the following steps:
1. Open the visual admin tool.
2. Navigate to Server -> Services -> Web Container -> Properties.
3. Check the value of the property 'SessionTimeout'.
Regards,
Nivas209
Edited by: Nivas209 on Feb 8, 2012 12:50 PM
Edited by: Nivas209 on Feb 8, 2012 12:51 PM
Edited by: Nivas209 on Feb 8, 2012 1:03 PM
Edited by: Nivas209 on Feb 8, 2012 1:06 PM

The Web Dynpro Application 'UmeAdminApp' has expired

hi,
if i login to portal to any application i am getting session out for each second.
500   Internal Server Error
          SAP J2EE Engine/7.00
The Web Dynpro Application 'UmeAdminApp' has expired. Restart the application using the Refresh button or via the following link UmeAdminApp.
Details:
No details available
plz help to solve this.
thanks,
Harish

HI ,
Set the application time out property to a value as per requirement.
Please follow below links for more details it may be help ful.
webdynpro application has expired
http://help.sap.com/saphelp_nw04s/helpdata/en/2a/7a754297fdd142e10000000a1550b0/content.htm
If application time out is set correctly check for the disk space available in server or log file space (basis person will do this).
Please check SDN , there are many posts available on this.
Regards
Deepak

The Web Dynpro application was called up with the wrong URL parameters

Similar Messages

Maybe you are looking for