Error WIS 30270 Internal error call API 'processDPCommands

building reports webintelligence
1

Error WIS 30270 Internal error call API 'processDPCommands.

When I’ll try to run a Webi Report (BusinessObjects XI R2), always I’ve the Error WIS 30270 Internal error call API 'processDPCommands.

Does anyone could help me?

I’m working with a Oracle 9.i conecction. This error always happens in the universe with this connection, in universes connected for example with ODBC not give me any error.

Thanks.

emicheca (BOB member since 2008-04-21)

2

Have you made sure the oracle client is on the webi server that you are connecting to? If it has, make sure the tns names file is also present there.

Make sure it is an oracle 9i database yiu are connecting to.

Make sure you are licensed to use oracle connections.

jonathanstokes (BOB member since 2004-09-17)

3

The problem is something related to your Oracle Connection itself.

If your oracle client is installed on Unix;

Just check your LD_Library_path for Oracle connection.

It should be pointing to lib32 directory if you are having lib32 directory in /u01/app/oracle/product/10.2.0/client/ folder.

chetanmaniar :india: (BOB member since 2008-02-06)

4

Hello again, I still have the same problem.

I’ve made Reports in Desktop Intelligence, but I’ve not had any problem with the same Oracle universe.

I’ve made querys in SqlPlus too, so I think that my TNSNAMES is correct.

Any idea?

Thanks

emicheca (BOB member since 2008-04-21)

5

Take a look at this post. Looks very similar to yours:

jonathanstokes (BOB member since 2004-09-17)

6

Thanks, making

works properly.

emicheca (BOB member since 2008-04-21)

7

Can you please share making what solved your problem. Couple of solutions are suggested in that thread.

Thanks.

queryanalyzer (BOB member since 2005-08-28)

8

I am also facing same error,
“An internal error occurred while calling the ‘processDPCommands’ API. (Error: WIS 30270)”

can anyone share solution for this … :roll_eyes: :roll_eyes: :roll_eyes:

Vills :india: (BOB member since 2007-10-24)

9

Hello,

I had the same issue.
The problem is related to file source of the report not found.
I fixed the issue by editing the source of the report and affect it a new source Excel file.

Regards,
MH