Creating PDF issues.

Hello everybody,  I currently am testing the trial version to see if it will fit my needs, however whenever I try to convert a word document to pdf I get the status bar that says reading pdf or some such and it continually loads and reloads without ever creating anything, i've let it sit for up to an hour with no results.  Any help would be appreciated.

It is also useful to know just exactly how you are trying to create a PDF. For simplicity, open your DOC file in WORD and print to the Adobe PDF printer. If that works, then go back and try using the PDF toolbar in WORD. Trying to create the PDF directly in Acrobat is the worst place to try a trail run. It is the most complicated of all the techniques and most prone to failure.

Similar Messages

  • I can't create PDFs from CS3 programs in Acrobat Pro XI. Compatibility issue or just Acrobat?

    I was just upgraded to Acrobat Pro XI this morning. InDesign, Photoshop, and Illustrator don't seem to be supported file types for creating a PDF from Acrobat.  While I usually create my PDFs from the authoring program, I occasionally need to make a lot of PDFs of different files at once, and making them from Acrobat makes sense instead of opening each individual file.
    Is this just a compatibility issue? We have requested upgrades to CS6, but it will be a while before it gets approved (if it gets approved).  Did someone think it was a brilliant idea not to allow PDFs from the CS products to be created from Acrobat instead of the authoring program?

    Can you describe your workflow a little more? Are you saying that you created PDFs of InDesign documents using Acrobat directly -- not using InDesign?
    If that was possible in CS3, I must have missed it.
    FWIW, I can't select CS6 InDesign, Illustrator or Photoshop documents in Acrobat X. You can only select a handful of image formats, HTML or PostScript/EPS.

  • Creating PDF's from *.doc or *.docx file with fake security issue's ......

    Hi,
    We're trying the new 11 Pro and just patched it to:11.0.09 to try to fix this error below.
    When the user tries to create a PDF from the main menu that now says "Create PDF from File" instead of the old screen that said "Create PDF" ......
    If I start the process with a *.docx file I get the " can't open the file because of rights "  error and it was doing the same thing in the old original installed
    version of 11 and also now this the new one I just updated now to try to fix it. 
    I also deleted the normal.doc templates in both his old MS Word 2003 program and also in the current copy he uses MS Word 2007.
    If I start the 11 Pro and pick the same document as the first one except for the fact that it has been re-saved in a *.doc MS Word 2003 format,
    the whole thing works perfectly.
    Any suggestions?
    Cheers'
    Dave

    Have you tried to open WORD and either print to the Adobe PDF printer or use the Acrobat icon (PDF Maker)? Try both. Do they work or not. PDF Maker has to work for the functionality of the create in Acrobat to work.

  • Random error when using cfpdfform to create pdf

    I have a series of pdf forms that have been created with extended rights in reader using both Acrobat Pro 9 and Acrobat Pro X. I use cfpdfform to pre-populate the form and name it with a unique guid.  Some people randomly are getting the error in reader "This document enabled extended features in Adobe Reader.  The document has been changed since it was created and use of extended features is no lonfer available.  Please contact the author for the original version of this document."
    I have tried to replicate the error using the exact same settings of windows, browser and reader version and cannot replicate.  I have researched extensively online and see many people experiencing the same error message but no clear resolution found.  Below is the code that I am using to save the prepopulated form.  Has anyone else run into this issue?
    <cfset uuid = createuuid()>
            <cfpdfform   source="forms\#url.frpdf#"
                        destination="forms\exh\#variables.uuid##url.frpdf#" overwrite="YES" overwritedata="YES"
                        action="populate">
                <cfpdfformparam name="name" value="#rtrim(variables.company)#">
                <cfpdfformparam name="address1" value="#rtrim(variables.address1)#">
                <cfpdfformparam name="address2" value="#rtrim(variables.address2)#">
                <cfpdfformparam name="address3" value="#rtrim(variables.address3)#">
                <cfpdfformparam name="citystatezip" value="#rtrim(variables.citystatezip)#">
                <cfpdfformparam name="city" value="#variables.city#">
                <cfpdfformparam name="state" value="#variables.state#">
                <cfpdfformparam name="zip" value="#variables.zip#">
                <cfpdfformparam name="country" value="#variables.country#">
            </cfpdfform>
    <cfcontent file="#expandpath(".")#\forms\exh\#variables.uuid##url.frpdf#" type="application/pdf">

    Depending on your application you may or not be able to carry the links over (reason for graffiti's question). To carry them over you need to use PDF Maker (the create PDF icon in WORD and several other products).

  • Print to PDF Issue

    From Word 2010, when printing to the Adobe PDF printer (Acrobat 10.1.6), some users are experiencing an issue where the log file is created but the PDF document is not.  THe log file contains two lines:
    THe operation COmpleted successfully
    Pipe:\\.\pipe\PMtoDistiller_ID_165:Microsoft Word - Test
    I can print to file, create a PS file, and successfully create the PDF using Distiller.
    Acrotray.exe seems to be running on the machine.
    Has anyone seen this before? What would cause it?
    Thanks.

    I appologize I wrote Adobe reader, but it's adobe standard 6.0.  And like a I
    said I can create PDF's normally in all other situations and programs except for this one

  • Create PDF crashes webapplication

    Hi,
    We have a website that creates PDF-reports using SAP Crystal Reports runtime engine for .NET Framework 4 (64-bit) SP1. The site runs on Windows 2003 R2 x64.
    The site (w3wp.exe) crashes every now and then when a report is generated in PDF. We cannot trace it back to specific reports, users or actions. It seems to be random. We don't have this issue on x86-webservers with the same application and CR-version.
    We got a memory dump from one of the crashes. The dump can be found [here|http://www.megaupload.com/?d=ZFVJ7FEZ] (zipped, about 330MB). Microsoft already analyzed this dump and this is the conclusion :
    Here is my analysis: as you already noted, the stack goes from the SAP component to msvcr80, based on the method name (without the private symbols we cannot see the arguments passed etcu2026) it looks like they are initializing something which requires memory to be moved around, hence the call to memmove_s
    0:076> kpL
    Child-SP          RetAddr           Call Site
    00000000`27ceec88 00000000`781b6a70 msvcr80!memcpy(unsigned char * dst = 0x00000000`26bbceb8 "???", unsigned char * src = 0x00000000`26bbceb8 "???", unsigned long count = 0)+0x1ec
    00000000`27ceec90 00000000`41d69db4 msvcr80!memmove_s(void * dst = 0x00000000`00000000, unsigned int64 sizeInBytes = 2, void * src = 0x00000000`000001c2, unsigned int64 count = 0)+0x80
    00000000`27ceecd0 00000000`41d6b2bc crxf_pdf!UXFInitializeW+0x1834
    00000000`27ceed50 00000000`37b2d78f crxf_pdf!UXFGetExportFormatsExW+0x10c
    00000000`27ceeda0 00000000`37da9c1a crpe32!CRPEConnectionInit+0x365df
    00000000`27ceeef0 00000000`37da0b93 crpe32!MWCleanupProcess+0x4ffca
    00000000`27ceefd0 00000000`37da54eb crpe32!MWCleanupProcess+0x46f43
    00000000`27cef720 00000000`37d27bb4 crpe32!MWCleanupProcess+0x4b89b
    00000000`27cef750 00000000`37d38964 crpe32!CRPEConnectionInit+0x230a04
    00000000`27cef820 00000000`37d39a8f crpe32!CRPEConnectionInit+0x2417b4
    00000000`27cefb90 00000000`37d39dac crpe32!CRPEConnectionInit+0x2428df
    00000000`27cefbe0 00000000`37d3a45c crpe32!CRPEConnectionInit+0x242bfc
    00000000`27cefd30 00000000`783917cd crpe32!CRPEConnectionInit+0x2432ac
    00000000`27cefe20 00000000`781337d7 mfc80u!_AfxThreadEntry(void * pParam = 0x00000000`23e01f80)+0x101
    00000000`27ceff20 00000000`78133894 msvcr80!_callthreadstartex(void)+0x17
    00000000`27ceff50 00000000`77d6b71a msvcr80!_threadstartex(void * ptd = 0x00000000`77d6b6e0)+0x84
    00000000`27ceff80 00000000`00000000 kernel32!BaseThreadStart(<function> * lpStartAddress = 0x00000000`00000000, void * lpParameter = 0x00000000`00000000)+0x3a
    First, itu2019s interesting to note that the destination pointer does not look to be valid; the call to msvcr80!memmove_s comes directly from crxf_pdf!UXFInitializeW (there are no u201Chiddenu201D calls in the middle):
    0:076> ln 00000000`41d69db4
    (00000000`41d68580)   crxf_pdf!UXFInitializeW+0x1834   |  (00000000`41d6b1b0)   crxf_pdf!UXFGetExportFormatsExW
    The exception (an Access Violation) is actually thrown in msvcr80 while it is trying to copy the memory as a result of the move call:
    0:076> .exr -1
    ExceptionAddress: 000000007814e38c (msvcr80!memcpy+0x00000000000001ec)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 000000002c78b280
    Attempt to write to address 000000002c78b280
    Also looking at the thread registers confirms that the memory address is not valid:
    0:076> r
    rax=0000000000000009 rbx=0000000000000413 rcx=000000002c78b280
    rdx=ffffffffff9329f0 rsi=0000000000000000 rdi=0000000000000002
    rip=000000007814e38c rsp=0000000027ceec88 rbp=0000000041dd42b0
    r8=0000000005500dc0  r9=0000000005500dc4 r10=000000002728a4c0
    r11=000000002728a4c0 r12=0000000041dd42b0 r13=0000000000000001
    r14=000000002728a4c0 r15=000000002c78b284
    iopl=0         nv up ei pl nz na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010204
    msvcr80!memcpy+0x1ec:
    00000000`7814e38c 8901            mov     dword ptr [rcx],eax ds:00000000`2c78b280=????????
    Unfortunately without the private symbols we cannot see what that memory belongs to.
    Anyway since I have access to all Microsoft private symbols, the fact that I cannot find this specific one I think means this is part of the SAP components. I think we can conclude the problem originates from the crxf_pdf.dll and manifests itself in msvcr80.dll because of some wrong parameter passed into that call.
    All help would be very much appreciated.
    Many Thanks,
    Thomas

    Hi Thomas,
    Since you have RAS available use this code and test again:
    private void ExportToPDFRAS_Click(object sender, EventArgs e)
        //CrystalDecisions.CrystalReports.Engine.ReportDocument rpt = new CrystalDecisions.CrystalReports.Engine.ReportDocument();
        ISCDReportClientDocument rcd;
        //rpt.Load("c:
    Reports
    Group.rpt");
        rcd = rptClientDoc;
        // Declare a PrintOutputController to allow documents to be exported to PDF
        PrintOutputController rasPrintOutputController;
        CrReportExportFormatEnum rasReportExportFormat;
        CrystalDecisions.Shared.DiskFileDestinationOptions diskOpts = CrystalDecisions.Shared.ExportOptions.CreateDiskFileDestinationOptions();
        diskOpts.DiskFileName = "c:
    reports
    reports1.pdf";
        // Set the CrReportExportFormatEnum to export the report as a PDF file.
        rasReportExportFormat = CrReportExportFormatEnum.crReportExportFormatPDF;
        rasPrintOutputController = rcd.PrintOutputController;
        // Use the Export() method of the PrintOutputController to export the report to a ByteArray.
        ByteArray tempByteArray = rasPrintOutputController.Export(rasReportExportFormat, 0);
        Byte[] byteStreamOutput = tempByteArray.ByteArray;
        System.IO.Stream oStream;
        byte[] byteArray = null;
        oStream = rpt.ExportToStream(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat);
        byteArray = new byte[oStream.Length];
        oStream.Read(byteArray, 0, Convert.ToInt32(oStream.Length - 1));
        // this is used to verify the file so I saved it to disk
        System.IO.File.Create(diskOpts.DiskFileName, Convert.ToInt32(oStream.Length - 1)).Close();
        System.IO.File.OpenWrite(diskOpts.DiskFileName).Write(byteArray, 0, Convert.ToInt32(oStream.Length - 1));
        System.IO.File.SetAttributes(diskOpts.DiskFileName, System.IO.FileAttributes.Directory);
        oStream.Close();
    CR requires contiguous memory space so for large reports IIS may not be able to handle cleaning up it's memory fragmentation when objects are freed up. It's a common problem with Java app's also, Java doesn't have a good memory manager either.
    Because of the lack of ability to pass files through Forums I suggest you purchase a support case if you don't have a Support Contract and work with a Support engineer here to debug the problem. We can get the PDB's for those files to you if that helps MS determine what their issue is...
    Thanks
    Don

  • Acrobat Pro 8.1.2 won't create PDFs by itself or within an Office 2007 application. Please help.

    Well, needless to say, everything was working fine when our department was running Acrobat 7 and Office 2003. We made the choice a few weeks ago to upgrade to Office 2007 and Acrobat 8. Both are pushed via Group Policy. One other thing to note, as I think it might be an issue, is that our users have their My Documents redirected to a server. I only mention this, because the Default PDF Output Folder within Acrobat 8 is My Documents.
    Here are the strange things that we've noticed so far:
    1) When you open up the Adobe PDF Properties within Printers and Faxes, the Location displays an "x" followed by two non-standard box characters that I can't seem to write out here. I've uploaded a screen shot if that makes it easier. On a manually installed copy of Acrobat 8, this location box will say My Documents.
    http://i57.photobucket.com/albums/g223/daedalus42/adobe_weird_characters.png
    2) The Adobe PDF printer port grabs LPT1, even if there is another printer already on that port. This behavior is seen when being pushed via GPO. When it's manually installed via the disc, Adobe PDF gets it's own special port "My Documents\*.pdf" with a description of "Adobe PDF Port". When I try to see if I can add such a port on the GPO pushed computers, it doesn't list it as an option. Here again are two screen shots to show what I'm talking about.
    Weird Port:
    http://i57.photobucket.com/albums/g223/daedalus42/adobe_weird_port.png
    Adobe Port:
    http://i57.photobucket.com/albums/g223/daedalus42/adobe_correct_port.png
    Ok, so those are just the oddities seen after performing a GPO installation.
    3) When I right click on a Word 2007 (*.docx) file and choose "Convert to Adobe PDF", it asks me where I want to save the newly created PDF at. It will start converting it, but a few seconds later a balloon error pops up saying that the document failed to print.
    4) When I try to create a PDF via the Word 2007 ribbon add-on for Acrobat, I get the same error.
    I decided to bump a standard user up to administrator of the local machine. All these errors go away and they can create PDFs to their heart's content. As soon as I bump them back down to a standard user, new errors arise.
    5) Now when they try to create a PDF, they get prompted TWICE for the PDF Save As location. When I click on Convert to PDF via the context menu of the Word 2007 file, I get the Adobe PDF Status box, then a few seconds later, I get the Save Adobe PDF File As box. I tell it where to save the PDF to. I then get a second box asking me where to save the PDF to, but it's titled different. This new box is "Save PDF File As". Whatever location I choose there, I get an Access Denied error and an Adobe Printer error that the document has failed to print. I've created screen shots of those as well. Here they are in order:
    http://i57.photobucket.com/albums/g223/daedalus42/adobe_access_denied_01.png
    http://i57.photobucket.com/albums/g223/daedalus42/adobe_access_denied_02.png
    http://i57.photobucket.com/albums/g223/daedalus42/adobe_access_denied_03.png
    http://i57.photobucket.com/albums/g223/daedalus42/adobe_access_denied_04.png
    Does anyone have any solutions whatsoever to fix this? I'm not about to go around to 100 computers and install Acrobat manually when it should work correctly via GPO. If Acrobat doesn't like the fact that a user My Documents is redirected to the server, I noticed that I can change the default PDF file location within the Adobe Customization Wizard. I've not tested that yet to see if it would even help.
    I should mention that I have tried running a repair. Didn't help. Uninstalling and reinstalling via GPO. Didn't help. So, we've installed the Microsoft Office PDF Creator plug-in and that works perfectly. For the time being Acrobat Pro has basically dropped itself down to a reader for all intents and purposes.

    @ Bill@VT: I did try adding a port. That's the problem. When it's on a problematic installation, those special Adobe Port aren't available for me to choose from.
    OK, I have some new information regarding my issue. I've done some more testing and this is what I have learned and how I arrived at that conclusion.
    b It appears to be an issue with the 8.1.2 update.
    1) I manually installed Acrobat 8.0.0 via the executable file I downloaded from Adobe Licensing. I had to go through all the installation prompts, enter the serial key, accept the EULA, etc. I even applied the 8.1.0 update. At this point, everything was fine. Any user on this computer could create PDFs via any method. The Adobe PDF Port was correct and no listed under LPT1 like in the above screen shots. And My Documents was listed as the Default PDF Location, even though users have their My Docs redirected to the server. Like I said, everything worked perfectly.
    2) I decided to install via the Administrative Install Point (AIP) on the server for Acrobat 8.1.2 and the corresponding transform file. After doing this, the problems came back. My first assumption is that the transform file is causing the problem.
    3) To verify that it was in fact the transform file I perform an install from the AIP using the AcroPro.msi file only. No switches and no transform file. Guess what? Problems are still there. So, that wipes out the transform file problem.
    A couple of notes:
    It could be related to the AIP and doing administrative installation upgrades to 8.1.2. My next test is to install 8.0.0 from scratch and manually upgrade that installation to 8.1.0, then 8.1.1, then 8.1.2 to find out when and if it breaks.
    I was able to get a contact number for Adobe's "Volume Licensing" department, so I might end up giving them a call. In fact, even if I narrow down what appears to be the problem, I'm still going to have to give them a call to find out what can be done about it. Because at the moment, the issue is there for 100+ users and something needs to be fixed. All I'm doing at this point is working backwards to figure out what may have caused the problem in the first place.

  • FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

    An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
    GOOD NEWS
    I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
    DON'T USE "SAVE AS PDF"
    But what's wrong with "save as PDF" as currently implemented?
    The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
    (1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
    (2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
    (3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
    (4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
    (5) Some or all text in the resultant PDF file cannot be searched or indexed.
    (6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
    (7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
    (8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
    (9) Some or all page content is missing (other than margin areas).
    (10) Relatively inefficient PDF is generated.
    If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
    It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
    In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
    Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
    Whether the printer supports color (Acrobat Distiller does)
    What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
    Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
    Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
    Resident fonts (Acrobat Distiller doesn't really have resident fonts)
    Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
    Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
    Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
    Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
    Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
    DON'T USE PDFWRITER
    The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
    SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
    The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
    Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
    PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
    PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
    Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
    Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    Case 3: Acrobat 3
    Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
    - Dov

    You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

  • Having difficulty creating pdf from XML data source

    I have a 'rpt' file built with a classic install of Crystal 10, using xml as a data source. I have tried using both ADO.NET(XML) connection and ODBC CR ODBCXML Driver 4.20.
    The rpt file was built on Windows2000 NT platform. The report runs, and displays data from the sample xml file in the preview tab.
    I am attempting to feed xml data into the rpt file with the intent to create pdf formatted output. I am using java with the Crystaldecisions packages. I am running this app out of an Apache server on an Ubuntu VM Hardy Heron release. This does not have any version of Crystal Reports installed on it.
    I have followed the examples and I am comfortable that I have the correct package imports, I am able to open the rpt file, and convert both the xml and xsd to byte arrays. When I issue the command
    reportClientDocument.getDatabaseController().setDataSource(xmlDataSet, '', '')
    I get the response
    Cannot find corresponding table information in the XML file
    Set data source failed: The table 'criminal_case' could not be found.
    Request failed and JRC Command failed to be undone
    JRCAgent1 detected an exception: The table 'criminal_case' could not be found.
    at com.crystaldecisions.reports.reportdefinition.datainterface.g.a(Unknown Source)
    The xsd does validate the xml which contains a noNamespaceSchemaLocation pointer to the xsd.
    The xml is the same data that was used to design the report on the NT box. This means that I see the same elements being byte streamed as were used to create the rpt file.
    Is this as simple as I am running my webserver on Linux? I do see the connection attribute properties reference a Database DLL that is clearly windows based. What can I do?

    So why develop a report if there is no data? I can only think that you have a bunch of static text, maybe an instruction page you want to publish? If so, you still need a data source, it can be a dummy source
    <?xml version="1.0"?>
    <ROOT/>
    ie no data per se. BIP needs a source even if there is not data to merge.
    Cheers
    Tim

  • Problems in Windows 8 creating PDF documents using Adobe Acrobat Pro 9.5.5

    I am running Windows 8 with the latest version of MS Office (version 14) and Adobe Acrobat Pro 9.5.5.  I was not having any problems making/printing PDF documents until about 30 days ago.  The only things that I can think of that have changed during this time period is 1) I updated my Office Suite to version 14 from the previous version and, most recently, 2) my Adobe Acrobat Reader program was automatically updated to the latest version.  I ended-up uninstalled Adobe Reader becuase the new program became my default for openning all Adobe PDF files, even when I tried to force my computer to use Adobe Acrobat Pro as the default (becuase doing so allows me to edit docments with features not available in the free Reader version).  When I go to print a Word document, for example, to Adobe Acrobat, the process stalls/stops at the point where you are supposed to choose a location to print/safe the new PDF document file.  All I get is the Save-As Screen with most of the buttons and folder tree blank (see example below).  After 5-10 seconds, "not responding" shows up in the title of the Save-As Screen and I have to click the "X" box in the upper right corner to abort.  This problem seems to have first started when trying to print pictures from the Windows picture viewer.  After a while long, I noticed that the same problem occured when printing from my internet browser (Firefox), but I coudl still print from Word or Excel.  Now, as of the last couple of days, I can't print from any program except the basic Paint software program.  I think this may actually be a Windows issue because when trying to toublshoot this problem, I re-installed Adobe Acrobat Pro and it did not help. I also tried making PDF documents using the free PrimoPDF software and had the exact same problem.  I have no idea where to go from here.  All I know is that I desperately need to create PDF documents and cannot!  Please help!!

    You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

  • How to create PDF file from MX7600 scanner in Windows 8.1

    I just changed to a new desktop PC that is running Windows 8.1. I downloaded the drivers from the Canon website for Windows 8.1, and I can not find the function to create a PDF file of the scanned document, like I could in Windows 7. How can I created a PDF file in the new driver software? 
    Solved!
    Go to Solution.

    Hi alove5230,
    Ini addition to the drivers, you will need to download the MP Navigator software for the printer to create PDF files.  Please click here to go to the Drivers and Software page for the PIXMA MX7600.  Once on the initial download page for your printer, please do the following:
    1. Verify that the operating system detected in the "OPERATING SYSTEM" drop-down menu is correct, and if it is not, please click the drop-down menu to select your operating system.
    2. Next, please click on the red arrow next to the "SOFTWARE" section and click on the MP NAVIGATOR file. When you do, a red DOWNLOAD button will appear. Please click on the checkbox below the DOWNLOAD button, then click the red DOWNLOAD button to begin the download. The time for the download process may vary depending on the speed of your Internet connection and the size of the file being downloaded.
    Once the file is downloaded, please double-click on it to install the program on your computer.
    Hope this helps!
    This didn't answer your question or issue? Please call or email us at one of the methods on the Contact Us page for further assistance.
    Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

  • Save as PDF or Save Book As (pdf format) Causes Frame 8 to try to quit after creating PDF

    I have Framemaker 8p273 and Acrobat distiller 8.1.3.
    When trying to creating PDFs from books using either Save as PDF OR Save Books As (PDF) file, the PDF creates FINE but the program then attempts to quit by throwing up weird dialog boxes.
    Steps to reproduce bug:
    1.Open any book
    2.Use File-->Save as PDF or File-->Save Books As and then choose type PDF
    3.PDF created fine - no errors reported in Distiller window
    4. Framemaker then throws up a small dialog box that says "cannot quit." You cannot close this box, only click OKAY.
    The only other issue that arises might be a "cannot print some graphics - will print as gray boxes"
    5. Clicking okay brings up sequence of 5 total of the same boxes (the book file has 7 files in it including the TOC).
    6. After last of 5 "cannot quit" boxes, a new Framemaker one appears, that says "Unsaved Changes in file (book name) Save before closing?" Options are Yes, No and Cancel. Yes saves file and quite Frame. No quits Frame. Cancel leaves file open.
    I have reproduced this error multiple times with different books, using both the Save as PDF and Save Book As (PDF) commands.
    File--Print Book using Acrobat printer works fine (making sure to enable the acrobat setting so bookmarks are properly generated).
    Just frustrated that the first two options cause such an annoying error. Reported as a bug.

    Jaclyn,
    I've seen this happen when an API client attempts to close a document that doesn't exist, which defaults to closing the FrameMaker session, but the session cannot close because it's in the middle of some operation. It's normally the result of sloppy code. Do you have any third-party API plugin software running? For that matter, does anyone know if the "Save as PDF" uses an API client? If so, might be a bug in that software, although it seems that there must be something unique going on here to invoke this behavior in your case.
    Russ

  • Question re Create PDF from Word doc

    Hi
    I am trying to create a pdf from a Word document (Word 2007, Acrobat 8 Professional), and am having lots of trouble with images,fonts and document overhead. With the fonts, i generate the PDF by saying Create Pdf from the plugin in Word. I specify in the Preferences that fonts are not to be embedded. I then open the PDF and access PDF Optimiser -> Audit Space Usage, and it says that fonts take up like 20% of the document, however there are only like 10 lines of text in Arial (9pt), and 6 titles also in Arial (Bold). I dont understand why Font is taking up so much space considering that i have elected not to embed fonts (if i go to the Fonts section in the Optimiser, it shows both embedded and unembedded panes blank).
    With the images, i have 2 jpegs in the footer, that are compressed (JPEG -> Low). The other thing i am struggling with is the headers and footers, if i generate the PDF from the Word doc with Headers/Footers, then images take up over 15% of the document. Not sure if there is a way to add headers and footers within minimum impact of filesize? I have tried checking everything in the 3 categories of Dicard Objects, Discard User data and Clean Up. but the Document Overhead remains at 35%.
    What else can i do to get these filesizes reduced?I have been researching this for days and have not come across anything that has helped.I have tried to PDF print, i have changed the font to like Courier, ensured no thumbnails or bookmarks, ensured JPEGs are not embedded in the doc, tried Save As, Save As under a different filename - basically anthing you can find on the net i have found and tried, but still cant fix this!!!! please, if anyone knows acrobate 8 better than me / or knows what the problem is, please advise????
    Thanks very much.

    The colors and size in a graphic needs to be done in a graphics editor. What type of editor would depend on the use of vector graphics versus bitmap. Sometimes vector graphics are larger than bitmaps if you are using a lot of lines that would display better as just a splotch of color. Such are the variations between vector and bitmap graphics, but important if you are looking for size reduction. For a bitmap, I would do the sizing and color depth with IrfanView, but you should be able to do that with PhotoShop if you have it. Vector graphics can be adjusted in Illustrator. The size of vector graphics is not an issue since they are scalable, but the size of a bitmap is important since your are looking at individual pixels and that depends on size. The point is that if you can adjust the color depth and size for the desired pixel resolution, the bitmap is optimized for the conversion to PDF from WORD.
    As I mentioned, the smallest file size job options should minimize font storage in the PDF. Checking with the PDF Optimizer does not always give you all of the fonts. I am not sure why. It is better to check the font tab in the document properties to see what has been embedded. There is a preflight macro to embed fonts, you might check to see if there is one to delete fonts (I have not checked on that). Sometimes you can play with the reprint of a PDF, but that is not an option that is generally recommended, particularly if you have any tagging or such. Of course, tagging can really bloat a PDF, but is needed for a variety of reasons such as format for saving back to WORD (not a great workflow), accessability, and related issues. In another topic, there is some discussion of the purposes of tagging and bookmarks. However, the tags and bookmarks take space if that is really an issue for you. The latter are avoided if you use the print to the Adobe PDF printer and do not use PDF Maker in the PDF creation process. Again, there is a trade-off here in terms of size and functionality, particularly accessibility compliance.
    Not sure I am helping as I run on, but sort what might be useful for you.

  • MSWord items that crash Adobe Acrobat 9.0 add-in (Create PDF function)

    I just want to include a tip I discovered after two days of troubleshooting a colleague's MS-Word (2007 - docx) document. I tried going through the forums to see if anyone else has posted this.
    Obviously, my colleague would try to use the Acrobat add-in within Word through the "Create PDF" button. But doing so causes MS-Word to crash. The crash involves the dialog box for sending an error report to MS (which I cancel).
    I then attempted this on another PC and got the same result.
    Another colleague on the support team suggested trying to convert only sections of the document to try and pinpoint the issue to an element within the document. The result of trial and error pointed me to a particular graphics element on Page 11 of the 46 page document. The graphics element was composed of 4 clock diagrams that were made up of smaller elements (arrowheads and lines for the clock-hands, separate textboxes for the numbers 1 - 12 on each circular clockface, etc.) Deleting the whole graphic allowed the document to be converted to PDF.
    I then reverted to the original document and clicked on the graphic. I was about to investigate if there was a particular element within the grouped graphic that caused the crash, but, by luck, I was able to discover that just by ungrouping the graphic into its elemental components "Create PDF" was able to render the PDF successfully.
    Perhaps this is something to try in the future should anyone run into this issue. I hope this helps someone else.

    It may be something that Adobe did not catch in the way that MS did the graphic processing (and to be sure MS does not always do things by the book). It may have been fixed. I note that you only have AA9.0. The current version is AA9.3.4, so an update might be in order. Potentially that would resolve the problem.
    In any case, I have found the graphic processing done by WORD 2007 to be strange. Taking the same file to WORD 2003 (saving to a DOC format if required) has no problem with the conversion. So there are likely problems from both MS and Adobe.

  • Can't create PDF from most MS Office files, or combine

    After behaving nicely for months, Acrobat suddenly won't create PDFs, either from the Acrobat menu or (for most) from right-clicking in Explorer. If I try File> Create PDF> From File, the dialog says it's looking for 'all supported formats' but doesn't show any of the files in the folder (not even .TXTs). It'll create a PDF from the right-click menu in Explorer, for only a very a few file types (for example, .docx but not .doc), and it won't do a Combine Files, either from Explorer or from the program, for any filetypes (says 'cannot convert file' on all filetypes).
    This worked fine up til today and I have the same setup at work (AA 9 Pro and Office 2010) where it works fine. Tried doing a 'Repair' but no change. Starting to panic here. What went south? Thanks for any clues!

    I said to print as a check, not to forget PDF Maker. The print is a temporary work around while you resolve the issue, partiuclarly if you are under time pressure. With versions before AA9, PDF Maker was simply a front end for the printer and when the printer was checked things might fail. So you get some trouble shooting of where the problem is. If you do not want to troubleshoot to see if everything is broken, that is fine.
    The updates and repairs are other steps to take. A reinstall is typically a last resort and should include deletion of the Acrobat folder and running a cleaner on the registry after the uninstall.
    Generally, if the PDF Maker in WORD does not work, then none of the other options to right click and create a PDF or creating a PDF directly in WORD will not work either. The whole point is to trace down to what is the major problem. Often folks have problems because the PDF Maker is not being recognized in WORD and has to be activated, but you have the icon and that suggests things should work.
    Your next step is to check the job settings file. Be sure you have access to the job settings file. You will usually get an error message if this access is denied for some reason and posting the error is helpful.

Maybe you are looking for