Error when exporting to excel (.xls)

Everytime I try and export my spreadsheet to excel, it says "an error has occurred" and nothing happens. I'm not using special text or something, it's in Times New Roman. How can I fix this error?

Hi sunandmoon,
Welcome to Number '08 discussions.
Could you provide more information, size of file, multiple tables, graphs, and the like. Are you doing File > Export, Excel?
The more information you provide the better we may be able to assist you. Also, did you use the Search feature in the upper right? Thousands of questions asked and answered.
These Discussions are enduser helping enduser, not Apple employees answering questions. Apple provides these discussion forums for endusers however, Apple neither monitors nor engages in discussions. Enduser such as yourself when they have extra time answer questions.
Again, welcome to Number '08 Discussions, have fun here.
Cordially,
RicD

Similar Messages

Runtime error when exporting to Excel

Hi
I'm new to this so pardon my mistakes.
When i try to export a report (viewed in cystal reports in SAP) to excel, a runtime error occurs and forces SAP business one to close.
In some reports, the export to excel icon on the menu bar is active, but in some it is grayed out.
Please Help with this issue
Win XP
SAP 8.82 PL 15
Crystal reports 2008 runtime engine sp3

Hi Nagarajan,
Sorry i do not have the screenshot but this is what the error says:
" Runtime error !
Program : C:\Program Files (x86)\SAP\SAP Business One\SAP Business One.exe
This application has requested to Runtime to terminate in an unusual way
Please, contact the application's suport team fore more information. "
The excel version is 2007.
Export using other formats (pdf,word, xls data only) work fine. Its only xls with full formatting that generates the error.
The report being exported is viewed in crystal reports within SAP.
Thanks,
Aziz

Error when exporting to Excel for SharePoint 2010 List

We have few users who are getting the following error message when they try to export to Excel from the SharePoint list:
"An operation that uses the database driver could not be completed. If the driver is a Microsoft driver, make sure the driver file isn’t damaged, and if it is, reinstall the driver by reinstalling Microsoft Query. For other drivers, contact
your database administrator or driver vendor.‘
The export option works for me on my machine and also tested it out on other users' machines without issues. The list is currently holds 29763 items.
1. Created a view that filter the list to show few items, and the user was able to export without issues.
2. Followed the steps in the following Blog:
http://www.sharepointserverrecovery.com/blog/troubleshooting-problems-when-exporting-sharepoint-list-data-to-excel-spreadsheet-and-fixing-database-corruption/ and the user was able to export the original list.
3. My colleagues and I don't have any issues exporting to Excel. (Note: even my test account, that does not have any special permissions or members of any SharePoint group(s)).
4. Some Blog/Forums suggest to increase Threshold limit in Central Admin, which we don't want to do, since the issue only affect certain users.
Any idea on how to troubleshoot/resolve the issue?
Thanks,
Yassar

Do they have to export all the information or is a subset of it ok?
Creating an index on the columns that your users interact with the most and then creating views that limit the returned results will be useful. This will then allow an export.

LSCompatibility plug-in error when exporting to EXCEL partial workaround

hey guys. i had a big project at work today that i needed to turn in and when i went to export my file to excel it just kept dying out on me. anyway, i looked at my spreadsheet and decided to remove all the drop down menus and just replace them with the answers. it worked right away! so, obviously we shouldn't need to do this. but for now, use it, it works.

I'm really surprised because here, I may export flawlessly documents with Pop-up Menu items to Excel.
Of course I get the alert explaining that this kind of item is not recognised by XL and that they will be replaced by the values of the cells.
May I know the number of Pop-up Menu cells in your document?
Maybe there is a limit to the number of "problematic" cells.
Yvan KOENIG (from FRANCE dimanche 14 septembre 2008 19:26:47)

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

Error: -43..when exporting to Excel

Hi All
A client gets Error: -43 [863-29], when exporting a list to excel.
I cant seem to find what the error means.
Any ideas?
Thanks
Jerusha

From SAP Note number 864829
When exporting to excel via Business one , this error occurs if user does not have the correct permissions on the folder he has chosen to save the data in.
Solution
Verify user permissions on the folder.
User must have the correct permissions ie read and write on the folder.
Give user the necessary permissions to be able to save to that folder.
These rights can be given by the local Administrator.
Regards,
Frederic

Reports output delayed when exported to Excel using OLE2

Hi All,
Platform - Oracle Application Server 10g Release 2 10.1.2.3 on Windows 32 bit.
The report output is getting generated in a minute when exported to PDF i.e destype=cache & desformat=pdf. When we generate the output to excel is considerably delayed. It is taking time and internal server error is occuring.
1) Report developed with simple query
2) Used RPT2XLS procedure which uses OLE2 builtin to export report output into excel.
3) Called RPT2XLS.run procedure in After-Report trigger of the report.
4) We have relased all memory objects in the RPT2XLS package after exporting data and there is no EXCEL.exe running once the file is generated.
System parameters used in the URL.
. destype=file
desformat=pdf
CONTAINSOLE=yes (Required for exporting OLE2 objects into Excel in report)
desname=path & name of the file.
I have gone through the tuning documents for reports server and increased minengine, maxengine and initengine parameters of the reports engine and also changed maxconnect and IdleTimeout parameters in reports server configuration file.
What might be the reason for delaying in the output of the reports when exported to Excel. Can the guys with special knowledge on this area help us in getting out of this issue.
Thanks in advance.

hey all,
Thanks everyone for the reply.
I am using the foloowing field cat:
l_col_pos = l_col_pos + 1.
    wa_fieldcat-col_pos = l_col_pos.
    wa_fieldcat-outputlen = 32.
     wa_fieldcat-fieldname = 'SOLLWERT'.
     wa_fieldcat-inttype   = 'P'.
*    wa_fieldcat-tabname = 'i_final'.
    wa_fieldcat-seltext_l = text-t11.         "Target Value
    APPEND wa_fieldcat TO i_fieldcat.
    CLEAR wa_fieldcat.
I have use this also in the field cat but stil i get space in the excel header.
wa_fieldcat-REF_FIELDNAME = 'SOLLWERT'.
*    wa_fieldcat-REF_TABNAME = 'QAMV'.
Also the space comes with the descrip[tion in the cell of excel.
its like [space Target Value] and i dont need this Space.
I have also used wa_layout-colwidth_optimize = 'X'. but it doesnt wrk.
Please suggest

Merge columns when exporting to excel data only

Hi,
I have a report with headers in fowling format.
Quantity |
first day | last day |
When exporting to excel data only I want output in following format and want to merge upper header cells.
Quantity
First Day
Last Day
Please reply.Thanks.

Hi,
You can achieve this requirement Please follow the below document.
How to WYSIWYG SAP Crystal Reports Export to XLS
I hope this is the best formatting example suited for this requirement.
Ludek thanks for preparing this document and sharing with us......This is the best formatting ex.
Refer Link: Crystal Reports Crystal to Excel
Thanks,
DJ

Header of ALV with space when exported to excel using Standard ALV

Hi,
I am Using Reuse alv grid display    to dispaly my report and it works fine and I am using the standard SAP application tool to export it to excel.
But for some of the header fields I am getting space in the excel sheet but there is no space while displaying through ALV.
I am using the following field catalog for the same.
wa_fieldcat-col_pos = 10.
wa_fieldcat-fieldname = 'SOLLWERT'.
wa_fieldcat-seltext_l = 'text-t10'.      "Target value (* this has no space here)
wa_fieldcat-outputlen = 32.
wa_fieldcat-colwidth_optimize = 'X'.
APPEND wa_fieldcat to it_fieldcat.
but there are still space for this Colomn when exported to excel if after optimizing the column.
kindly suggest what field needs to be passed to the field catalogoe to avoid spaces in excel for the header.
Thanks
Ritesh

hey all,
Thanks everyone for the reply.
I am using the foloowing field cat:
l_col_pos = l_col_pos + 1.
    wa_fieldcat-col_pos = l_col_pos.
    wa_fieldcat-outputlen = 32.
     wa_fieldcat-fieldname = 'SOLLWERT'.
     wa_fieldcat-inttype   = 'P'.
*    wa_fieldcat-tabname = 'i_final'.
    wa_fieldcat-seltext_l = text-t11.         "Target Value
    APPEND wa_fieldcat TO i_fieldcat.
    CLEAR wa_fieldcat.
I have use this also in the field cat but stil i get space in the excel header.
wa_fieldcat-REF_FIELDNAME = 'SOLLWERT'.
*    wa_fieldcat-REF_TABNAME = 'QAMV'.
Also the space comes with the descrip[tion in the cell of excel.
its like [space Target Value] and i dont need this Space.
I have also used wa_layout-colwidth_optimize = 'X'. but it doesnt wrk.
Please suggest

Formatting lost when exported to excel

When I export a worksheet results to excel the formatting is being lost like in my worksheet I wanted a line and space for every grouped item which is lost in excel sheet. Is there a way get around for this ?
Thanks

Not exactly sure what formatting you're having a problem with, but I'll list some of the points I can think of, of exporting to Excel and will hopefully cover it. I believe you may be referring to point 1 below, but just in case ...
1. If you have group sort on for a column or more, then when exported to Excel, you won't have those 'blank' values for the column(s) that's grouped. That's why when you know someone will be exporting to Excel, it's a pain as all group sorts are usually taken back off (which can screw up exactly what you're trying to point out in the workbook).
2. If you have a page -> item (ie: lots of values you pull down like a LOV), then I believe, that you won't get an Excel worksheet for each value in the LOV but only for the one currently displayed when you performed the File -> Export.
3. When you export to Excel, you only get actual values, no functions of how it was calculated (ie: it'll be static, not dynamic).
4. You can export to Excel using Plus and might not get the formatting characteristics you want in Excel. I've seen users specifically bring up Viewer just to get the formatting characteristics (colors, fonts, etc.) when they export from that Disco version.
5. Sometimes when you export from Disco to Excel, that actual value that gets posted in Excel is different. I know ... it sounds wierd, but it's a fact. The problem is NOT Disco, but is a problem with Windows and a setting has to be altered (although I'd have to hunt what that setting is now though). However, I've only seen this happen a few times, so definitely not the norm.
Russ

SSRS 2012 Conditional Formatting Color Issues When Exporting to Excel

Hi all,
We recently upgraded to SQL 2012 from SQL2008 R2. I'm having a strange issue with SSRS2012.
One of the report has conditional formattings on cell background colors. Everything works fine when render the report in browser or preview mode. However, the conditional formatting stop working when export the report to Excel (no issues if
export to pdf). All cells are high-lightened with pre-defined color although it should only high-lighten those cells that fulfil the condition.
Has someone encountered this issue before ? Thanks for any help.

Hi ZZ02,
I have test the scenario in my testing environment, however, everything goes well when exporting to Excel format. The issue might be related to the expression for the conditional background color. To make further analysis, please post the expression as well
as the report design structure.
Additionally, in SQL Server 2012 Reporting Services, the Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010, the format of which is ExcelOpenXML. By default, the previous version of the Excel rendering extension,
compatible with Microsoft Excel 2003, is disabled. At this time, I suggest that you enable the Excel 2003 rendering extension by modifying the RSReportServer.config file. After that, the Excel 2003 rendering format will be available on report manager (not
available in Report Designer). So, please export the report from report manager and check the result again.
For more information about enable the Excel 2003 rendering extension, please see:
http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/0713de27-dcc0-4e51-81ac-5272647d171f
Regards,
Mike Yin
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Mike Yin
TechNet Community Support

Crystal Report 2008 doesn't set page size when export to excel file

Hi,
I am using Crystal Report 2008 Developer edition.
At Crystal report design time setting the below page setup:
Page Options -
to A3(297X420 mm)
Orientation --- Landscape
and using the following code in .net (c#)
I am using below format options to export in excel in .net 2005
ReportDocument oReport = new ReportDocument();
oReport.FormatEngine.PrintOptions.PaperOrientation = PaperOrientation.Landscape;
oReport.FormatEngine.PrintOptions.PaperSize = CrystalDecisions.Shared.PaperSize.PaperA3;
if (aParamlist.ReportFormat == ReportFormatEnum.MicrosoftExcel)
ExcelFormatOptions excel = new ExcelFormatOptions();
excel.ExcelUseConstantColumnWidth = false;
// Use detail section one as a guideline to determine column width
excel.ExcelAreaGroupNumber = 1;
//excel.ExcelAreaType = AreaSectionKind.Detail;
excel.ExcelAreaType = AreaSectionKind.Detail;
// Prepare exporting options
ExportOptions export = oReport.ExportOptions;
export.FormatOptions = excel;
export.ExportFormatType = ExportFormatType.Excel;
oReport.Export();
when export to excel it doesn't set the Paper Size to A3(297X420 mm).
Is there any way to set the paper size while export to excel or in other formats also????
Thanks & Regds,

Hi,
thanks for your email.
This is not happening in development environment.It is setting the paper size anf paper orientation properly.
this is happening in the production environment where only redist installation is done.
thanks

'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

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);

Error when exporting file from LR5.2 - file created

After updating to LR5.2, I receive an error when exporting files to another disk drive. a file is created, but a warning appears "Unable to Export: "An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute". I also have CC iunstalled for other applications, but originally installed LR5 as a standalone Adobe application. I tried removing the program and reinstalling through CC, with no change in this behavior.

The answer is in the thread:
http://forums.adobe.com/thread/1303578?tstart=0

Error when exporting to excel (.xls)

Similar Messages

Maybe you are looking for