Discoverer Plus4i - Exporting to Excel - Your server is running low

We are currently running Discoverer Plus 4i.
We have a couple of large reports that we want to export to Excel.
We retrieve the report and then carry out the 'Export to Excel' action. The export starts to run but during the 'sort' phase we are getting the error "Your server is running low on virtual memory".
The largest report is currently retrieving about 64K rows but will grow by at least another 20K.
I appreciate we could restrict the retrieval through parameters but we were wondering if anyone had encountered this before and if there are any solutions out there.

Hi,
Any chance any of your items are created using custom functions/packages that return varchar's? If so, check you max char fetched (admin edition - properties tab, each item in folder(s) used by the report). The columns created by custom functions/packages will probably be 4000 characters. Excel doesn't like this. This also slows down your report. Wrap your custom function call in a substr and reduce to the correct size. This might fix your problem.
If you don't use custom functions/packages in this report, oh well, just a thought.
Regards,
Nancy

Similar Messages

The server is running low on virtual memory.

When running a sheet in discoverer I am getting the following error after around 10 mins
The server is running low on virtual memory. This can happen due to insufficient disk space or heap space on the server. Please contact your Discoverer Administrator for assistance.
I have changed the following settings to
maxvirtualdiskmem = 4096000000
maxvirtualheapmem = 4096000000
The query returns 625500 records with parameters selected
and 834360 records without any parameters set
Can anyone help

Memory usage is going to depend on several things. While rows returned is part of it, other things like sorts, calculations, page items and report type can have a huge impact. Out of curiosity, is the report a crosstab? are there a lot of sorts, of some complex calculations?
How many users are accessing Disco at the same time, and is there anything else on the same box as Disco?
Also, after you changed the settings (and I am assuming the change was made to pref.txt), did you run applypreferences.sh and then bounce the app server? If not, the changes have not taken place.

Job in BODS is failing with an error " Your system is running low on process virtual memory".

hello,
I am facing an error with one of my job which is running on BODS server. The job is failing daily since last one year with the same error " Your system is running low on process virtual memory". We checked with team which deals with space issue and the space is sufficient enough.
Please help me with this error and what can be done to do away with this.
Regards,
Ritu Sharma

Greetings Narendra,
It may help if you were to explain in more detail the software product you are encountering this issue. There are about 500 different products that might be encountering this issue. Specifying which product you are using will assist the Forum Team in providing an appropriate response.
Thank you,
Rob
Technical Engineer
Customer Assurance

Discoverer issues exporting to excel

i'm using OracleBI Discoverer Viewer Version 10.1.2.48.18 and some users claim that when they try to export to excel they get the following message: The exported document no longer exists. An exported document is not maintained after the first download. If you wish to view the document again, please perform the export again.
I'm able to replicate the error but only after I export and then I closed the workbook in excel. If I re-run the report I can export but for the users whith the problem they can not even export the first time.
any idea of what the problem is?

Hi,
I am using Discoverer Viewer .....
Wherein there are few parameters based on which we can drill down to reports
BUT
when i click on Export to Excel option it displayin all d reports one after d other
But can't it display in d same way like hierarchy and allow user to drill down based on parameters
Any suggestions please....
Thanks in Advance

ALV List export to Excel when program is run in background

Hello,
I am running into an issue with a custom ALV report which contains an export to Excel option on the input screen. However, when I attempt to run the report in background due to high volume of records/expected performance constraints, the job fails to produce a spool when the "export to Excel" option is selected. When I deselect that option, the background job successfully generates a spool, which I can then export to Excel (albeit the formatting will not look the same).
Is the above an accurate statement or does anyone know of a way where either;
1) The background job can create and store the Excel output into a cached directory?
2) The spool generated, when exported to Excel, can match the format of the foreground Excel output?
Thanks in advancce.

Check out the sample program of the provided link ..
http://www.sap-img.com/abap/download-in-background-in-excel-format.htm

SAPUI5 Export to Excel in Server side

Hi Experts,
I have a requirement to export SAPUI5 table to excel.
I tried different client side download and most of them failed in IE browser
Export sap.ui.table.Table as CSV
http://jsfiddle.net/hybrid13i/JXrwM/
Can anyone able to guide me to implement it in server side?
In my UI5 application I am having JSON data.
one way is :
I will create a "form" and will set the content in that form. And will submit that form.
$("#myForm").submit();
Now I have to route this to my java server class for converting it to excel. In that point I am struggling.
Can anyone help me?
Regards,
Jacob

Hi,
Check if this blog Displaying backend data both as SAPUI5 Table and an Excel File helps you.
Regards,
Chandra

Discoverer plus : Export to excel sheet is blank after upgrade to 10.1.2.3

Hi All,
We have done the below changes in the discoverer
1. Moved to 10.1.2.3 from 10.1.0.2
2. Applied April 2009 CPU
3. Applied Cumulative 3 patch for 10.1.2.3
While performing the testing we have received complains that the export to the excal sheet is not working and the page is coming blank.
Please advice
Thanks & Regards,
Rakesh

Hussein,
Yes, this is happening for all workbook and also Web Query functionality which allows us to automatically refresh reports in Excel is not working, its not displaying the data. only the headers are displayed.
And we are using the certified version and it is wokring before we apply these patches
Thanks & Regards,
Rakesh

Export to Excel '07 doesn't run the formatting Macro

I've searched Metalink for more information on this topic, but haven't anything usefiul. Has anyone run into this?
We're on 10gR2 (10.1.2.2)
Appreciate any help anyone could throw my way.
Brent

Kumar,
Thanks for your suggestion. I've already set the Export All Rows property on the exportButton item to True. I don't think we need to have the View objects for both the regions on the page.
As I mentioned this works fine in JDeveloper with different VOs associated with the regions.
It is not working once I deployed it to Apps Instance.
Thanks,
Satya

Warning Your system is running low on process virtual memory space

Hi,
I face this problem when i use a flat file source with about 19000 records (about 6 mb size).
The job starts there is no error message but it just halts no progress....
Can anyone help.

Greetings Narendra,
It may help if you were to explain in more detail the software product you are encountering this issue. There are about 500 different products that might be encountering this issue. Specifying which product you are using will assist the Forum Team in providing an appropriate response.
Thank you,
Rob
Technical Engineer
Customer Assurance

Discoverer: Export to Excel not working properly on XP sp2

Hi,
In Discoverer, after exporting to Excel the spreadsheet should be displayed automatically. It works fine on Windows 2000, XP sp1, but not on XP sp2.
Any suggestions on how to fix that problem?
Thanks,

Sonal,
Did you try using the context menu to export the results?
I faced the same problem. I could not export using the export functionality but worked when i used the context menu.
Left click on any result area --> Enhanced Menu --> Export to.
hope this helps
Mustafa

I get this when i try to add photo to iphoto:The disk containing your iPhoto library is running low on space.

i get this message when i try to add photo to iphoto: The disk containing your iphoto is running low on space

1 - NEVER assume - it makes an "*** out of u & me"
2 - for the third time - how much space do you have on the drive where your iPhoto library is located?
If you continue to refuse to answer that simple question then no one can halp
LN
PS - your iPhoto library is NEVER automatically moved anywhere - to move it
Moving the iPhoto library is safe and simple - quit iPhoto and drag the iPhoto library intact as a single entity to the external drive - depress the option key and launch iPhoto using the "select library" option to point to the new location on the external drive - fully test it and then trash the old library on the internal drive (test one more time prior to emptying the trash)
And be sure that the External drive is formatted Mac OS extended (journaled) (iPhoto does not work with drives with other formats) and that it is always available prior to launching iPhoto
And backup soon and often - having your iPhoto library on an external drive is not a backup and if you are using Time Machine you need to check and be sure that TM is backing up your external drive
LN

Export to Excel Error in SQL Server 2014 Report Builder/Viewer

Hi,
I am using the 2014 version of ReportViewer in a WinForm to display an RDL report.
The report was originally created in Report Builder 2.0 (SQL 2008 R2), but has since been edited in Report Builder 3.0 (SQL 2014).
The report loads and displays OK, and even exports to Word and PDF. But when exporting to Excel and then opening the Excel document, the following error occurs:
"We found a problem with some content in <filename>. Do you want us to try and recover as much as we can? If you trust the source of this workbook, click Yes."
If you click Yes, then a second message appears:
"Removed Part: /xl/styles.xml part. (Styles)
Repaired Records: Cell information from /xl/worksheets/sheet1.xml part"
The Excel document then opens, and the data is there, but there is no formatting (no border columns, colours, bolds etc.)
The three interesting things are:
- When exported from SQL 2008 R2 Report Builder 3.0, which exports to .xsl instead of .xslx, it works
- A brand new report created in 2014 Report Builder 3.0 exports to .xslx great
- In Report Builder 2014, I stripped everything back and removed all rows and columns so the original table in the report only has one empty row and column it the export still errors - it is only by removing the original table and creating a brand new table
that export works OK
It appears to be a problem with the tablix, but ideally we don't want to have to recreate our reports from scratch to fix this issue.
Has anyone come across an issue like this before, and know of any potential resolutions to it?
Thank you.

Hello,
Based on your description, you render a report originally created in Report Builder 2.0 (SQL 2008 R2) and export the report to excel with format of Excel 2007-2010.
Edit the report in Report Builder will not upgrader the report. In that case the report still with SSRS 2008 R2 RDL schema. Please try to upgrade the report by open the report in Report Designer in SQL Server Data Tools (SSDT) and then try again.
If you don’t want to upgrade the report, please try to export the report
with Excel 2003 rendering extension and check if the issue persists.
The SQL Server 2014 and SQL Server 2012 Reporting Services Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010 with .xlsx as file extension. Only the Excel rendering extension is available by default.
You must update the Reporting Services configuration files to make the Excel 2003 rendering extension available.
For example, changing the value of Visible to
true in the following line in the RSReportServer.config:
<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"
Visible="true"/>
Reference:Upgrade Reports
Exporting to Microsoft Excel (Report Builder and SSRS)
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SQL Server 2014 Reporting Services export to Excel

Hello,
We recently upgraded to SQL Server 2014 from 2008 R2.
In SSRS With the new version of SQL Server we are having an issue with the Cell Border Expression logic when exporting to Excel.
This Cell is a Grouped By Column on the Staff ID
Here is the expression for the Cell Border
BorderStyle:
=IIF(Fields!StaffParttime.Value = "Y", "Solid","None")
The report renders correctly however when exporting the report the Border is not correct in the spreadsheet.
Example: Cell 1 Parttime = "N" there is no border, Cell 2 Parttime = "Y" there is a border, Cell 3 Parttime = "N" there is a border
Cell 3 should not have a border, also the subsequent sheets all have borders when they should not. Once the border is set it does not change.
Has anyone had this same/similar problem and if so what was your resolution?
Thanks

Hi Jrod T,
Based on your description, you are experiencing an issue with the Cell Border Expression logic when exporting the report to Excel, you can’t see the expression added for the Border Style (=IIF(Fields!StaffParttime.Value = "Y", "Solid","None")
) work fine in the recently upgraded SQL Server 2014, right?
I have tested it on my local environment in both the early version and the later version and reproduced the issue in SQL Server 2014.
The issue due to in the earlier versions of Reporting Services (2005), there was limited support for translating expressions in RDL to Microsoft Excel formulas. But in the newly version, when you export a report to Excel, RDL expressions will not translated
to Excel formulas, So in the version 2014 the expression will not work.
Below links of articles are for your reference about more details:
http://msdn.microsoft.com/en-us/library/ms143380%28v=sql.100%29.aspx
https://connect.microsoft.com/SQLServer/feedback/details/684666/excel-formulas-not-supported-in-reporting-services-export
http://msdn.microsoft.com/en-us/library/dd255234.aspx
Regards
Vicky Liu

Export to Excel Problem - Page server Error

Post Author: Preethig
CA Forum: Exporting
Crystal Reports were designed using the Seagate Crystal Reports Developer Version 8.5.3.975.The reports does designed are published in the Seagate Crystal Enterprise 8.0.2.6725 across the web.
When we try to the export these reports to excel from the Crystal report viewer of the Crystal Enterprise it throws up an error" The export format 'U2FXLS:5' is not supported. [on Page Server : <webserver>.pageserver]."
The webserver as the Following ConfigurationWindows Terminal Edition - Windows 2000Service Pack 4.Seagate Crystal Enterprise 8.0.2.6725
The Client system on which the "Export to Excel" is performed has the following Configuration.Windows XP Professional Operating SystemService Pack - SP2.Excel 2002 (10.2614.2625).
We have tried uninstalling the Crystal Enterprise 8.0.We have also checked for the u2fxls.dll and Crxf_xls.dll in the C:/ <% system Root%> /Crystal.
Kindly help us to figure out the problem. It has been working fine for quite long and flawed only recently.
Thank You in advance.
Thanks and regards,
Preethi

Post Author: Preethig
CA Forum: Exporting
Cyril,
Thank You For your tip. But the problem of export To excel could be solved after I renamed the Crxf_xls.dll in the <%System root%> /Crystal folder which allowed the dll U2fxls.dll to Excel export work just as fine as explained in the Knowledge Base of Bussiness Object.
Thank you
With Regards,
Preethi

500 Internal server error on Export to Excel

Hello All,
I have implemented Export to Excel using this tutorial:
http://wiki.sdn.sap.com/wiki/display/Snippets/WebDynproJava-ExportingTableDataUsingOn-DemandStreams-SAPNW+7.0
However, after deploying the application, it simply throws 500 internal server error. I have followed each step carefully but I guess something is missing or I am doing it wrongly. How should I go about resovling this issue? I have been trying to fix this since yesterday and yet no success.
As it is failing right after the deployment that means doInit() method of my view is not able to execute the method mentioned below:
wdThis.wdGetExportExcelCompInterface().initialize(wdContext.nodeVn_OutputTable(), getColumnInfos());
I have defined getColumnInfos() method in the view but not sure why it is failing? Any thoughts on this? Has anyone implemented this? If not, please direct me to some simple export to excel code snippet or document. I have been struggling to implement simple Export to Excel on table. (I am not using RFC. The data is coming from KM APIs)
Ameya

Dear Ameya,
For Comunication between DC's, you should use the other DC's as Used Webdypro Component. If you are using with different scenario with webdynpro reference, then please have a look at below document might help to resolve your issue.
http://help.sap.com/saphelp_nw70/helpdata/en/42/9ddf20bb211d72e10000000a1553f6/content.htm
Adding a WebDynpro DC as used Component to a portal app
Using Development Components in WebDynpro components - runtime failures
Best Regards
Arun Jaiswal

Discoverer Plus4i - Exporting to Excel - Your server is running low

Similar Messages

Maybe you are looking for