Java iView Runtime Error in BEx Designer

[Former Member]

Hi,

Through analyzer, Query is working absolutely fine

When trying to run a query via the query designer I get the two messages :

1.In development

Java iView Runtime

copyright 2002 SAP AG.All rights reserved.

An exception occured while processing your request.

If this situation persists,please contact your system administrator

2.and in Quality

503 Service Unavailable

Application Stopped

Thanking you,

Tarun Brijwani.

[Former Member · Accepted solution]

Hi Tarun,

Please, check note 654982 whether it could be useful for you.

654982 : URL requirements due to Internet standards

It seems that the Java is not working at all.

I did a quickly search and I found some notes that may be useful for you.

1205897 Error: "HTTP 503 Service Unavailable" when trying to log on

1185855 Error: "503 Service Unavailable" when you try to log into

1183486 Error: "503. Service Unavailable" when you try to log into

1189848 Error: "503 Service Unavailable" trying to logon to Infoview

I'm not familiar with the command 'jcmon', but I know that you can verify which services are UP and running, check if the command have a help option and take a look.

Hope it helps.

Regards,

Daniel

[Former Member]

solved

[Former Member]

Hi BT..

Can i know how did you solve this problem?

As we are facing the same issue

advance thank you.

[Former Member]

Hi Tarun,

Can you tell us how did you solve this issue?

We have the same error on our development portal.

Java iView Runtime

Copyright 2002 SAP AG. All rights reserved.

An exception occured while processing your request.

If this situation persists, please contact your system administrator.

Thanks very much.

[Former Member]

Hi,

The problem is reoccuring again and again even if it gets solved temporarily after restarting the java instance.

We are again getting the following on the web error after executing the query in BEx designer:

Java iView Runtime

Copyright 2002 SAP AG. All rights reserved.

An exception occured while processing your request.

If this situation persists, please contact your system administrator.

Somebody suggest the solution please.

Thanking You,

Tarun Brijwani.

Edited by: Tarun Brijwani on Feb 5, 2009 2:52 PM

[Former Member]

Hi Tarun,

We saw that message for the first time today using the Query Designer (SPS 17). The message disappeared when we removed many of the infoobjects in the rows (there were 15) and restricted the number or rows of data returned.

Dave

[Former Member]

Hi,

Thank you very much for your reply.

From your reply, I have some doubts.

You mentioned that you reduced the no of info objects in the rows in query definition and the problem got solved.

1.Did you check that for the some queries which were already containing less no.of rows, it did not show this error.

2.And you were getting this this error only in the those particular queries which were containing more no.of rows?

3.Have you again tried by placing more no.of info objects in rows after you solved the error?

Please reply even if you didn't try all these things coz it will be very helpfull for us in further investigation.

Thanking You,

Tarun Brijwani.

Edited by: Tarun Brijwani on Feb 6, 2009 12:02 PM

[Former Member]

Hi Taurn,

To answer your questions:

1. I have run other queries but did not experience the Java iView Runtime error again. We did not see the 503 error you mention in your quality system. The large number of infoobjects selected in the rows was an effort to track down a data error. Most queries do not retrieve so many fields at one time.

2. I only saw the Java iView Runtime error for the one query and that was the first time. When I saw your post, I passed on a quick solution that worked for us. Errors are pretty frequent with the java based tools, but I have only experienced this error once.

3. I have not tried to run the query again with all the rows selected to see if the error comes up. I am not at my desk today, but may try that when I return. I can post a followup.

Hope this helps you.

Dave

[Former Member]

Hi,

We raised a message to SAP and they suggested to fpllow the steps mentioned in note: 937697

We ran the support desk tool as specified in the above note and found some configuration errors which we corrected and thereafter, the configuration was made ok.

After that, everything went ok and we did not get the same error message but after many days were passed, again the same error reappeared and from the basis team found that user SAPJSF was getting locked due to incorrect logons.

We unlocked the user and again the error disappeared.

But we are wondering that why everytime this user is getting locked.Please provide suggestions.

Thanking You,

Tarun Brijwani.

[Former Member]

We restarted the java instance and it solved the problem

Edited by: Tarun Brijwani on Jan 22, 2009 1:25 PM

[Former Member]

Dear Tarun,

Looks like the Bex Web is not set up for your BW system.

Here a Portal on a Java stack is required for you to be able to execute the query in Web.

You may please refer below note for further details:

Note 917950 - SAP NetWeaver 2004s: Setting Up BEx Web

Further ,below Note may help you in resolving the issues in Web:

Note 888687 - BEx Web Java: Analysis of communication/logon problems

Hope this helps!

Kind Regards,

Robin