Font error when exporting PDF

Just exported my file from InDesign to check the PDF before sending it to the printer. Getting message "Cannot extract the embedded font 'CDGLWI+Optima-Bold'. Some characters may not diplay or print correctly."
I saw thread about emailed files garbling, but this is on my own computer.
File uses all optima fonts and none are showing correctly in the PDF. Find Font in InDesign doesn't show a problem and nor does Font Book when I validate the font files. Using In Design CS4 and OS 10.6.5.
Ideas?

Apparently a font can have a problem or perhaps something in the conversion to PDF has a problem with that font that Font Book doesn't see. After replacing font it now exports to PDF just fine.

Similar Messages

'Font contains bad/Widths' and 'Cannot find/create font' errors when saving pdf as Other Reduced Size PDF

I am exporting .indd files from within Indesign as pdf files, opening in Acrobat Pro XI. I have no trouble creating the initial pdf file, however, when I go to Save Other > Reduced Size PDF I get error messages. Depending on the file, I receive either the message, "The font (Myriad Pro) contains bad/Widths" replacing the text with dots or "Cannot find or create the font (Helvetica) Some characters may not print or display properly" replacing text with dots or boxes.
My confusion is that the file is exporting to pdf from Indesign without error, it is only when I try to Save Other> Reduce Size PDF that the error occurs.
Also, it is only occurring on five out of 120 pages. These same fonts are on other pages and I have no trouble at all with exporting or Reduce Size PDF.
More frustrating is that I have never had this problem occur in all my previous versions of Acrobat using the same process and typefaces.
I am reaching deadline on this and cannot find a solution other than to reload Acrobat 9 and ditch this upgrade.
Any help would be greatly appreciated.

I, too have experienced this issue. Upon export from INDD CS6, I see the error message "The font 'IXWIPX+SourceHanSansSC-Bold' contains bad \Widths."
The only items on the single-page InDesign document I'm trying to export are copies of a one-page PDF (which was extracted from a longer PDF, arranged into a cover format). I can provide all files as necessary. The longer document that the one page came from also experienced an error when I tried to print to Adobe PDF. While I still get a PDF of the cover on export, despite the "bad \widths" message, it won't print from certain machines. I get nothing (not even an empty shell file) from the attempt to print the larger document (where the cover elements came from) to PDF.
I can deal with these issues with a few unorthodox workarounds, but wanted to offer comments or volunteer to help test fixes if possible.
For the record, I'm really not enjoying Acrobat XI. It doesn't seem to have much by way of new features (at least not that I use), and some of those I used most in version X are gone or less functional. Common fonts like Times New Roman are often not found (even though they are definitely on my system); I have a much harder time editing text through the new interface, and I have a few other small gripes—some that I don't have time to get into, others that wouldn't really matter, except that they weren't a problem until I "upgraded." Just sayin'.
Thanks for listening.

Errors when Exporting PDF to various formats

I have a 231 Page PDF that consists of text, scanned images/pages of text, metadata, comments and hidden text. The document is a company manual/handbook. I am working on a project to pull all this into InDesign in order to make the document easily and quickly editable. The problem is that the original PDF was created with Word with all the elements I've listed and the main problem being the scanned pages of text (from previous versions of the manual) just inserted in word before being exported. So, I can't just copy and paste everything into InDesign because a lot of the text is actually scanned pages.
Originally, I got around this by running the OCR Engine and then Command-A > Command-C, etc. The problem there is that the formatting is completely messed up. Line breaks all over, etc. I removed all formatting (including line breaks) by copying and pasting all of the text into Safari's Google search box and then copying/pasting that back into Word (which will eventually simply serve as the file InDesign pulls the text from). Now I'm going through adding in text formatting (paragraph breaks, etc.) by flipping pages of the original manual while hitting "Enter" in Word.
Now, I see a feature in Acrobat 9 Pro that allows me to export to Word, RTF, etc. However, I keep getting some errors. I've managed to get rid of all but one - Bad Fonts. Adobe pops up this "Bad Font" error and tells me the file has not been saved. Additionally, I've managed to get through 116 pages of the document saving process when exporting to "Text - Accessible" and then Acrobat 9 Pro just quits.
Any thoughts on how to get around this error or fix it? Any other time saving tips?
Thanks

Hello,
It seems that the problem is related to particular PDF file.
1. Try running OCR on it via Tools -> Text Recognition -> In This File, and then convert the file.
2. Print the file to Adobe PDF printer and then try to Export it into Excel.
Regards,
Anoop

InDesign CC 2014.1 Error When Export PDF

I am using the following script to generate a pdf, but to execute the command sends me the message "Error Export to PDF".
Please help me identify what I'm doing wrong.
 InterfacePtr<ICommand> pdfExportCmd(CmdUtils::CreateCommand(kPDFExportCmdBoss));
if(pdfExportCmd==nil)
CAlert::InformationAlert("CheckInOutDialogController::crearPDF pdfExportCmd is invalid");
break;
 CAlert::InformationAlert("A2");
 InterfacePtr<IPDFExportPrefs> exportPrefs((IPDFExportPrefs*)::QuerySessionPreferences(IID_IPDFEXPORTPREFS));
// set export prefs
InterfacePtr<IPDFExportPrefs> pdfExportPrefsToExp(pdfExportCmd, UseDefaultIID());
 if(pdfExportPrefsToExp==nil)
 CAlert::InformationAlert("CheckInOutDialogController::crearPDF pdfExportPrefs is invalid");
 break;
pdfExportPrefsToExp->CopyPrefs(exportPrefs);
 CAlert::InformationAlert("A3");
 IDocument* theDoc = Utils<ILayoutUIUtils>()->GetFrontDocument();
 UIDList pageUIDs = UIDList(::GetDataBase(theDoc));
 InterfacePtr<IPageRange> myPageRange((IPageRange*)::QuerySessionPreferences(IID_IPAGERANGE));
 IPageRange::RangeFormat pageRangeFormat = myPageRange->GetPageRangeFormat();
 CAlert::InformationAlert("A4");
 // Assume theDoc is a valid IDocument* for export.UIDList pageUIDs = UIDList(::GetDataBase(theDoc));
 InterfacePtr<IPageList> iPageList((IPMUnknown*)theDoc, IID_IPAGELIST);
 if (pageRangeFormat != IPageRange::kAllPages){
 PMString pageRange;
 pageRange = myPageRange->GetPageRange();
 pageRange.SetTranslatable(kFalse);
 iPageList->PageRangeStringToUIDList(pageRange, &pageUIDs);}else{
 int32 cPages = iPageList->GetPageCount();
 for (int32 iPage = 0; iPage < cPages; iPage++ )
 CAlert::InformationAlert("Pagina");
 UID uidPage = iPageList->GetNthPageUID(iPage);
 pageUIDs.Append( uidPage );
 CAlert::InformationAlert("A15");
 // Assume pdfExportCmd is the valid ICommand* from kPDFExportCmdBoss.
 InterfacePtr<IOutputPages> iExportPages(pdfExportCmd, IID_IOUTPUTPAGES);
 // Assume exportPrefs is the previously set IPDFExportPrefs from kPDFExportCmdBoss.
 iExportPages->InitializeFrom(pageUIDs, (exportPrefs->GetPDFExReaderSpreads() == IPDFExportPrefs::kExportReaderSpreadsON));
 PMString name;
 theDoc->GetName(name);
 iExportPages->SetName(name);
retval = CmdUtils::ProcessCommand(pdfExportCmd);

I am using the following script to generate a pdf, but to execute the command sends me the message "Error Export to PDF".
Please help me identify what I'm doing wrong.
 InterfacePtr<ICommand> pdfExportCmd(CmdUtils::CreateCommand(kPDFExportCmdBoss));
if(pdfExportCmd==nil)
CAlert::InformationAlert("CheckInOutDialogController::crearPDF pdfExportCmd is invalid");
break;
 CAlert::InformationAlert("A2");
 InterfacePtr<IPDFExportPrefs> exportPrefs((IPDFExportPrefs*)::QuerySessionPreferences(IID_IPDFEXPORTPREFS));
// set export prefs
InterfacePtr<IPDFExportPrefs> pdfExportPrefsToExp(pdfExportCmd, UseDefaultIID());
 if(pdfExportPrefsToExp==nil)
 CAlert::InformationAlert("CheckInOutDialogController::crearPDF pdfExportPrefs is invalid");
 break;
pdfExportPrefsToExp->CopyPrefs(exportPrefs);
 CAlert::InformationAlert("A3");
 IDocument* theDoc = Utils<ILayoutUIUtils>()->GetFrontDocument();
 UIDList pageUIDs = UIDList(::GetDataBase(theDoc));
 InterfacePtr<IPageRange> myPageRange((IPageRange*)::QuerySessionPreferences(IID_IPAGERANGE));
 IPageRange::RangeFormat pageRangeFormat = myPageRange->GetPageRangeFormat();
 CAlert::InformationAlert("A4");
 // Assume theDoc is a valid IDocument* for export.UIDList pageUIDs = UIDList(::GetDataBase(theDoc));
 InterfacePtr<IPageList> iPageList((IPMUnknown*)theDoc, IID_IPAGELIST);
 if (pageRangeFormat != IPageRange::kAllPages){
 PMString pageRange;
 pageRange = myPageRange->GetPageRange();
 pageRange.SetTranslatable(kFalse);
 iPageList->PageRangeStringToUIDList(pageRange, &pageUIDs);}else{
 int32 cPages = iPageList->GetPageCount();
 for (int32 iPage = 0; iPage < cPages; iPage++ )
 CAlert::InformationAlert("Pagina");
 UID uidPage = iPageList->GetNthPageUID(iPage);
 pageUIDs.Append( uidPage );
 CAlert::InformationAlert("A15");
 // Assume pdfExportCmd is the valid ICommand* from kPDFExportCmdBoss.
 InterfacePtr<IOutputPages> iExportPages(pdfExportCmd, IID_IOUTPUTPAGES);
 // Assume exportPrefs is the previously set IPDFExportPrefs from kPDFExportCmdBoss.
 iExportPages->InitializeFrom(pageUIDs, (exportPrefs->GetPDFExReaderSpreads() == IPDFExportPrefs::kExportReaderSpreadsON));
 PMString name;
 theDoc->GetName(name);
 iExportPages->SetName(name);
retval = CmdUtils::ProcessCommand(pdfExportCmd);

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 message: Helvetica Medium outline font missing when creating PDF's

Error message: Helvetica Medium outline font missing when creating PDF's. Where can I downlaod it and why is it suddenly happening?

OS? Version of ID?
This means that either you have an extra Helvetica Medium font installed and it's interfering with ID finding the T1 version, or the T1 version is damaged. I found this really old thread that explains it fairly well: http://www.asadesigner.com/22-indesign/2d812de56777cc90.htm
The good news is that it's probably only affecting the page information marks.

SRVE0199E: OutputStream already obtained when exporting pdf

Hi,
I am have a problem when export pdf file from a web application. When I build with tomcat every works fine, but when deployed in Websphere. The problem occurred. It is that the exception stack being attached at the end of pdf file which prevents Adobe Acrobat 7 from open and displaying message like the file is damaged and could not be repaired. This is the exception stack,
<H1>Error page exception</H1>
<H4>The server cannot use the error page specified for your application to handle the Original Exception printed below. Please see the Error Page Exception below for a description of the problem with the specified error page.</H4>
 <H3>Original Exception: </H3>
Error Message: SRVE0199E: OutputStream already obtained 
Error Code: 500 
Target Servlet: action 
Error Stack: 
java.lang.IllegalStateException: SRVE0199E: OutputStream already obtained
 
 at com.ibm.ws.webcontainer.srt.SRTServletResponse.getWriter(SRTServletResponse.java(Compiled Code))
 
 at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java(Inlined Compiled Code))
 
 at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java(Compiled Code))
 
 at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java(Compiled Code))
 
 at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java(Inlined Compiled Code))
 
 at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java(Compiled Code))
 
 at com.ibm._jsp._exportResults._jspService(_exportResults.java:104)
 ... there is more...
and my code that generate pdf is,
try {
out = res.getOutputStream();
PdfWriter.getInstance(document, out);
document.open();
Paragraph para = null;
para = new Paragraph("Title", FontFactory.getFont("Arial", 20,Font.BOLD));
document.add(para);
} catch (DocumentException e1) {
e1.printStackTrace();
} catch (IOException e1) {
e1.printStackTrace();
document.close();
please help me out because this is an urgent issue. Thanks.

I didn't put this code within JSP, but inside javax.servlet.jsp.tagext.TagSupport. Is this the same as in JSP?
While waiting for the answer, I also find that in TagSupport, there is a member variable, pageContext, that also has pageContext.getOut() which is a JspWriter. This is used to export to excel. But for exporting to pdf, i used PdfWriter.getInstance(document, res.getOutputStream()); and res = pageContext.getResponse();
is this the main reason?

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

Font issue in exported PDF from indesign

Font issue in exported PDF from indesign:
In Indesign file we have kept a sentence in “Univers LT Std” (San serif font) with all caps style that was orginally in lower case. Refer below
When we selected the sentence in exported PDF some of the characters are not selected. Refer below.
If we enable “create tagged PDF“ in export PDF setting, then the problem is solved. Refer below.
Can you please check why this problem happened? In another project also we have faced this same problem but different font “Frutiger LT Std” with all caps style. Here also same San serif font. Please check and advise to solve this issue permanently.

Without tags a PDF is a silly amount of letters, images and lines, with tags all itams a kept in their semantic context. So work with tags as it is the only way to get correct selections and export to other file types like Word DOCX.
Without tags InDesign reads from left to right from top to bottom and the font geometry might influence the correct order of letters.
Why should anyone work without tags today? If you open a tagged PDF in Acrobat DC it is much faster than without tags.

'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 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 flat file in ODI 11g

This works ok in ODI 10g. I'm using IKM SQL to File Append on Windows Server 2008 R2
Getting the following error when exporting to a flat file in ODI 11g: ODI-40406: Bytes are too big for array
I've seen a couple of threads like this on the forum, but I've never seen an answer to the problem.

Problem is with the difference in behaviour for the IKM SQL to File Append KM between 10g and 11g.
Our 10g target file datastore had a mixture of fixed string and numeric columns. Mapping from the source to target was simple one to one column mapping. It generated the desired fixed format flat file; numerics were right adjusted with embedded decimal point and leading spaces. Each numeric column in the generated flat file occupied the exact space allocated to it in the layout. This gave the desired results, even though documentation for the 10g IKM states that all columns in the target must be string.
When we converted to 11g and tried to run this interface, it generated an error on the "numeric" columns because it was wrapping them in quotation marks. The result column was being treated as string, and it was larger than the defined target once it acquired those quotation marks.
In order to get 11g to work, I had to change all the numeric columns in the target data store to fixedstring 30. I then had to change the mapping for these numeric columns to convert them to right adjusted character strings (i.e. RIGHT(SPACE(30) + RTRIM(MyNumericColumn),30).
Now it works.

How to create a hyperlink when exporting .pdf?

Hi guys,
I've been doing quite a bit of research on how to make an object into a hyperlink when exporting my .ai as .pdf.
So far I've come across guides that show the method of using Object > Slice and the Attributes' Image Map, but none of them seem to work when I open my exported .pdf.
How do you guys create objects with links when exporting .pdf?
Thanks in advance.

InDesign, most probably.
Or create the PDF in Illustrator and use Acrobat (Pro) afterwards to make links.
Depends on what's inside the document.

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins?

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins. I have try reinstalling aperture three times, deleting plists a few times, reinstalling plugins, restarting my MacBook Pro many times. Everything I've tried may fix the problem for a very short while and I can export a few photos before it returns. The problem happens with topaz and photomatrix pro plugins after I edited and try to export version.

I had the same problem with the Photomatix plug-in and this solved it for me. I realised it only happened with Photomatix and not other plug-ins so I checked where the plug-ins were installed. The Photomatix plug-in was installed in
~/Library/Application Support/Aperture/Plug-Ins/
where ~ is the home location for the current user account. All the other plug-ins however were installed in
Macintosh HD/Library/Application Support/Aperture/Plug-Ins/
which is the location that makes them available to all user accounts on your Mac. Moving the Photomatix plug-in to this location solved the problem for me.
Note that the Library directory under the first location is normally hidden, to get to it hold down the Option (Alt) key and select it from the Finder Go menu.

The problem with the correct diagnosis sensitive when exporting PDF to RTF

Welcome.
I came across the following error when converting PDF files to RTF program "Adobe Acrobat XI Pro" - it happens that some files (unfortunately, they form the majority of those who support it) some letters for some reason are not properly converted - for example, instead of getting a word in capital letters word in which the first letter is small and the other large. This is just one of many examples - "POLICE" -> "pOLICE", etc.
Can someone already encountered a similar problem?Is interesting to add that when I open this PDF in the "Adobe Reader" and choose "save as" -> "text" - the letters are incorrect.
I apologize in advance for any spelling mistakes - the text is translated automatically :-)
PDF:
RTF:

Unfortunately, this was afraid ... I understand that there is no way to get around this? I do not have any influence on how the PDF files are created - just get there already, and I bring them into a fully editable (RTF).

Font error when exporting PDF

Similar Messages

Maybe you are looking for