Loading fillable PDF from IE endless loop

Hello,
     I am having an issue. I am trying to load a fillable PDF from Internet Explorer but every time I hit the load button my computer goes into and endless loop with downloading into a temp folder then back to IE and then again to downloading to the temp folder. This is not with just 1 file but multiple.

Sorry, I don't understand what you mean by "load button"; do you mean Save?

Similar Messages

  • How to load a PDF from page 1 in IE

    I am currenty working on a fllex based web application that needs to load multiple PDF documents. The pdfs are loaded and displayed properly but after the user scrolls couple of pages/ lines and switches to a new document, IE saves the last visit cursor position of the pdf document. On user revisit to the first PDF the IE loads it from the last cursor position.
    I need to reload the PDF document from Page 1 everytime the user selects to load a pdf document.
    Is there any setting in the Adobe Acrobat Page display settings or in the IE that would help me accomplish my task.
    Please respond ASAP.
    NOTE: The pdf is loaded inside  an IFRAME.
    Thanks,
    -Karun

    > I have a feeling that removing the save button will not be possible.
    You cannot remove the save button, no, but you can replace its execute method with something that, say, pops up a warning to the user instead.
    > Is there any way to just load the file using a URL?
    The ActiveX control definitely loads a URL. See the "src" property of the ActiveX control. If you download the SDK, the ActiveView sample actually loads a PDF from a URL by default.

  • How to load a PDF from a stream

    Hi,
    I'm looking at how to load a PDF file from a stream in .NET, e.g. something like a MemoryStream or FileStream. All of the methods I've seen so far only allow the PDF to be loaded from a file which we don't want to do because of security issues. I know I can do this with a third party tool, but is this possible without using any additional tools?
    Cheers,
    Dave Harrington.

    > I have a feeling that removing the save button will not be possible.
    You cannot remove the save button, no, but you can replace its execute method with something that, say, pops up a warning to the user instead.
    > Is there any way to just load the file using a URL?
    The ActiveX control definitely loads a URL. See the "src" property of the ActiveX control. If you download the SDK, the ActiveView sample actually loads a PDF from a URL by default.

  • How to create a fillable PDF from InDesign?

    Hi everybody!
    Hope there's no thread about that... by the way. I have to create a fillable PDF from a InDesign file.
    I try to explain: with ID I'd create a file with text form, tables, images with text forms on them etc.... Now I have to export that in PDF and I want to transform the forms (sorry for the bad english, I'm italian) in fillable ones in PDF. How can I do it?
    Thanks to everyone!
    Dario

    Export the ID file as an Interactive PDF.
    Open the PDF form in Acrobat XI  and then:
    File > Save As Other > Reader Extended PDF > Enable More Tools (includes for fill-in & save). . . Your users will be able to fill in the form and save it (assuming they have the later versions of Acrobat Reader).
    Make sure you keep a copy of your original PDF with a different file name as once you've created a Reader Enabled PDF Form you can't change it.
    Derek

  • Random characters added in Excel export from Adobe Tracker (via fillable PDF from FormsCentral)

    Exported fillable PDF from FormsCentral and distributed it via Adobe Pro X.  Received two responses and from the Tracker, we exported to Excel.  In the Excel columns, there are seemingly random characters and the word "edit" which are not in our question.  For example, "_10_8_House_rep_edit;_6S7OYQDcL9nQcNR6j761WQ
    Thanks!

    1. To edit the PDF follow these steps : http://forums.adobe.com/docs/DOC-3661
    2. The fillers don't need to have a subscription (paid or free) to fill up the form. They can fill out the PDF and save it to their machine and then submit. Only the author of the form needs to have a paid FormsCentral subscription to collect data via PDF forms.

  • How to automatically create fillable PDFs from XML

    We are looking for a way to create fillable PDFs that users can enter data into and save (so the PDF needs Reader Rights applied) and we want to be able to automatically create these PDFs from XML files. We are able to do what we want in a manual fashion using Acrobat Pro v8 but we need a way to automate this due to the volume of XML files that we will need to convert.
    Is there any way that this can be scripted from a command line interface with Acrobat.. like:
    Acrobat.exe –input FileName.xml –output FileName.pdf –applyReaderRights true
    If there is no command line options for this is there any way that this could be coded using .NET or any other programming language?

    You cannot automate applying usage rights with Acrobat. For that you'd need to use Adobe's LiveCycle Reader Extensions.
    How exactly are you currently converting XML into fillable forms? Are you using an XDP to somehow convert to an XFA-based PDF?

  • Sharing a "Flattened" copy of a fillable PDF from a mobile device - Reader App

    Ever since the latest iOS update, our fillable reader extended PDF's are not working properly in the Reader App. I created fillable forms and save as a "reader extended" file. When we open the file on the Reader App, we can fill in the form and sign, but when we go to email the form it attaches the blank form to an email. It does not offer the "Share Original" or "Flatten copy" option before going into the email. We use this feature for mobile devices to sign contracts on site vs. going on a laptop. If I open a normal PDF file, a non fillable form, I can email the original or flattended copy from the reader app but this is not needed on a normal PDF. How can I share the flattened copy of a fillable form from the reader app on the iPhone/iPAD? Is this issue going to be resolved or are there settings I need to change in the PDF file before saving it for reader extended?

    Thank you for reporting the issues with Reader Extended PDFs.
      "when we go to email the form it attaches the blank form to an email. It does not offer the "Share Original" or "Flatten copy" option before going into the email."
    As you mentioned, Reader for iOS version 11.2 does not offer the E-mail Document dialog with the two options for Reader Extended PDFs.  We will investigate if this is a new defect that was accidentally introduced in Reader 11.2.
    Regarding the other issue, please note that a PDF form that is sent as "Original" does not become a blank form.
    The problem is that many non-Adobe PDF viewers, such as Apple Mail (the default email app on iOS) preview feature, Apple iBooks, Apple Preview for Mac OS X (desktop), do not render form fields or comments correctly.
    A workaround is to make sure to open an "Original" (non-flatten) PDF document in Adobe Reader.  For example, an email recipient (who views your "Original" PDF form in Apple Mail on iOS) can long press (press and hold) the preview of the PDF form and select Open in Adobe Reader.
    We will get back to you on the issue with the E-mail Document dialog soon.

  • Fillable PDF from RTF template

    Morning all..
    So, I have created a report layout using a RTF file. Then in Application Express, Under Shared Components -> Report Layouts / Queries I have created a report that is filling the RTF file just fine and outputting to PDF. My question would be, once it creates the PDF, Is their a way to have fields in the PDF that the end user can fill in?
    Resonse for this would be for Digital Signatures and other generic fields that are not stored in the database. I know I can creat a form to fill in most of it, but it would be very helpful to be able to fill in the pdf and save after it is generated from the report queries.

    It can be done via a 3rd party product, either using Adobe's pdf product (not reader but the builder utility) or from the list provided by this Google link:
    http://www.google.com/search?client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&channel=s&hl=en&q=fillable+pdf&btnG=Google+Search
    It would be external to your application though..
    Thank you,
    Tony Miller
    Webster, TX

  • Fillable PDF from Smartforms

    Has anyone converted a Smartform to a PDF document with certain fields that are fillable by the user before he prints out the form?  We are on version 4.6C of SAP.
    I do not mean that after he fills them they are communicated back to SAP.  I am just speaking of letting the user key data into certain fields before printing.
    Thanks
    Janice Ishee

    Hi Janice
    Vani's correct. Smart Forms doesn't let you add information to the form once it's output. The complete form is passed to the spool.
    To use truly interactive forms, play around with Web AS 6.40 and the integrated Adobe technology. You can find a lot of background information here in SDN: https://www.sdn.sap.com/sdn/developerareas/was.sdn?page=AdobeForms.htm.
    Regards,
    Markus
    Markus Meisl
    SAP NetWeaver Product Management

  • I can't load a PDF from my Mac to my iPad

    I have made changes to a PDF doc on my MAC. When I send it to my email and open it on my iPad, I only have a blank doc. What am I doing wrong? It shows up fine when I check my email on my MAC.

    Which program are you using?  Pages?

  • How do I down load a PDFs from the web?

    ccan anyone help me with this issue?

    Hi bdreed51,
    Would you provide more information about your problem so that we can help you?
    Did you use Safari (the default web browser for iOS) on your iPad/iPhone to try to (a) open a PDF document in Adobe Reader for iOS or (b) download a PDF document to your iPad/iPhone by tapping a link or button in a web page?
    Is a PDF document already opened in Safari?  What do you see on the screen as a result?

  • Mail trying to load messages and seemingly in endless loop

    Recently, after getting a new logic board, new memory and reinstalling 10.4.11, mail has been trying to download emails from my server and just gives a "fetching message..." in the activity viewer for an extended period of time (I let it go for 10 minutes to make sure). BTW, this happened after I had been receiving emails just fine for 3 or 4 days.
    In the activity viewer window, the "status bars" that normally move are stagnate. It also mentions trying to route the first message from two of my accounts. I don't have any rules set up (other than the default news from apple one) and junk mail enabled. I am using DSL, so it's not a slow download and I searched through my ISP host and could get to the emails, but it would be much more convenient if I could use Mail!
    If I stop the downloading of these emails, Mail just sits and in the activity viewer I get "STOPPING :...." for each one but nothing happens. I have reverted to just Force Quitting Mail to move on, but something is obviously not working right.
    Any thoughts on what's happening or where to go from here?

    Mulder,
    Did 1, 2, and 3 as after each one, still the same problem. After 3, I started Mail without doing anything else, including any updating of software. In console got this long list:
    2008-09-23 22:59:48.187 SystemUIServer[968] lang is:en
    2008-09-23 23:00:20.820 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character b at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.840 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character  at line 1
    Old-style plist parser error:
    Unexpected character '0x2' at line 1
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character at line 1
    Old-style plist parser error:
    Unexpected character '0x0' at line 1
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character at line 1
    Old-style plist parser error:
    Unexpected character '0x0' at line 1
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character at line 1
    Old-style plist parser error:
    Unexpected character '0x100' at line 1
    2008-09-23 23:00:20.886 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character e at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character Q at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.916 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character e at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.927 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character l at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.937 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character a at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.947 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML.'
    2008-09-23 23:00:20.956 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character a at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.966 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character D at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.977 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character  at line 1
    Old-style plist parser error:
    Unexpected character '0x10' at line 1
    2008-09-23 23:00:20.987 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character V at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:20.996 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/InMailbox.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character  at line 1
    Old-style plist parser error:
    Unexpected character '0x3' at line 1
    2008-09-23 23:00:21.008 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/DraftsMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character a at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:21.010 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/DraftsMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character $ at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character at line 1
    Old-style plist parser error:
    Unexpected character '0x0' at line 1
    2008-09-23 23:00:21.014 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/DraftsMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character  at line 1
    Old-style plist parser error:
    Unexpected character '0x1' at line 1
    2008-09-23 23:00:21.017 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/DraftsMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character e at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:21.020 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/DraftsMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML.'
    2008-09-23 23:00:21.026 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/OutMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character i at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:21.028 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/OutMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML.'
    2008-09-23 23:00:21.030 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/OutMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character p at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character at line 1
    Old-style plist parser error:
    Unexpected character '0x0' at line 1
    2008-09-23 23:00:21.037 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/TrashMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML.'
    2008-09-23 23:00:21.039 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/TrashMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character . at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:21.041 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/TrashMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character e at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:21.051 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/junkmail.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character  at line 1
    Old-style plist parser error:
    Unexpected character '0x18' at line 1
    2008-09-23 23:00:21.053 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/junkmail.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character B at line 1
    Old-style plist parser error:
    Unexpected ';' or '=' after key at line 1
    2008-09-23 23:00:21.062 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/junkMailFlag.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character > at line 1
    Old-style plist parser error:
    Unexpected character '0x3e' at line 1
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character at line 1
    Old-style plist parser error:
    Unexpected character '0x0' at line 1
    2008-09-23 23:00:21.066 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/junkMailFlag.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'Conversion of data failed. The file is not UTF-8, or in the encoding specified in XML header if XML.'
    2008-09-23 23:00:21.071 Mail[992] CFLog (0):
    CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be:
    /Applications/Mail.app/Contents/Resources/NormalMailboxLarge.tiff
    The parser will retry as in 10.2, but the problem should be corrected in the plist.
    Error in createMutableDictionaryValue:1012 for property 'Email' 'XML parser error:
    Unexpected character , at line 1
    Old-style plist parser error:
    Unexpected character '0x2c' at line 1
    2008-09-23 23:00:21.091 Mail[992] * -[NSCFString objectForKey:]: selector not recognized [self = 0x5c99bf0]
    2008-09-23 23:00:21.091 Mail[992] Exception raised during monitored invocation of openSynchronouslyUpdatingMetadata:, exception: * -[NSCFString objectForKey:]: selector not recognized [self = 0x5c99bf0]
    Sep 23 23:00:22 kevin-and-tiffins-imac-g5 mdimportserver[961]: * -[NSCFString objectForKey:]: selector not recognized [self = 0x621580]
    Sep 23 23:00:22 kevin-and-tiffins-imac-g5 mdimportserver[961]: -[FileProcessor importMetadataFromFileAtPath:] Got exception * -[NSCFString objectForKey:]: selector not recognized [self = 0x621580] for path '/Users/KnT/Library/Mail/[email protected]@mail.fuhrmanmusic.com/D eleted Messages.mbox/Messages/587.emlx'
    Wow, any ideas now?

  • Loading PDFs from memory

    Hi,
    I'm using PDFLib 8.1 to open PDF documents for creating PNG previews. Using some example code I've successfully created preview images from PDF documents on my file system. What I would like to do is be able to do exactly the same, however the PDF document are stored in a memory buffer.
    I understand from reading similar queries that I need to create my own ASFileSys (and/or ASFile) to implement reading from memory. Can anyone help point me in the right direction for doing this please? Has anyone done anything similar to this? Any code snippets that anyone has will be greatly appreciated.
    Many thanks,
    Alan.

    Hi,
    Thanks for your reply.
    I don't seem to be able to find any ASFileSys samples / skeletons so I'm fighting this problem in the dark :(
    I have instantiated a new ASFileSysRec as follows...
    ASFileSysRec pdfMemoryFileSys;
    memset( &pdfMemoryFileSys, 0, sizeof( ASFileSysRec ) );
    pdfMemoryFileSys.size = sizeof( ASFileSysRec );
    pdfMemoryFileSys.open = OpenMemory;
    pdfMemoryFileSys.close = CloseMemory;
    pdfMemoryFileSys.flush = FlushMemory;
    pdfMemoryFileSys.setpos = SetPosMemory;
    pdfMemoryFileSys.getpos = GetPosMemory;
    pdfMemoryFileSys.seteof = SetEofMemory;
    pdfMemoryFileSys.geteof = GetEofMemory;
    pdfMemoryFileSys.read = ReadMemory;
    ...etc
    (a very laborious task to implement each callback!)
    and I have got as far as ASFileSysCreatePathName working (calls pdfMemoryFileSys.createPathName) and I even see SetPosMemory / ReadMemory / etc being called from PDDocOpen (I simply return the required memory buffer position from a global buffer).
    However I get all sort of problems (exceptions thrown) - I'm pretty sure I'm returning the correct buffer contents/seek positions, etc. I have noticed the following callback functions...
    pdfMemoryFileSys.firstFolderItem (ASFileSysFirstFolderItemProc)
    pdfMemoryFileSys.nextFolderItem (ASFileSysFirstFolderItemProc)
    ...etc
    I've no idea what to return in these callbacks (?).
    It's very frustrating, I don't believe I'm asking for anything too out of the ordinary by wanting to load a PDF from memory instead of a file!
    I'm hoping that someone will tell me I'm crazy to be doing what I'm doing and that there's a much simpler way (?!).

  • Acrobat Javascript button not loading when PDF is opened in browser

    We have a requirement to have a custom print button in Acrobat Reader 9.1.3. We've created this via a JavaScript file stored in the users application data Adobe javascript folder. The button appears when Acrobat is started up normally and works as expected. However when opening a pdf file via Internet Explorer 7  acrobat is loaded inside the browser but the button does not appear automatically. Instead we need to right click on the tool bar and select Add on tools for the button to appear. Once loaded it works as expected.
    Now I was wondering is there a way to make the button to appear automatically when acrobat is launched from within IE as my users are getting a bit annoyed now. I've been searching all over the place and can't find a solution to this.
    Am hoping someone here might have an idea as to what the problem might be. I've attached the code I'm using below.
    Thanks in advance
    app.addToolButton({
    cName: "myToolButton",
    cExec: "printGreen()",
    cEnable: true,
    cTooltext: "Print to Green",
    cLabel: "Print to Green"
    global.objDoc = this;
    printGreen = app.trustedFunction (
    function()
    app.beginPriv();
    var objPrintParams = this.getPrintParams();
    objPrintParams.printerName = "\\\\burns\\prn-cash-copier";
    objPrintParams.interactive = objPrintParams.constants.interactionLevel.automatic;
    this.print(objPrintParams);
    app.endPriv();

    OK... I'm still puzzled. There seems to be something else that controls whether Acrobat JavaScript runs or not.
    If I'm loading a pdf stream though a http GET, JavaScript in Acrobat is run even when the setting in Edit->Preferences is disabled.
    <body>
        <iframe height=600 width=400 src = "http://<some servlet that returns a pdf stream>" />
    </body>
    If I'm loading the pdf from a file...
    <body>
        <iframe height=600 width=400 src = "<pdf file path>" />
    </body>
    ... the expected warning (that Adobe javascript is disabled) pops up
    The http response in the first case is something like...
    HTTP/1.1 200 OK
    Pragma: public
    Content-Type: application/pdf
    Content-Encoding: no-compress
    Content-Language: en-US
    Expires: 0
    Accept-Ranges: bytes
    Server: Microsoft-IIS/7.5
    X-UA-Compatible: IE=EmulateIE7
    Content-Disposition: inline;filename=<some UNC file path>
    Server: WebSphere Application Server/7.0
    X-Powered-By: ASP.NET
    Date: Tue, 17 Jun 2014 19:19:09 GMT
    Connection: close
    %PDF-1.6
    %����
    2 0 obj
    <</Metadata 36 0 R/Pages 3 0 R/OCProperties<</D<</RBGroups[]/ON[27 0 R]/Order 26 0 R>>/OCGs[27 0 R]>>/OpenAction 29 0 R/Type/Catalog/AA 31 0 R>>
    endobj
    Do you have any idea why this is happening?
    Thanks,
    Radu

  • Launch PDF from HTML and execute search

    Is it possible using JavaScript in an HTML doc to launch a PDF and execute a search.query with a passed-in search parameter? TIA

    Hello, George, thanks for following up.  I went into Advanced->Document Processing->Document JavaScripts and put the code at the top of the file outside of the dummy function declaration I had to insert to activate the edit button.  It looks like this:
    // Split the file path into an array
    var aPath = this.path.split("/");
    // Remove the last element, which is the file name
    aPath.pop();
    // Join the path elements back together and add the index file
    var cIdxPath = aPath.join("/") + "/Support Documents/SupDocs.pdx";
    search.query ("Enhanced Tactical Automated Security System (eTASS)", "Index", cIdxPath);
    function Search()
    It runs fine when I launch the PDF directly into the reader by double-clicking in file explorer in the folder above "Support Documents".  When I load the PDF from an HTML file in the same folder, however, the script does not run.  I set the reader preferences to force loading in the reader even when launched from a browser, and the script still will not execute.  I tried adding a button to the PDF and attaching the search script to it.  Again, it runs when launching directly but not from the HTML document.  Otherwise, the PDF is empty, and I'm using a relative URL and JS to load it from the HTML doc, such as:
    document.location = "mySearch.PDF"
    or
    window.open("mySearch.PDF", "searchwin");
    Neither one works.  This product has to run from a CD-ROM, so I haven't bothered to test it via http service.  Any suggestions?  Thanks again!
    Jon Camp
    Senior Computer Scientist
    Applied Research Associates, Inc.
    North Florida Division
    Training Solutions Group
    430 W 5th Street Suite 700
    Panama City, FL  32401
    comm: 850-914-3188 x203
    fax: 850-914-3189
    email: [email protected]

Maybe you are looking for