Error: ERR_WIS_30270 (processDPCommandsEx API)

building reports webintelligence
1

Hello Gurus,

I am getting following error message when I try to refresh a Webi report in Launch Pad.

Thanks and best regards,
Deniz

Deniz (BOB member since 2008-04-01)

2

Does the report work from Infoview or Rich Client? i.e. is it only a Launchpad issue?

3

Mark, BI Launchpad is the new name for InfoView. :roll_eyes:

Is the universe in UNV or UNX format? Have you tried refreshing it from the Rich Client application?

MichaelWelter :vatican_city: (BOB member since 2002-08-08)

4

Hi all,

I am using a BeX query as data source. So there is no universe.

Thanks and best regards,
Deniz

Deniz (BOB member since 2008-04-01)

5

Unfortunatelly pretty general error,

What I can recommend (if you use BICS)

  • Try in SAP BW if query run (the best way is to run in transaction rsrt2),
  • If you changed any attribute in your bex query you have to make change datasource in your document (Data Access/Tools/Change Source) to the same query
  • If it don’t help check if you APS server run OK, sometime it need to restart (maybe DSL server), check logs on your server,…. .

Martin

MartinSoka :slovakia: (BOB member since 2011-09-18)

6

Also, make sure you are on the current patch level, which is as of today: SAP BI BusinessObjects 4.0 SP02 Patch 11.

What version and patch level is the SAP BW system?
Is this a plain vanilla SAP BEx query? If not, test with a plain vanilla one.

Andreas :de: (BOB member since 2002-06-20)

7

Any suggestions or answers on this?

I am getting this same error when running a report on demand (“Run Now”) in the CMC or when it is scheduled. My report has 3 queries linked together as follows…

Query 3 criteria specifies that a key element be present in Query 2.
Query 2 criteria specifies that a key element be present in Query 1.

I can get the report to run in WebI if I refresh the queries in the proper order (1 then 2 then 3).

I am assuming is has something to do with Query 2 trying to run without Query 1 having been run.

This was working. We just upgraded to BI 4.0 SP4 (14.0.4.738) and our issue may be due to that.

Thanks,

Noel

nscheaffer :us: (BOB member since 2012-04-26)

8

@ nscheaffer

Hi Noel,

Did you ever resolve this? We are on BO XI 4 SP4 and I am getting this error on reports that previously worked fine.

Thanks
Lynne

Lynnieshell :uk: (BOB member since 2012-09-18)

9

Hi, I’ve had the same problem and I solved it a few minutes ago.
I had to restart the ConnectionServer.
Now everything is ok.

helle (BOB member since 2010-06-08)

10

Hello All,

We have just started getting this error on all of our BEx Query reports. They previously all worked fine?

We are on B! 4 SP5

Anyone got any ideas

Thanks
Dan

bhafcdan (BOB member since 2005-01-21)

11

User Server Groups to test each of your Web Intelligence Processing servers with the same report. We found this message occurred when one or more WIPS had corrupted. A report run on that WIPS would always fail.

Nick Daniels :uk: (BOB member since 2002-08-15)