Crystal Reports: Print Engine Error when exporting a report

We recently upgraded from Crystal Reports 2008 to BusinessObjects Edge Series X3.1. When exporting a report to an excel data-only format we get "Crystal Reports: Print Engine Error". All other formats work fine. Any help is highly appreciated.
Thanks,
Jaseem

Anyone?

Similar Messages

GR224 Report Painter: Internal error when converting a report

Hi
Using FAGL_RMIGR transaction I've trasferred report 8A3-0010 in a
custom library ZXX. The migration happened without error messages. I've
tryed then to run report FL3-0010 by GRR3 transaction but error message
GR224 appears
Report Painter: Internal error when converting a report
Message no. GR224
Diagnosis
During the internal compilation of a Report Painter report to a
Report Writer report, sets are generated. This caused an error in the
subprogramm GENERATE_ROW_MULTI. The return code was 7.
System Response
The report could not be generated and/or saved.
Procedure
Please call the SAP Hotline and send them this longtext as well as
detailed information describing the circumstances in which this
error
occured.
Please could you help me?
Thanks in advance
Giovanna Scamardella

HI,
SAPNET notes search with GR 224 brings some old (but maybe helpful) notes: 37611, 193392,137231, pls. check.
Best regards, Christian

File I/O error when exporting a report

Post Author: Beth
CA Forum: Exporting
Hi,I have a program that runs as a scheduled task daily that runs four reports and exports them to rtf format. This process has been running fine for a long time (several years). However I've noticed now that I occasionally get an exception with the message "File I/O error", and the stacktrace doesn't give a much more useful information (see below): 5/4/2007 7:47:29 PM exception caught - Message:File I/O error. 5/4/2007 8:36:25 PM at . F(Int16 , Int32 ) at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext) at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export() at CrystalDecisions.CrystalReports.Engine.ReportDocument.Export() at EmailReport.Form1.ExportReport(TableLogOnInfo crTableLogOnInfo, String exportFilePath, String reportLocation) at EmailReport.Form1.crystalReportViewer1_Load(Object sender, EventArgs e)As mentioned, this exception message and stack trace don't give me any information as to what the problem might be, and a search on the web hasn't yielded anything to help either. Is there anyway to find more information as to the root cause of the exception? Does anyone know what the File I/O Error means?As I said, this is not a new report, but something that has been in Production a long time. My best guess is some upper limit on the report has been reached, and at this particular time the number of records being processed for this report is too big. But I don't know how to prove this - the report was written by someone who has long left the company, so I don't know too much about the details of the report (as I don't know much about Crystal Reports to begin with).System Info:The machine exporting the report is a W2K machine.The executable was build using VS2003 with .NET 1.1 framework and CR8.5 and C#.The program itself contains a Form with a CrystalReportViewer object. Then creates a ReportDocument object, sets the appropriate parameters, then calls Export().Does anyone have any insight into what this exception means?Thanks,Beth

Chapter markers are not relevant to this. How long's the movie? What drive are you exporting to? How much space is on the drive? Did you render everything (Opt-R) before exporting? Did you mixdown the audio (Cmd-Opt-R) before exporting?

Crystal Report XI R2 error when opening a report

This issue may not be unique to my situation and I'm hoping there are others here who have experienced this problem and have found a solution/workaround for it.
I have a Cyrstal Report file that was created using CR version 10.0 that has been in use by our web application without any issues for a while now. However, I found out that after I upgraded the Crystal runtime on my web server to version 11.5, this particular report refused to work with a simple error message that said : "File cannot be found.".
I tried opening this same report on Crystal Report XI R2, and it does not open and throws an error message saying: "This document could not be opened".
Strangely enough, this same file opens up fine on Crystal version 10. I'm inclined to believe that the report file I'm trying to work with has some header information that Cyrstal XI does not like, because it opens and generates fine on version 10.
The option of re-creating a new report from scratch on XI R2 is the last option since its a very complex report. Any help on this is greatly appreciated.
Thanks

Madusha,
Those errors usually indicate that the report or something in the report has become corrupted. You could try
a) Exporting the report to RPT format in CR 10 and see if it will open
b) Try deleting 1 section at a time in CR10 until it opens in XI or R2, keep a copy of the original report and if you are able to narrow down the cause to a specific section or object then remove it from the original in CR10 and readd it in XI or R2

JAVA error when exporting to reporting schema ODDM 4.1

When attempting to export a design to a reporting schema, we received the following error:
ERROR ReportsHandler - error exporting to reporting schema:
java.lang.classcastException: oracle.dbtools.crest.model.design.relational.column cannot be cast to oracle.dbtools.crest.model..design..relational.columnView
at oracle.dbtools.crest.exports.reports.RSViewColumn.export (RSViewColumns.java:43
at oracle.dbtools.crest.exports.reports.RSRelationalModel.export (RSRelationalModel.java:62)
at oracle.dbtools.crest.exports.reports.ReportsHandler.export (ReportsHandler.java:135)
at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run (ControllerApplication.java:2079)
We downloaded and installed ODDM 4.1 (EA-1) build 4.1.0.866 to resolve an issue with column widths when exporting to the reporting schema (per SR 3-10154440761). This is the 64 bit version with the included JAVA 1.8 JRE.

David,
We migrated this model from data modeler 3.3. That Model was created from an import from Oracle Designer. We have not yet tried to import the data model from Oracle Designer directly into v4.1 but are planning to do so shortly. When we tried to export that design (from v3.3) to the reporting schema, it failed with object too large for column errors. We wrote SR 3-10154440761 and were advised by Michael Wickham to use v4.1 EA as the column size issue had been resolved in this version. It was apparent that the export to the reporting schema was making more progress before it failed on the JAVA error.
We are trying to migrate from Oracle designer to Oracle Data Modeler

CRAXDRT Error when exporting a report to Excel

I have a large report in Crystal Reports, using the browser, inside a COTS package called Medgate. It's 521 pages. I can export to PDF just fine, but when I export to Excel, I get "CRAXDRT Error Occured on Server: -2147206450: Disk full." The popup window is titled "Report Viewer Export."
The disk is not in fact full. How can I resolve this error?

Did you write that software, COTS package called Medgate?
If not then ask that company for support. No one here would know how to fix it. They are using the CR RDC report engine.
Thank you
Don

Failed to read data from report file : Reason: Crystal Reports: Print Engin

Hi,
When we try to migrate the crystal reports from BO R2 to BO R3, some of the reports are faling with the error:
Failed to create a new Report.Reason: Failed to read data from report file C:\DOCUME~1\xxxxx.rpt. Reason: Crystal Reports: Print Engine Error
Would please someone help me in fixing the issue.
Thanks and Regards,

Few quick checks to identify the cause -
1. Are you able to run report in your R2 system?
2. In XI3.1, check SIA running on which account.
3. Check the acount have sufficient rights on file system and registry.
4. What's your web server?
Give proper rights and import again. Hopefully it will resolve.
Edited by: Das on Dec 6, 2010 9:47 PM

Error when exporting reports using MAPI

We created a .NET class that wraps CR 2010 .NET Crystal Reports functions and made it COM visible. This class is used to create a COM object in a js script which in turn used to export reports to a PDF file with the destination MAPI.
It exports reports just fine without any errors however if prior to instantiation the exporting class we instantiate a class that has nothing to do with the Crystal Reports functions, our exporting object throws u201CExternal component has thrown an exception.u201D error when exporting. It appears that it has something to do with the SideBySide feature. I was wondering if somebody knows what causes this and if there is a way to fix this problem.
Thanks for your help!
 
 
Below are 2 procmon.exe outputs, the first when exporting works and the second when it doesnu2019t
 
 
 
1) Procmon.exe output when exporting works fine
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 7:16:30.7403615 AM test.exe 4396 FASTIO_QUERY_INFORMATION C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Image Base: 0x79260000, Image Size: 0x1073000
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryNameInformationFile, Name: \Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest NAME NOT FOUND Length: 20
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 
 
 //////////////////////////////////////////////////////////////////////
 2) Procmon.exe output when exporting doesnu2019t work, notice that it tries to open MSO.dll at the same location as in the output above but fails, it tries then to open it at several other locations and fails
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll FAST IO DISALLOWED
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll FAST IO DISALLOWED
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\SysWOW64\MSO.dll FAST IO DISALLOWED
 C:\Windows\SysWOW64\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\system\MSO.dll FAST IO DISALLOWED
 C:\Windows\system\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\MSO.dll FAST IO DISALLOWED
 C:\Windows\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

I tried to run exporting code in a .net application and got the same error. I first created the COM object that causes the problem and then ran exporting CR functions. It works fine if I run the code without creating the COM object.
Below is the code I used.
 Type objClassType = Type.GetTypeFromProgID("ebms.main");
 object objMain = Activator.CreateInstance(objClassType);
 try
 object[] p = new object[4];
 p[0] = "C:\\ebms\\co1";
 p[1] = "C:\\ebms\\co1";
 p[2] = "Administrator";
 p[3] = "";
 objClassType.InvokeMember("LoginToCompany", System.Reflection.BindingFlags.InvokeMethod, null, objMain, p);
 catch (Exception ex)
 this.RPTDoc = new ReportDocument();
 this.RPTDoc.Load(@"C:\\Users\\Paul\\Desktop\\AR Customer List.rpt");
 PdfRtfWordFormatOptions pdfOpts = ExportOptions.CreatePdfRtfWordFormatOptions();
 MicrosoftMailDestinationOptions mailOpts = ExportOptions.CreateMicrosoftMailDestinationOptions();
 ExportOptions exportOpts = new ExportOptions();
 pdfOpts.UsePageRange = false;
 exportOpts.ExportFormatOptions = pdfOpts;
 mailOpts.MailMessage = "something";
 mailOpts.MailSubject = "something";
 mailOpts.MailToList = "emailaddress";
 exportOpts.ExportDestinationOptions = mailOpts;
 exportOpts.ExportDestinationType = ExportDestinationType.MicrosoftMail;
 exportOpts.ExportFormatType = ExportFormatType.PortableDocFormat;
 try
 this.RPTDoc.Export(exportOpts);
 catch (Exception ex)
 MessageBox.Show(ex.Message, "Error", MessageBoxButtons.OK, MessageBoxIcon.Error);

Crystal Reports XI R2 Javascript error when viewing web report

Post Author: msilka
CA Forum: General
I have an ASP web application that was working fine with XI but when I upgraded to XI R2 I received the following error when displaying a report in the report viewer.
Line: 461
Char: 1
Error: Object expected
Code: 0
URL: my report URL
When I debug with a javascript debugger the line in question reads as
addOnloadFunction(reportViewerNamebobjInit);
I need to get the reports to run without this error.
Thank you

The only personal folders visible from under Admin panel are for users Administrator and Guest. I've tried to query CMS tables but these store entries not in plain text so I cannot identify entries connected to personal folders. I have also tried to do this via Query Repository tool but all returned entries were ok.
I have also noticed that when trying to load group from LDAP after it returns error "LDAP: Failed to commit objects to server : Duplicate object name in the same folder." entry for this group is created in CMS table. Also this group is then visible in admin Groups panel. No users are created with the group and when I'm trying to list users belonging to added group it returns "internal secLDAP security plug-in error" but without any other suggestion what went wrong.

SSRS XML Errors when exporting to .xlsx from Dynamics NAV Database

We use Dynamics NAV for our ERP and have many SSRS reports. We get xml Errors when exporting to Excel .xlsx. I've seen this happen since SQL 2008 R2 and have posted in many places trying to find an answer, but was hoping MS would solve the
issue. The numeric data types in the Dynamics NAV database are all decimal(38,20) and when the value is zero the Excel renderer throws the errors.
We now have over 400 reports and we export them to Excel 2003 format. I'm starting to feel like this is my new Y2K issue when Excel 2003 is set to sunset. I'm fearing that I'll have to do conversions on all numeric data types for all reports.
Both of these are Microsoft products so I'm wondering is this even on their radar.
We're running SQL Server 2012 SP2, and just rolled out CRM 2015 on SQL Server 2014. I get the errors in SSRS 2008R2, 2012, and 2014. Has anyone seen this before?
Timothy Kruse

Hi Skywalker73,
According to your description, when you export the report to Excel, the error “Excel was able to open the file by repairing or removing the unreadable content.” throws out when opening the Excel file.
Based on my research, it has reported the same issue when exporting to Excel. The issue could cause by numeric columns has a precision of 16 or higher. To fix the issue, we could change data type in the table to a support lower precision, or convert
the numbers in the stored procedure that populates the report. For more information, please refer to this article:
SSRS 2012 Bug – “Excel found unreadable content”. Besides, please refer to this
article to check if non-printing characters exist in the report.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

'file could not be written due to an error' when exporting jpg

I'm working with an Illustrator file in CS2 and after a certain point it has started saying 'the file could not be written due to an error' when exporting to a jpg.
i've tried a couple things like deleting layers and although the file is much smaller, it still says the same error when exporting.
at its highest it was 130mb as an illustrator file and jpgs were 2-5mb.
i''ve tried copying some of the layers into a new file but the error report still comes when i'm exporting.
i have vector and raster based data in the file and tried turning off/deleting either of the layers and there is no difference.
i don't understand why it's started doing this because before it had no problem at all exporting before.
ANY IDEAS ANYONE? I'm trying not to have to reproduce days of work to remake the file.
many thanks,
P

Mylenium,
Sounds like you know a good deal about this product. Is there any way to restore a color profile/setting to an earlier point?
I don't recall changing it and to tell you the truth, wouldn't be able to say which it may have been set to before - if different.
Thanks,
Paul

Getting error while exporting the report

Hi,
I am facing error while exporting the report. Getting below error.
"No data can be exported because there are no rows.Operation failed."
how come this error is coming even though my report contains data.
please do the needful.
i am using the version discoverer 10g.
Thanks,
RC.

I am having the same problem. I found this article in which the user was exporting 100,000 plus records and had the same issue exporting (Discoverer workbook exported to excel error - No dta can be exported and they were able to fix it by adjusting two memory settings in their pref.txt file. However, in my report there are only 1,100 records with eleven columns being returned. I export much larger reports on a daily basis.
Originally, the report was returning records and when I would go to retrieve all records it would tell me that all the rows could not be returned and the data may be incomplete. After scrubbing my SQL I no longer get that message, but the report still will not export and I get the same error as you.
I have not tried the pref.txt settings fix but may try it today to see if that is a workaround. I will then have to evaluate whether it is a good fix or just a band-aid.

Problem when exporting the report to PDF viwer a 45,000-page report

I am using Visual Studio 2013 with the report vivew.
I have a report that works correctly, however when generating a 45000 pages he is giving memory error when exporting to PDF, any tips?

Check this SAP Note: 1089388 Incorrect value in exported PDF when Concat function is used
[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=1089388]

Poor image quality when exporting a report to Word

Hi,
We are developing an application where users can download exported Word 2003 or PDF documents generated by Crystal Reports. The problem is that when the format type in the export options is set to Word for Windows the quality of the images in the document degrades immensely. The PDF images are looking fine though.
Literally, the only difference between the two exports is that only one of these lines executes depending on what the user selects when exporting the report.
crxReport.ExportOptions.FormatType = CRAXDRT.CRExportFormatType.crEFTPortableDocFormat;
crxReport.ExportOptions.FormatType = CRAXDRT.CRExportFormatType.crEFTWordForWindows;
I am using Crystal Reports 10.0. Upgrading to Service Pack 6 did not seem to solve the problem. This service pack resolves a similar problem that occurs with PDFs but it's Word documents we're having trouble with. The project we are working on is a .NET 1.1 project and it is hosted in a machine running Windows 2003 Standard Edition with Service Pack 2.
Any help is greatly appreciated
L.

Hello Logan:
See if the directions in [this|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do] note help.
[This|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do] note is not quite what you'd look for, but it may be worth considering to see if it helps.
Other than that, as Ido recommended, despite the difficulties of the number of parameters, see if exporting from the CR designer is any different. If it is not, we're fighting a lost battle. Alternatively, you could create a new report in the CR designer, no database connection needed. Insert an image, export.
Ludek

Add page break when exporting a report as an editable RTF with JRC

Hello,
When exporting a report as an editable rtf in Crystal Reports Designer we can select the option : "Insert page break after each report page".
Does the same option exists in the JRC ? I don't want to use the MSWord export format.
Thanks in advance.

Yes. EditableRTFExportFormatOptions has the following method:
setInsertPageBreaks(boolean bInsertPageBreaks). Sets whether page breaks are inserted into the exported Rich Text Format (RTF) file that correspond to the page breaks in the report.
For more information please see the RAS Documentation in the SDK Library.

Crystal Reports: Print Engine Error when exporting a report

Similar Messages

Maybe you are looking for