cancel
Showing results for 
Search instead for 
Did you mean: 

BO BI 4.1 - patch 5 in SP3 in a more recent SP ?

Former Member
0 Kudos

Hi,

I work on BO BI 4.1 SP4 (version 14.1.4.1327) and I found a note (2043161) that could fix my problem ("An Internal error occurred while calling 'opendocument API . (Error:ERR_WIS_30270)( WIS 30270)").

This note give the patch 5 as a solution but for SP3.

So I looked in SP4 and I didn't find the equivalent.

Do you know in which SP / patch I could get it ?

Regards

Olivier

Accepted Solutions (0)

Answers (2)

Answers (2)

CdnConnection
Active Contributor
0 Kudos

Olivier,

     This is very generic error.   It could be related to JAVA crash, APS not sized properly, WebI Process server crashing and even your over memory not sized properly.

Need more details:

  • What is OS ? ver?
  • How much system memory?
  • Typically how many users on the system?
  • How did you split the APS?
  • Any custom memory setting for the APS?
  • What type data source being used?  BW/BICS   or UNV/UNX

Regards,

Ajay

Former Member
0 Kudos

Hi Ajay,

actually, the problem is about only one report so, I don't think that it is caused by server configuration.

My question is, where could I find an equivalent of patch 5 in SP3 (for the problem described in the note 2043161) for my version of BO in SP4.


Regards


Olivier

mhmohammed
Active Contributor
0 Kudos

Hi Oliver,

Speaking from my personal experience, doesn't matter if its an issue with just one report, it can still be due to Server configuration. How big is the report?

We had an Open Transactions report, as the name itself suggests, it was a pretty heavy report as it had data for all the open transactions, we had issue in scheduling and/or while opening this report as it used to take long time to run it.

Hope that helps.


Thanks,
Mahboob Mohammed

amitrathi239
Active Contributor
0 Kudos

Hi,

This is more generic error.check if the reproduce steps are same  as your steps.

when exactly are you getting this error.

Amit

Former Member
0 Kudos

Hi Amit,

the error occur when opening the report in the launchpad.

Olivier