Report timeout

[Former Member]

I am working on a new install of BPC 10 NW. I just attempted my first report and recieved an error

MDX statement error:"Error occurred when starting the parser: timeout d"

Does this indicate my install is broken? It is meant to be the latest version of BPC so I would have thought by now it was stable enough to run a simple report. Has anyone else had this problem? If so, how did you fix it?

Thanks

Cliff

[Former Member · Accepted solution]

Have you checked that your MDX parser connection is still ok via SM59?

[Former Member · Accepted solution]

What I have discovered is that if I select base level members of a dimension on rows, even a large number of them the report runs in about three seconds. As soon as I introduce a rolled up member (node?) the report fails.

I checked SM59 and under there saw a MDX connector. I clicked on it and saw a place to run a connection test. This produced the result below.

I'm new to this whole Netweaver thing but it looks as if the MDX parser is broken. How do I go about fixing it?

Thanks

Cliff

[former_member190501 · Accepted solution]

Dear Cliff,

Check with your basis team. They will know how to resolve this connection issue.

Thanks,

Raju

[raghu_ram · Accepted solution]

Hi Cliff,

You can look at SAP Note 1032461 - MDX parser does not start.

Regards,

Raghu

[Former Member · Accepted solution]

Hi Raghu

The note said I needed to ensure all my copies of librfc32.dll are the latest. I discovered I have four copies (in separate directories) with different dates and sizes. I replaced the old ones with th elatest and then discovered I was not able to start SAP. Just trying to reach the login page gave me this error.

I reverted to the old mixed copies and the problem went away. At this point  have to assume that despite the SAP note, the BASIS person who built this image has got the correct mix of DLLs.

Thanks

[Former Member]

I've made some progress. The MDX Parser is running again. I don't know what killed it and why it restarted but I will check the note Raghu has suggested so I can fix it next time.

I have discovered another thing about the time out. As I stated above, the report is not dealing with large amounts of data. I have now proved that:

• a report with rows as children of a current context and without ticking "include starting member" works if the context is one level up from the base, ie all we're returning is base members.
• If we include the parent and have "order parent after" it still runs, taking about 2 seconds.
• If we change the order to parent before it times out after 60 seconds. It will do this even for a small report.

Clearly the problem is with aggregating data, even very small amounts. Has anyone else experienced this?

Thanks

Cliff

[former_member190501]

Hi Cliff,

Can you check point 4 in below note.

Note 1691567 - Use Calculated Time Hierarchy for better report performance

Hope it helps to improve performance at parent level.

regards,

Raju

[Former Member]

Hi Cliff,

Do you face the similar problem if you open any of the predelivered templates?

Can you try with a smaller data region to see whether its the problem with huge volume of data or not.

[former_member210696]

Hello Cliff,

It might be because of the processing large amount of data and it gets time out before it could process that.

You may try increase the session time out. Look at below thread on how to increase the timeout -

http://scn.sap.com/thread/2119376

Hope it helps!!

[Former Member]

I tried it on the rates cube for a single month so I should be getting a tiny amount of data. I'll take a look at the timeout value but would be surprised. I suspect the mdx is simply not running.