Web user receives error when exporting to excel 1

[talenx]

Hello all,

I hae ran into a little issue that i haven't been able to resolve. have any of you seen an error like this? if so where would i be able to go within the MS tool to set a maximum export threshold?

note: the report that we a exporting doesn't have any export option specs applied to it, nor does it go over excel's limits of 255 column or 65535 rows

"Unable to export


You cannot export this report because it has exceeded the limits that the Administrator has set for the maximum number of columns and rows to export to Excel, CSV, or HTML. However, this report can be exported to plain text by selecting this option either from preferences or when prompted before exporting.

Please perform some manipulations on the report or contact the Administrator.



--------------------------------------------------------------------------------
Copyright © 1996-2002 MicroStrategy Incorporated. All rights reserved. Confidential. "


any suggestion would be great..
thanks
talenx

 

[jonhoward]

assuming you're using mstr7, the max number of rows that can be exported to excel is 4000. but, the default is set to 1000 - and that may be the problem.

taken from TN5600-7X0-0100.........

As Web Administrator, select the link to 'Export' from the Preferences options.

Select the link to 'Project Defaults' under the 'Preference Levels' options in Export preferences.

Select 'Export' from the Preferences options in the project defaults.

Locate the setting 'Maximum Number of rows to export to Excel, Lotus or HTML' in the Export options.

Scroll to the end of the page to apply these settings.

 

[talenx]

remarkable work my friend, thank you very much!!!! I had searched all over for that when it was right under my nose in the first place.

again thank you.
talenx

 

[talenx]

Oddly enough even though i changed the maximum to 4000 rows a report that contains 3701 rows triggers the following error:

(reportname)
Error in report results

Request timeout.

this error is exported into excel.

any thoughts?
thanks
talenx

 

[chael]

This is a fairly common error. TN5600-7X0-0276 addresses this...but you probably don't need to go to the extent of actions that the TN goes to...

If the report was cached, delete the cache, re-run the report and try again. This error sometimes comes about when a report has a message ID that doesn't quite match up against the binary or XML caches stored on the server.

Chael

 

[talenx]

thanks for the quick reply

though..
even after i purged the reports cache i still received the error

oddly this error is only triggering it's self when the report is exported from the web client. the desktop client has no problems exporting the report.

thanks
talenx

 

[chael]

This is probably a job for tech support....but there are still ways of narrowing the problem down on your own...

Does this happen with smaller reports (i.e. 50 or so rows)?
Does this happen when exporting in plain text?
What version of Excel are you exporting to?
Can you get any of the export options to work in web (csv)?
Does this occur for all reports or only for one report?

If the last is true then simply re-saving your report could do the trick...but you really should open a case with this. They can recommend whether some of the recommendations in TN5600-7X0-0276 are suitable for your sitaution.

Chael

 

[jonhoward]

Have you looked at the 'Request Timeout' setting in Web Administrator? The report may run in Desktop because the Governing characteristics in Project Configuration are fine, but the settings for Web are too low.

As a starter you could look at changing this setting to a greater value than it currently is - as a one-off change give it a BIG increase. Assuming it works you can then do some interrogation to get it down to a much more sensible size.

Of course, I could be miles off on this...

 

[talenx]

Thanks for the advice; I will submit a ticket today.

Just so you know the report errors out on the following

1. I can export the first page of the report with no problem through the export option to either export the whole report or just the displayed data

2. It does error out when exporting to plain text. Or any other format.

3. Excel 2000 on all user machines

4. (Csv) show the error has been export to it.

5 any report that needs to export 3000 + records

Thanks
talenx

 

[talenx]

Thanks
I attempted to increase the request time out from 40 to 80, unfortunately the report still errors out when attempting to export. Oddly the report doesn't perform the full 80-second count when exporting, from the time I click the [Export] button to when the report errors out is about 47 seconds.

Thanks
talenx

 

[talenx]

FYI
I checked my error logs in the Web Administrator
and found an error entry for every time I tried to export.

Time = ''

User = ''

Level = 1

Error number = 451

Error Source = Microsoft VBScript runtime error

Error Desc = Object not a collection

File = PreviewCuLib.asp in preview.asp

ASP function = SetPageBy

API function = Set aPreviewRequest(O_REPORT_INSTANCE_PREVIEW_REQ) = aPreviewRequest(O_REPORT_INSTANCE_PREVIEW_REQ).ReportManipulator.ApplyChanges()

Comments = Error in SetPageBy

Any suggestions would be great.
Thanks
talenx

 

[talenx]

STATUS UPDATE:
well it turns out that there was a few things that contributed to this issue.

The 'Request timeout' setting is the length of time the Web server waits for a response from the MicroStrategy Intelligent Server. If a response is not received within the timeout setting, a 'request time out' error message is displayed to the user. The default Request timeout setting is 40 seconds ( i set it to 3600)

Increase the JVM Heap Size to 256 MB. The JVM Heap size determines the amount of memory that the Java Virtual Machine in the Web Server can use. When exporting a report, MicroStrategy Web request all the report data from MicroStrategy Intelligence server. The Java Virtual Machine Heap Size Memory needs to be large enough to hold the result set. The recommended value is 256 Mb.

To change this setting, open the registry of the Web Server machine. Look for:
\HKEY_LOCAL_MACHINE\Software\Microstratetgy\JNI Bridge\ Configuration\JVM Options\HeapMaxSize.


Change this to '256M'

ASP Script Timeout/ Session timeout: To change this setting, open the IIS Console. Right-click on the MicroStrategy7 virtual directory and select 'Properties'. Click on the 'Configuration' button in the Application Settings section. Select the 'App Options' tab and modify the Session timeout and ASP Script timeout to a bigger value. A good start value would be 40 minutes.

After I made the above changes the reports seem to export with no problem.

Thanks for all of you help,
talenx