Internal Error when Exporting to PDF

Hello all,
I have created a report in SSRS 2008. My report was running fine until I inserted an extra row. Once I would insert this row,(no matter where I insert it) whenever I try to view the print layout or export to a PDF I get the following error:
"An internal error occured on the report server. See the error log for more details. (rsInternalError)"
Checking the error log I found this:
library!ReportServer_0-90!12f4!01/09/2015-07:46:21:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: ScalableList: Index -1 outside the allowed range [0::5], Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more details.;
I have researched a great deal to try to figure out what could be causing this problem. I found several threads that had a similar problem and their solution was to set all "Hide Duplicates" properties to "None." I have checked several
times and my report has all it's "Hide Duplicates" properties set to "none."
Does anyone have any idea what could be causing this error?
Thanks,
Sarah

I found out what was causing the error in my report.
When the original report was created, a parent group was created. When a parent group is created, SSRS automatically adds an extra column with whatever it’s child group was grouped by inside of it. When this column was created, instead of deleting the text
inside the column or deleting the column, the column was made so small that you almost couldn’t tell it was there. I did not realize it was there until today. Since SSRS is pretty picky, it did not like that column.
You could do 3 things to get rid of the error:
Delete the column
Delete the text inside of the column
Expand the column so that the text inside it is visible
I tested all 3 approaches by adding 25 extra rows after applying the solution and all would export to a PDF just fine.
So basically if anyone out there happens to have the same issues I had, check and make sure you don't have any extra columns hiding anywhere. Hopefully this can help someone someday!
-Sarah

Similar Messages

Fireworks CS4 internal error when export to PDF

Trying to export a PDF from a layout gets an internal error
message with Fireworks CS4. The layout involves a master page plus
5 pages with a few PSD images imported. To test to see if it was
something to do with the specific file, I tried another simple
single page png which initially exported but then started to fail
as well. Regular export to CSS, etc. seems to be fine. My OS is
Vista Business.
I've tried googling for a solution but have only found topics
around certain fonts causing start up failures.
Any ideas?
Thanks.

quote:
Originally posted by:
tjodoin
After some debugging, I discovered that if all text is
removed, the project exports to PDF without issue so this looks
like a font issue similar to the other threads covering program
launch problems. I haven't installed any fonts outside of what come
with the system or Web Premium CS4.
Is there a list available that identifies fonts required by
Vista?
Here you are:
The
big font list in Windows

Error when exporting a pdf in SAP

She sends me the error when exporting a pdf from the SAP system, this is the message:
X Object reference not set to an instance of an object.
I hope I can support.
Annex image

See your other thread.

Error when exporting to pdf using Infoview.

Hi,
If I preview one of our reports (built in CRXI) in the CMC for CR server and then attempt to export the output to a PDF after waiting for a few mins I get the error:
Error
Your request could not be completed because a failure occurred while the report was being processed. Please contact your system administrator.
The report has 6 supreports each that take 2 parameters. Previously we have had problems with this report when trying to change the database connections for the subreports (we were getting a 'Missing prompting units' error until we started making the database connection change in CRXI, running from CRXI not the CMC and then saving the file to the repository once it had run successfully with the new connection settings).
All our other reports preview fine, they do not generally use sub-reports or multiple parameters though.
Thanks for your help.

There's so many variables for each Enterprise action, even with an effort to improve these over the years, the Enterprise error messages are usually so vague you have to trace to really identify the issue.
Exporting directly from Crystal Reports is a good start.
Sometimes it's just a matter of the report has streamed the 1st/beginning pages to you, but it is still processing in the background when the export to pdf is executed. Since the report is not complete, it fails. Try scheduling it directly to pdf to eliminate this possibility.
Else you will have to trace the Page Server or RAS to get more info.

Page Number Error when export to PDF

I am getting an error on page numbers for a book file when I export to PDF. The page numbers are set in the master pages and when I export each chapter individually the page number show fine. When I export the entire book, then some of the page numbers repeat. The pages are the right pages, but the numbers change incorrectly. For instance, the sequence goes, 58, 59, 58, 61 and 72, 73, 72, 73, 76.
I've updated to the latest InDesign (7.5.2) and have tried multiple PDF export options (High Print, Press, PDF/X, etc) and nothing fixes it.
Any suggestions?
thanks

This is a known (and fairly catastrophic) problem in CS5.5.
Some people have found exporting the individual INDD files to IDML, resaving them as INDD files (don't overwrite your originals!! Make a backup first!), and recreating the book works...for a while.
You could revert to CS5.0 if you have a license for it.
CS6 is on the horizon and should fix this bug.
Hopefully there'll be a CS5.5 maintenance update to do so as well.
Sorry I don't have a better suggestion.

Internal error when making a pdf of a book in FM8

Hello,
I'm currently learning to work with Framemaker 8.
When i wanted to pdf the book that i created, i get the following error message:
Internal error8004, 6343116, 8483344, 0. Framemaker has detected a serious problem and must quit.
A file named .........txt has been generated which contains information that may help frame development improve the product for future releases.
When i press the ok button of this error message, i get a second dialog box saying: The instruction at "0x00c91940" referenced memory at "0x00000000". The memory could not be "read".
After pressing the OK button of this dialog box, Framemaker shuts down completely.
I searched the internet for a solution but could not realy find one. I have tried to make a pdf via the safe as pdf and via print to pdf, but with both i have encountered the same problem.
Anyone has an idea how to solve this error?
The strange thing is that my colleague is able to make a pdf out of this book without encountering any problems and that we are using the same settings.
Thank you very much.
Bjorn

Bjorn, usually one post is sufficient... three is overkill.
The next time you post, please confirm that you have a fully patched version of FM 8 -- the third patch was just released this week. It would be useful to know if you're using the bundled version of Acrobat Distiller or a complete version of Acrobat. How much RAM do you have installed, and what operating system are you running?
# That said, a couple things to try and a couple questions: Make sure that you have lots of free space on your hard drive for temp files created during the process.
# Can you print the book's individual component files to the PDF printer?
# Open all the component files in the book before trying to print to the PDF printer.
# Do you have any graphic files that were copied into the files? Not imported by reference?
# In your preferences, is Generate Tagged PDF On or Off? Toggling it sometimes makes a difference.
Cheers,
Art

Error when exporting to pdf - cannot read a jpeg image, but I do not know which jpeg image.

I have created a document (A5) in Indesign cs6 with 116 pages. Because I would like to print the book I want to export it to pdf. Normally this is no problem for me, but now I got the following error: "Error encountered while reading JPEG image. Image may be damaged or incompatible. Resave the image with different settings and try again." This is quite annoying as my book contains 631 links of which most are .jpg. Does anyone know how I can find out which picture gives the error?
What is remarkable is the following. As it is a very large file InDesign automatically splitted it in subsections (with names like 'A5 V' or 'A5 V3'). To get closer to the problem I tried to export each subsection (all between 3 and 30 pages) to pdf. But somehow I managed to do this, so one might think that there is nothing wrong with the document at all. But when I try to expor the document as a whole again I still get this error about the JPEG image. It takes a couple of minutes (somewhere between 30 and 40% of the exporting) before I get the error.
Is there anything I should have tried which I forgot? I hope anyone can help me with this problem.

If you are able to export as sections it's almost certainly not actually a problem with the image, but a problem of not enough system resources to finish the job. This is not uncommon with large complex PDF exports.
Try rebooting, then immediately open ID and try the export again first thing. If it works, great. If not, you can combine your sections into a single PDF in Acrobat Pro.

Crystal report error when exporting to pdf

We have developed a crystal report that gives an error (doesnt say which one) when i try to export the report to pdf.
It says "exporting the report failed".
Version : 11.0.0.1282.
The viewer im talking about is the integrated preview of crystal reports.
Edited by: RolandWorms79 on Sep 2, 2009 10:42 PM

Seems to be working now.
I upgraded CR and adobe.
Edited by: RolandWorms79 on Sep 7, 2009 10:52 AM

Error when exporting to .pdf "blue boxes"

Does anyone know what happened here? I have been doing this for years and all of a sudden the pictures are just blue boxes when I export to a .pdf file. And it takes forever to go through the process. Some of the photos are OK, but the majority just show up as these empty squares. Please help.

I'm using Pagemaker 7.0.2 and Mac OS 10.2.8. and Pagemaker runs on 9.2.2.
I made a mistake last night and hit a goofy combination of command/control/alt (who knows what it was? I was trying to get rid of those ghost arrows and things that pop up) and my monitor went to "negative" = like a photo negative. I finally figured out how to fix that in the System Preferences/Universal Access.
I reinstalled Pagemaker, and some of the pictures show up, and some are just blue boxes. I embedded all of the pictures. Still doesn't work. And it takes a long time to export to the .pdf.
Now I found another glitch, and the Pagemaker won't let me create a booklet. Gives me Error 7241- can't find that error number anywhere.
Do you think there's a solution? Or do I have to dump my beloved Pagemaker and go to InDesign. That means I would have to reformat 30 newsletters!

New InDesign Error when Exporting to PDF

since upgrading to CS 5.5 my entire company has encountered numerous issues and errors with InDesign. This however, is a new one and I was wondering if anyone knew the root cause of such an error and a potential fix.
here's the error message my marketer is getting when trying to export a document to a pdf:
%%[ ProductName: Distiller ]%%
%%[ Error: ioerror; OffendingCommand: readstring ]%%
Stack:
(› PoÈsKÖn[1]µÐY5Âê2¢ ÷Fmø-êíöYJ
øR½=Ö¤%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
The steps she takes if file - export - adobe print PDF and then selects smallest file size. The file is packaged
Any comments/thoughts/help is greatly appreciated.

If anybody is still tracking this thread -
I've got a weird variation on the same problem. I've got a 400+ page document, which was printing fine until yesterday. Now I'm getting the error.
%%[ ProductName: Distiller ]%%
%%[ Error: ioerror; OffendingCommand: readstring ]%%
Stack:
(› PoÈsKÖn µÐY5Âê2¢ ÷Fmø-êíöYJ
øR½=Ö¤%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
I ran into this once before, found this thread, figured out that there was a problem with the master pages, as no subset of pages would print. So I deleted and created new master pages again this time. Now, if I just have one master page, it's fine, but as soon as I add the facing master page, the odd-numbered pages won't print. If I run just the even pages, it's fine. If I run the whole thing with a single master, it's fine. But I need different masters for the odd and even pages. ANY CLUE where the error might be, or how to work around it? I'm starting with blank pages for the masters, and the problem happens before I add any elements to the odd-numbered master.
Windows 7, CS 5.1, but since it has worked fine in the past, I don't think it's a system problem. I inadvertently hit a key yesterday that asked me about doing something with my pasteboard (I hit cancel, don't remember what it was), but if I do a Select All, I don't see anything lurking outside the print area to cause problems.

I have a problem. When exporting from PDF to PPTX error "unable to process the document in the module Save As file is not created." What to do?

I have a problem. When exporting from PDF to PPTX error "unable to process the document in the module Save As file is not created." What to do?
Windows 7 64
PC

everything works on a laptop (

InDesign 6: When exporting to PDF - error message fix a pixels/picas

InDesign 6: When exporting to PDF - get error message to go into Preferences and fix a pixels/picas issue - I've been working in the same project for two days and exporting pages all along without this trouble - just started all of a sudden. Haven't changed any settings... How can I fix this?

Error in character spacing when exporting to pdf from word 07

I am having trouble with exporting to pdf from MS Word 07. The character spacing throughout the document is wacky. This also happens when exporting to pdf from a GIS program.
Any help?

I use the term export because that is how it is done in the GIS software that I use - ArcMap 10.
In MS Word I access Adobe Acrobat Pro 9 through the print menu. I am using Windows 7.
I do not always have this trouble, but it started yesterday on a 30 page word doc and then after that, it started on an ArcMap doc.
As for embedding fonts, when I check the Word doc as you suggested, i see many different fonts listed. Some are embedded, some embedded subset, some are not embedded at all. I use styles to manage font types and heading levels. There is nothing fancy about it - all Times New Roman.

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

Internal Error when Exporting to PDF

Similar Messages

Maybe you are looking for