u2018The current request has returned corrupted data.' (ERR WIJ 20005).

[Former Member]

Hi All,

We get the following error message:

u2018The current request has returned corrupted data. Please contact your administrator (ERR WIJ 20005).u2019

Environment:

- Windows Server 2003

- BOE XI 3.1

- MYSQL default repo installtion

- TomCat default installtion

- Reporting off Oracle 9i Database.

Setps completed to get the error message:

u2022 Create a WEBI report with prompts defined on the query panel (e.g. start and end dates for a date range)

u2022 Refresh the report so that data is available

u2022 Save the report and log out

u2022 Log back in and modify the report

o Remove the query prompts and replace them with different prompts (e.g. a range of products)

u2022 Refresh and save the report

u2022 Click the u2018Edit Queryu2019 button

u2022 You should get the error message u2018The current request has returned corrupted data. Please contact your administrator (ERR WIJ 20005).u2019

Is there a fix for this issue or a workaround for this issue.

Cheers

Hai

Edited by: Hai Cao on Oct 31, 2008 12:44 AM

[Former Member · Accepted solution]

Hai,

Setps completed to get the error message:
1 ) u2022 Create a WEBI report with prompts defined on the query panel (e.g. start and end dates for a date range)
2 ) u2022 Refresh the report so that data is available
3 ) u2022 Save the report and log out
4 ) u2022 Log back in and modify the report
4a ) o Remove the query prompts and replace them with different prompts (e.g. a range of products)
5 ) u2022 Refresh and save the report
6 ) u2022 Click the u2018Edit Queryu2019 button
7 ) u2022 You should get the error message 

It seems that possibly the step in 4a has bad objects? What happens if after step 7 you go back to step 3 and in step 4a replace the objects with the work done in step 1 (e.g. start and end dates for a range) and then Execute Query. If the query now works back in its step 1 configuration, and it doesn't work in step 4a configuration (e.g. a range of products), then I would say you've got some object(s) not built properly and will have to investigate via Designer on the universe in question. Please let us know how you are able to proceed on this matter.

Thanks,

John

[Former Member · Accepted solution]

Hi John, thanks for the response.

We have replicated the error workflow on several different universes (including eFashion!) so we don't think that bad objects are the issue.

We've also tried using different query panels. On the interactive panel, you get a different error - WIH 444444.

[Former Member · Accepted solution]

Hi Cao,

Can you please tell me exact version of BOE 3.1 you are using from control panel-> add/remove programs.

Because I have replicated the workflow and found that reports are working absolutely fine with Java report panel and Interactive panel as well.

I am using BOE 3.1 version 12.0.0.800.

Regards,

Snehal

[Former Member · Accepted solution]

Hi Snehal,

My BOE XI 3.1 build version is 12.1.0.882.

The reason for this is that I have CR 2008PS0 and installed SP1.

The above will give you my build.

Cheers

Hai.

[Former Member · Accepted solution]

Hi,

I too have the exact same issue, however I would like to point out a few things:

1) The issue is not faced until we export the report to CMS.

2) The issue is faced only after the report is exported to CMS.

3) Issue does not occur with efashion database/universe.

4) Re-exporting universe/webi report does not help.

I think the problem is with SQL queries used with the universe objects as some how the java panel is not able to communicate to the webi report server.

Regards,

Ankur Potdar.

[Former Member · Accepted solution]

Hi ,

Can anybody help me recreate prompts?

will this be a probable solution to the issue?

Regards,

Ankur Potdar.

[Former Member · Accepted solution]

Hi Hai,

Did you get any solution or workaround for the below error message for Webi reports?

"We've also tried using different query panels. On the interactive panel, you get a different error - WIH 444444"

Your response would be really valuable....

regards,

Arun