cancel
Showing results for 
Search instead for 
Did you mean: 

CORBA.MARSHAL error in BI 4.0 SP2 Patch 4 while creating report

former_member230867
Participant
0 Kudos

Hi,

we are encountering an error message while trying to create a report in BI Launch Pad (BI 4.0 SP2 Patch 4). It contains the following:

The MDAS service encountered an error.

com.crystaldecisions.thirdparty.org.omg.CORBA.MARSHAL minor code: 0x0 completed: No

Workflow:

Logon to BI LaunchPad

Launch Analysis for OLAP from Applications

New Report

Search for Data Source

Select a known working query

Click OK - receive error

Click OK to error

Try to add a dimension - receive error

Any ideas? It is a showstopper. Thanks.

Erik.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member230867
Participant
0 Kudos

Hi all,

we have opened a SAP message to this error, I will update the findings than.

Erik.

Former Member
0 Kudos

Erik,

Were you able to solve this error? I am facing the same.

Thanks,

Prasanth

former_member230867
Participant
0 Kudos

Hi Prasanth,

we have opened OSS message for this issue - SAP recommended to install Patch 6 whcih should resolve it. We did install Patch 6 today, but currently facing another problem with Patch6 web application deployment. I will update the thread as soon as we will test it.

Erik.

Former Member
0 Kudos

Thanks Erik.

Am already on Patch6 and facing the issue.

You can try using the Wdeply to fix the web application deployment issue.

Regards,

Prasanth

former_member230867
Participant
0 Kudos

Hi Prasanth,

so then perhaps that Patch 6 will not solve it:(

I am running BI 4.0 on NW 7.3 WAS. The problem is that somehow I do not see the Build version updated (for Patch6) in CMC Settings after redeployment. What build version do you have under CMC on Patch 6?

Erik.

Former Member
0 Kudos

Build number: 439

Patch06 might still help you solve the issue. I had also logged a ticket with SAP and found that installing patch06 on top of patch04 solved the issue for some customers. gud luck.

Cheers,

Prasanth

former_member230867
Participant
0 Kudos

Hi all,

Just to confirm, Patch 6 has resolved this issue.

Erik.