Error while opening webi report

[former_member196240]

Hi Experts,

I have a webi report built on top of the bex query it was working fine until yesterday. But now when i attempt to open the report i get 2 set of errors in the event of opening the report.

1.Error when trying to refresh the current report - if i select the option close then i get the following error

2.An internal error occured while calling 'processDPCommandsEx' API. (Error: ERR_WIS_30270) (WIS 30270)

Executed RSRT the query just works fine, not sure what is wrong with the webi.

Note - I'm on BO 4.0 SP06 with patch 1.

Appreciate any thoughts/comments.

Thanks,

Vinay

[Former Member · Accepted solution]

Hi Vinay,

Please answer below questions and refer to below notes to see if your issue matches with any of the below.RSRT would run fine since changes in Bex would not affect Bex output with errors, but may affect webi report. Try creating a new simple webi report on the same OLAP connection and test if its working without any errors.

Were there any changes to the Bex query in last few days?

Was there any patch or service pack upgrade performed on your BO environment recently?

Check if there are two key figures in the Bex query with the same name

1610314 - An internal error occured while calling 'processDPCommandsEx' API. (Error: ERR_WIS_30720) in Web Intelligence report based on Bex query which has two key figures with the same name

1619405 - ProcessDP CommandsEx (WIS 30270) Error when run a report based on Bex querybased on Bex query which has two key figures

with the same name

1604990 - BI 4.0: Changing BEx query that's in use in Web Intelligence report causes "An internal error occured while calling 'processDPCommandsEx' API. (Error: ERR_WIS_30720) (WIS_30720)\

Thanks

Mallik

[former_member196240 · Accepted solution]

Hi Mallik,

I tried creating the report using OLAP connection without any errors, there was no change with the bex query in the last few days. And very recently we have upgraded our  D,Q, and P  systems with SP06.

Yes there are two key figures with same tech_name, one with USD conversion the other without any conversion(LC).

As i have mentioned, query has two hierarchy variables. If i remove them from the bex query the webi report runs with no issues/errors. If i add it back then there is an error, i'm just thinking same key figure  tech_name may not have an issue atleast in my report.

Let me know your view on this?

Thanks

Vinay

[Former Member · Accepted solution]

Agree Vinay,  seems like your issue is with hierarchy objects, refer to below note that has the issue with hierarchy objects addressed and check if this is your case.

1622057 - Error: "An internal error occured while calling 'processDPCommandsEx' API. (Error: ERR_WIS_30270) (WIS 30270)" when refreshing WEBI report with a hierarchy object.

"An internal error occured while calling 'processDPCommandsEx' API. (Error: ERR_WIS_30270) (WIS 30270)" when refreshing WEBI report that includes a hierarchy object in the query panel.

Reproducing the Issue

Create a simple WebIntelligence report using BICS connection.

Drag a hierarchy object and a key figure to the query panel and run the report.  The processDPCommand error is displayed.

Note: This issue is only reproducible with hierarchies that have leaves without a parent.

Cause

This problem is caused by a program error on the BW system.

Resolution

Apply the following SAP note to your BW system:

Note 1357433 - Child-parent relationships in hierarchy are read incorrectly

Thanks

Mallik

[former_member196240 · Accepted solution]

Hi Mallik,

The note does not apply to us as we are on  BI 7.3 the above note deals with the version up to BI 7.1

Let me know any other possible workarounds.

Thanks,

Vinay

[Former Member · Accepted solution]

Hi Vinay,

We have upgrade to SP6 on Q and we did not have any such issues with webi reports with BICS connections and moreover from what you say new webi report creation on OLAP connection is fine, which means there is no issue from OLAP Connection side.

Is the error with this existing report consistent across all webi reports with BICS connectivity, for different user ID's and all upgraded environments (D,Q,P)?? If answer is yes, Then something went wrong with your recent upgrade, need to contact your basis to check on if they missed anything.

If its a specific case with one off report, then it could be corruption post upgrade, try and promote a copy of this report from your server backups before upgrade to a different folder  and see if that copy works.

Thanks

Mallik

[former_member196240 · Accepted solution]

Hi Mallik,

Before i answer your above questions, you might be more interesting to know the following behavior:

In my further testing i have found, the webi report is working fine with the optional hierarchy variables but not with mandatory one's. I don't see any difference among them except the optional/mandatory.

I'm curious to know your view on this?

Thanks,

Vinay

[Former Member · Accepted solution]

Hi Vinay,

Please check the below wiki page and see if the any of the ADAPT's of known issues or KBA's is matching with your case, if so then verify if its in under fixed issue of SP6 patch 1 in Release notes.

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=334169942&bc=true

To me, It seems like more of an environment bug as there were good number of them reported on SP5 and that too on hierarchy variables, so suggest you to raise this with SAP.

One last check, if you want to do try and change the hierarchy node variable as optional(so that report doesn't throw errors) and then try to create a mandatory prompt at webi query panel level on the same hierarchy object to see if that works. you can use it as alternate if this works fine.

Thanks

Mallik

[Former Member]

Hi,

Did you already try changing the data source of the Webi report to point to the very same BEx query?

Best regards,

Victor

[former_member196240]

Hi Victor,

I did try changing the data source to point to the same BEx query but no luck.

Thanks,

Vinay

[former_member188911]

Hi Vinay,

I see you are using an OLAP unv that points to BW right?

If this is correct, when you upgrade to a higher SP level you need to refresh the universe structure, otherwise code changes affecting the calculation engine and/or semantic layer may result in errors or incorrect data

If you do still experience the errors after refreshing structure and re-publishing the universe, you should consider involving support if you can

Thanks

Simone

[former_member196240]

Hi Simone,

For this report the data source is BEx query using the BICS connection, i guess we don't have to refresh or publish anything here?

The support message has been created, currently SAP is looking in to it.

Thanks,

Vinay

[Former Member]

Hi Vinay,

Do you have a solution from SAP for this issue?

I am facing the same issue (SP5 Patch 13) while using 'Mandatory' Hierarchy Node Variables in the query and consuming it through BICS connection in my webi report.

Error:

1.Error when trying to refresh the current report - if i select the option close then i get the following error

2.An internal error occured while calling 'processDPCommandsEx' API. (Error: ERR_WIS_30270) (WIS 30270)

If I use an "Optional" Hierarchy Node variable instead, I don't have any issues. But the requirement for the report is to have a mandatory variable.

Appreciate if you could share SAP's reply.

Regards

Abhiman

[Former Member]

Hi  Vinay

As per SAp Note "1877252 - "An internal error occured while calling
'processDPCommands' API. (Error:ERR_WIS_30270)" while refreshing WebI report in
XI 3.1"

Cause

Security access level of an object in Object properties is set to
Confidential at Universe level

Resolution

1.  Login to Designer.

2.  Double click on Object.

3.  Go to the Advanced tab.

4.  Change Security Access Level of object to
     "Public" from "Confidential".

------------------------------------------------------------------------------------------

As per SAP Note " Internal Error Occured While Calling
'processDPCommandsEx' API. (Error: ERR_WIS_30270) (WIS 30270)“."

Resolution 

1. This issue is being tracked under Problem Report ADAPT01615411 and is
   targeted for fix in the BI4.0 SP04 release.
2. The issue has been identified and tracked under Technical Escalation ID
   5000408449.

Thanks & Regards

Sandeep

[Former Member]

Hi Vinay,

Try one of the below solution

Scenario 1:  Error occurs when try to refresh a migrated Web Intelligence report in InfoView, after entering a date or dates for prompts.
Suggested Solution:

1. Modify problematic report in Webi.
2. Change the prompt definition to be a constant, run the report in Webi, and save it.
3. Change the prompt definition back to prompt with required date definition. Make sure you are using the correct date format! (The report prompt should tell you what the format is supposed to be.) Re-run the report in Webi, and save it.
4. Re-open the report in InfoView and refresh.

Scenario 2:  Error occurs when trying to edit the properties of a Webi report containing merged dimensions.
Suggested Solution:
Remove the merged dimensions and then re-establish them.

Scenario 3:  Error occurs when the InfoView report has been open and idle for a long time.
Suggested Solution:
This error can be an indication of a time-out, based on the server’s settings.  Make sure you save your work often.  You will need to close and re-open the report when you get this error, and you may have lost any unsaved changes.

Thanks & Regards,

Pravin P. Kumbhar

[former_member196240]

Hi Experts,

I have just removed the hierarchy variables from the bex query and saved it, then ran webi report it was able to run without any error.

When i again added back those hierarchy variables in the bex query, the issue comes up.

I think something is wrong with the hierarchy variable, any idea?

Thanks,

Vinay