Skip to Content

Error while opening webi report

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 02, 2013 at 01:29 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Vinay Kumar

      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

  • author's profile photo Former Member
    Former Member
    Posted on Jul 05, 2013 at 02:19 PM

    Hi,

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

    Best regards,

    Victor

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

  • Posted on Jul 02, 2013 at 01:04 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 02, 2013 at 01:42 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.