Report Studio Error

[ab5602]

Hi, we are having a very strange error with Cognos report studio:

When the server loads metadata objects in the pane that says "Insertable Objects" and when more than about 8 users are using the server at the same time, the page times out and an error window appears which is titled "BI Bus Error".  And in the window, there is the following text:

------
The server returned and unrecognizable response: It is either incomplete or empty.

12152: Unknown
------

Has anyone seen this problem before?

Thanks for reading!
-Rob

[Darek]

What's your environment like ?

[cognosfreelancer]

Most likely you have kept the default timeout vakue of 30 seconds for the Report Service process.

Log into server administration and increase the wait time to about 60 seconds.

There is a lot more that can be done as far as tuning is concerned as and when you answer Darek's question.

NKT

[Mooski]

Hi guys,

Firstly, I'd like to say how fantastic this whole place is and I hope that I can give something back to the community when I have something to offer, that is!

Secondly, my apologies for bumping this old thread, but it is relevant to a problem I have at my current workplace.

It seems that we are having some problems where some of our users are trying to export reports to either Excel or PDF, but nothing seems to be produced: the cube keeps turning.  Now on my laptop (which isn't a great spec, to be honest) I can get both Excel and PDF without too much of a delay.  My initial reaction was laptop specs, but as mine has only 256MB or RAM, I'd like to ignore this option.

My thoughts then went to timeout lengths and if they could be specific to laptops.

Is this possible?

Many thanks and keep up the good work!

Mooski.

[MFGF]

Hi,

Are you saying you have the Cognos ReportNet Server software installed on your 256Mb laptop? Or are you using it just as a browser client?

The timeout referred to by cognosfreelancer is a server-based setting, so if you are connecting into a central ReportNet server it will apply not just to you but to all users.

When rendering non-HTML outputs (PDF, CSV etc), the ReportNet server has to render the entire report in one go, whereas with HTML rendering it can produce a page at a time.  The perception for the end user is that non-HTML rendered reports take longer to run, particularly for long reports.  For a single-page report there should be no difference.  Could this account for what you are seeing?

Just a thought...

MF.

[Mooski]

Thanks for the reply, MF, it's much appreciated.

I'm using the laptop as a client, as you suspected.

I did some testing with various date ranges for the report and found that for a month of data, it was taking up to 25 minutes to view with PDF, so this is a bulky report.  My guess now is that the users that are stating "It does't run!" are just being impatient and don't know how big these reports actually are.

I'll take what you said about the difference in rendering the reports in HTML/non-HTML and explain that to them.  Hopefully, they'll understand this and we can put this to rest now.

Many thanks again, MF!

[MDXpressor]

Mooski,
Try and get your users familiar with the Run With Options function.  That way the server can render the report, save it (or e-mail it to the user) and the user is not actively waiting on the report.  In my experience people patience is put to the test when left to count the revoultions of the spinning cube...