The action cannot be performed (WIS 30650)

[Former Member]

Hi,

Created a new webi report in webi rich client , published to repository and it works fine. Opened that webi report in rich client , done some modifications(added an input control and modified the formulae according to the input control values) and saved the report back to repository. Now ,

When opening this webi report in richclient throws error:The action cannot be performed (WIS 30650)

When trying to view in BI Launch pad, it throws error : Action cannot be performed (Error:INF)

When trying to modify in BI LaunchPad, it throws error: Load driver Call : InitDrillEngine (WIS 00000)

I have checked on an SAP note : 1604932 - But it doesn't help as the query stripping feature is not used in the report.

Could someone please help on this ?

SAP BI 4.0 SP2 Patch 14

Thanks

Pappu K

[Former Member]

I am facing the same error when trying to view the report migrated from BO 4.2 to 4.1.

Our Quality environment has BO 4.2, where as Production environment is still on BO 4.1 version.

Appreciate if you could help us with the fix.

[former_member207003]

Hi Mehurllah,

Even though the error message is the same, migrating reports from a higher version of BI to a lower version, ie. migrate from 4.2 to 4.1, can cause your reports to become corrupt or throw various different errors. This way of migrating content has never been supported or recommended in BusinessObjects. To resolve the issue and keep your content in sync, both environments should be the same version. Either 4.1 or 4.2.

[Former Member]

Hi,

Have you had any solution, I am getting the same error but I could open in launch pad but not in webi richclient.  user made changes in Webi Richclient and saved onto repository now when any opens the report it gives error action can not be performed.

Appreciate if you could help us with the root cause of the issue.

Thanks

[sourav_roy83]

I am facing the same error . I am on 4.1 SP7 .The bug was initially not there but it suddenly cropped up out of the blue .

I am working on Audit universe with DB2 10.5 32 bit JDBC drivers . Everything was working fine but suddenly the error has started cropping up since last 48 hours .

[Former Member]

Hello Roy,

last weekend I heve upgraded my BO to 4.1 SP07. I have the same issue. Have you found any solution?

[sourav_roy83]

Hello Piotr,

The issue is not resolved for us . We have to deploy db210.5 JDBC 32 bit driver files and configure db2.sbo file for WebI Rich Client to work . But the steps are making WebI Rich Client fail to work .

[Former Member]

Hello, I like to share our conclusion about this mysterious error.  This occur since we migrate scheduling from XI 3.1 SP2 ro BO 4 SP5.  It occurs on arround 10 % of thousand scheduling.  We found and fix this by setting correctly our multiple caching webi processing server.  It was because we didn't put UNC path for the caching folder.

Maybe it can help....

Good luck

[natasa_nakic]

Hi Patrick,

We saw similar issue after upgrading from 4.1 to 4.1 SP4. Only 3 out of 20 jobs could not run in scheduler. Some were very simple reports, no contexts, no prompts, some more complex. No common thread. One could run when scheduled in 4.1. SP3 though but we'd like to stay on SP4 because of other fixes.

You wrote "we fixed this by setting correctly our multiple caching webi processing server". I could not find that setting in CMC. Could you please advise further on where to make the UNC path change?

Thanks,

Natasa

[Former Member]

Same issue - upgrade from 4.1 SP1 to SP4 over past weekend and then a bug fix on Tue.  Now this error pops up in Rich Client with webi report.  Not scheduling issue - it's a run on demand report.  Does use ODBC for one universe connection.  Maybe upgrade to SP4 version of client tools?

Thanks,

Tom

[natasa_nakic]

Hi Tom,

I have all SP4 client tools installed already (Rich Client 14.1.4.1327) and have not seen this error in Rich Client yet.

In fact, there were several WebI errors that could not refresh after the SP4 upgrade from url and I was able to fix them by opening in Rich Client-> Edit query, rebuild SQL, run, save as a new report or some similar back and forth. I'd suggest to definitely install SP4 rich client and hopefully your issue will go away.

I have lots of issues with default contexts after the SP4 upgrade. The previously saved contexts are not recognized anymore and I have to uncheck the default context in the Parameters of the query. Watch out for that.

I also had a strange purge issue. I would purge the cubes, the number of rows in all data providers would show as 0 but the data were still visible in the reporting view as if nothing happened. The report could not be saved after that, WIS 30567.

An unusually high number of regressions for a service pack. I hope the SP5 will address them properly.

Good luck!

Natasa

[Henry_Banks]

Hi,

Are you in a position to evaluate a higher SP?  the final fix on SP02 was Patch21 in October last year.

SP02 and FP03 have been out of maintenance for some time, so customers should be on SP04 or SP05 with a later Patch4.x or 5.x to be benefitting from corrections.

IMO, there is very little value in investigating on this release, as things have really moved forward on the other active codelines.

Regards,

H

[Former Member]

Hello all!

Unfortunately until now I couldn't solve my issue.

http://scn.sap.com/message/13982575#13982575

Now I hope to set BO SP5 instead of SP4.

May be this will help me.

Thinks and Regards

Pavel

[Former Member]

We have this strange error too.  But it's random when we schedule report in BO 4 SP5 Patch 3

[former_member220738]

I have same problem as you, on SP2 patch 2.7

Yesterday i wanted to up one of the folders in my universe to the higher level.

After that i exported univers, but because of SP2 bug, my changes did not applied to reports.

On next day then I open report, where was your mistake -  Load Driver Call : InitCube (WIS 00000)

without any Query stripping enabled, mistake was on ALL reports

The solution was to rollback old universe. All good now.