Failed to export to Word

After uploading my pdf, I was told that it failed to export to Word due to an unexpected problem. Now what?

The problem with filling out the File Conversion Issues Form is that it requires an upload.  My file is 22.9 MB. But the form limits the upload to 20 MB.  As I understand it, the allowable size for conversion on line is 100 MB.  This is stated in a number of areas.  If the limit is 20 MB (I'll try splitting the file  next), it would be useful to say that.  Also, there are a number of comments on the same subject with no reply.  It would be helpful to direct people to the answer without having to trace throught 50 or so comments on the "unexpected problem" before finding an answer.  Like others, this is a one-off task.  For my $20, I would expect the on-line program to at least give me some guidance as to what the problem is.  
Regards,
Scott

Similar Messages

  • My 22 MB pdf file "Failed to export to Word."

    I have tried several times to convert a 22 MB pdf file to Word, but I receive this error message every time: "File failed to export to Microsoft Word.  There was an unexpected problem."  No further explanation is available.  I know my ExportPDF is working, because I have tested several other smaller files.  I even tried using a different browser (Chrome and IE) and home and work computers.  I checked the permissions of the document and I have all that are available.  The pdf document seems to upload OK although it takes a few minutes because it's large, but then I receive the error message.  I got the original file from an internet site (legitimate).  Any ideas?     

    Try disabling OCR with these instructions: http://forums.adobe.com/docs/DOC-3062 to see if that helps.
    If it doesn't, please open the PDF in Adobe Reader and choose File > Properties.  Let us know what it says next to 'Application' and 'PDF Producer'

  • Export to Word fails

    Most of my help projects are exported to Word at some point
    for editorial review. This works fine except on one project. When
    exporting this problem project, the process fails on any number of
    topics and always with the glossary. It looks like the project is
    damaged in some way, though it builds fine as Web help and HTML
    help. here's what the log says:
    Warning: The Word Document became corrupt when attempting to
    append a malformed topic: mytopic.htm'
    Failed to process 'mytopic'...
    Fatal Error: Word Document got corrupt. Abort building
    'References'.
    Failed to build 'References'...
    Failed to build 'References'...
    Failed to build one or more chapters.
    Building 'Glossary'...
    Failed to build 'Glossary'...
    I've replace 'mytopic' but the errors remain. The source code
    does not seem to be the problem. also, the export fails on various
    other topics too. If I exclude the glossary the export fails anyway
    on any number of topics. As soon as an error occurs, Word fails to
    respond. The only way out at that point is to kill the applications
    via Task Manager.
    The project is huge - about 1000 topics and plenty of
    hyperlinks between them. I don't want to have to import them into a
    new RoboHelp project unless all the links remain intact.
    I am using RoboHelp 5.02x on Windows XP on a computer with
    ample resources.
    Any suggestions would be very welcome!
    googun

    You could also create several SSLs, each of which generates a
    portion of the project. If you have topics grouped into folders,
    even better.
    If you must have a single document, then just append all the
    Word docs after running all the SSLs (and by the way, you can batch
    generate any combination of SSLs).
    Good luck,
    Leon

  • "filename.pdf" failed to export to Microsoft Word. There was an unexpected problem.

    "filename.pdf" failed to export to Microsoft Word. There was an unexpected problem.
    Every time i have tried to convert a pdf file to doc file I had this message.
    Could someone help please.

    Try disabling the OCR function of ExportPDF to see if it helps with your conversion. You can find instructions on how to do this here: http://forums.adobe.com/docs/DOC-3062
    -David

  • Error message - failed to export to Microsoft Word

    I signed up for this servive and it does not seem to be working for me. I have tyried different pdf files and browsers and I keep getting the same error message.

    I am also getting the same error message with a scanned text pdf file.  The support page says it will OCR scanned text pdfs and convert to Word, but I keep getting a "failed to export" message.  The file is only 19 mb, well within the 100 mb limit.  This is the only reason I subscribed, to convert scanned text pdfs to Word, and now the service does not seem to do what it says it will do.  I spent three hours with tech support before they finally informed that there is no tech support for this product, only the forums.  So here I am.  I trust someone with the necessary knowledge and expertise at this forum will be able to help me resolve this issue.

  • Error  "BMOD.pdf" failed to export to Microsoft Word. There was an unexpected problem.

    What does this mean and how do I fix it?
    Error  "BMOD.pdf" failed to export to Microsoft Word. There was an unexpected problem.

    Hi Calin,
    I apologize for the trouble. Have you tried it again recently?
    Let me know!
    Looking forward to hearing back from you.
    Kind regards, Stacy

  • Export to Word from SAP B1 2007A

    Hi all.
    When trying to export marketing document (sales order) to word from SAP B1 2007 A - I get error message. The error message appears in the word document and it states "unacceptable field". The template document also fails to return values in some of the data fields. We are using Office 2007.
    I have tried solution from notes (868723), saying to check "typing replaces selection". I've also set macro settings to low and given acces to VBA Projects.
    Has anyone some suggestions?
    Thanks and regards, Runar Wigestrand.

    Hi Runar,
    The following link is to the documentation about how to export to word. Check if it helps you with some useful information  :
    https://websmp108.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_HIER_KEY=701100035871000371280&_OBJECT=011000358700001146622005E&_SCENARIO=01100035870000000183&
    Regards,
    Jitin

  • Export to Word RTF - Page Server error when over 160 pages exported

    We have XIR2 SP2
    We have a Crystal report published into this Enterprise which, when all parameters are widened, runs to 190 pages.
    The resultant report includes tables
    We can export to PDF but the client requires it in Word RTF
    We can export to Word RTF Editable - and all 190 pages are produced in the resulting file, but of course the tables are omitted and the result is messy.
    So, we need to export to Word RTF where the format is neat and includes the tables.
    However, when we try and export more than 160 pages to Word RTF, we receive the following error.
    CrystalReportViewer
    handleCrystalEvent failed
    Unable to retrieve Object.
    The Page Server you are trying to connect to is not accessible. Please contact your system administrator.
    We have a duplicate environment with an identical configuration, standing by as a failover environment and which points to the same data.This produces the same error, so we don't think it's an installation corruption or failure.
    The page server is set to a maximum of 2,000,000 rows, the cache server at 256000 maximum.

    Hi Tony F,
    Many thanks for coming back on this one. Both Enterprise servers are identical in BO config, Windows 2003 server, but different in hardware.
    One has 4 proc and one has 2, one has twice the memory of the other, yet both fail at over 161 pages. Both have their boCMS db's on different servers, both derive the data from different servers.
    IIS is the web server. The only common denominator is the actual installation software itself and the person who installed it (me).
    On Friday, instead of running the reports in Enterprise/Preview or Infoview (both exhibit the problem) I switched from our default activeX to DHTML, and advanced DHTML. No improvement (Our report wouldn't work with Java, which we never use)
    On the suggestion of the SAP/BO support girl, I then SCHEDULED the report for immediate running and chose WordRTF as the format. This works fine.
    So on that evidence I suspect a software glitch that is specific to using Infoview to open the report rather than schedule it - the two processes must access the WordRTF translator in different ways.
    I'm hoping there is a patch or hotfix that can solve it. Sadly, our users don't have the appetite for the few extra clicks to use the workaround so we're going to have to pursue it with BO unless the forum comes up with an answer - perhaps its something I didn't do properly on installation, or a CMC/CMS setting. We've got 2m row limit on the page server but the report's row count is nothing like that and, anyway, it works if scheduled.
    I'm really grateful to you for taking the time to reply, I hope the above answers your question - if I had hair to pull out, I'd be doing just that!
    Kind regards
    Tony W

  • Export to Word Errors - possible fix

    Like several other people have mentioned, I wasn't able to export to Word. I'd get an "unknown error has occurred" error message and it failed. I decided today I'd solve this problem if I could and since I knew lots of people were exporting as Word okay I had three suspects in mind. It was my second.
    Using Font Book, I turned off all the Chinese, Korean, Japanese and Arabic fonts because I don't need them. Oops. I haven't delved into which are absolutely necessary (assuming any are not) but turning on all the default Apple fonts was the fix for me.

    Great tip. Following your advice with a little trial and error discovered that the Japanese font Hiragino Kaku Gothic Pro is the only one I needed to activate in order to successfully export to Word.

  • Failed to export

    I've tried to download my first 2 pdf files to excel and I get 'unexpected problem, file failed to export'.  Does this service actually work?  If not, I'd like my moeny back.

    Hi,
    To  disable OCR:
    1) In web ui at https://exportpdf.acrobat.com  turn off the box for "Recognize scanned text in" in Export Option dialog.
    2) In Adobbe Reader
    Turn on the box for "Disable Text Recognition" in OCR Setting after clicking "Change" under "Recognize text in English(US)"
    You can download Acrobat XI Pro trial version from www.adobe.com and install it on your computer.
    Then open your PDF file in Acrobat and select File menu > Save As Other > Microsoft Word.
    Thank you.
    Hisami

  • Why has my pdf document "failed to export"?

    I've just bought a subscription to export and convert pdf files to Word files, and only the second document I tried to convert is refusing to do so, giving the message "failed to export.  There was an unexpected problem".  Is there anything I can do to get this to work?

    Hi Robin,
    Can you share the file with us via the File Conversion Issue form?  Please include a link to this thread in your description of the issue.
    -David

  • Pages export in Word format problem

    A Pages-5 file exported as a Word file opens in MS Word as one would expect but crashes or fails to open in Open Office 4 which opens all other .doc/.docx files perfectly.  The new version of Pages must be doing something strange to the Word format as this never happened with earlier versions. 
    Any ideas ???

    Exported a .docx from IOS Pages v2.0.1 (new format) to OS X Mavericks and Lion.
    The above file crashed LibreOffice 4.1.3.2 (latest) on both operating systems. It opened fine in Preview, TextEdit, Quick Look, and Bean (3.2.5) on both operating systems. On Lion, it opened fine in Office for Mac 2011 (4.3.9). Do not have the latter installed on Mavericks.
    On Mavericks, opened this .docx in Pages ’09 v4.3 successfully with import warnings about removing all borders, and a large white-space area between text on the first page.
    On Mavericks, I opened this .docx in TextEdit. Added two words to it, and updated it in place. I then dragged and dropped it on the LibreOffice icon in the Dock. LibreOffice opened it without issue.
    Clearly, the IOS Pages export to Word (.docx) has some compatibility issues with OpenOffice and LibreOffice, as apparently does Pages v5 on OS X.

  • Mac OS 10.6.7 corrupt font on export from Word to PDF

    Hi,
    I have a library of Word documents that use our corporate font: Officina Sans ITC Pro Book. I have previously saved these as PDF using Word for Mac and opening in Acrobat Pro 9 without any difficulty.
    Today however, while Word will export and create the PDF. When the PDF is opened in Acrobat it comes up blank and crashes Acrobat. I have tried exporting from Word to PostScript, but this fails: "Stack:/Font-dict-/ZCYKUX+OfficinaSansITCPro-Book".
    The font is avialable on the Mac. I have validated the font and using Font Finagler I have cleared the cache. All without success.
    One pointer is the additional six digits in the PS log, which is in front of the font name.
    Anyone got any ideas on how to clear the problem and start export cleanly from Word to PDF again?
    Thanks,
    Niall

    Thanks Steve,
    The link described our situation. You are correct: yes our font is OpenType PostScript and, yes I had updated to OS 10.6.7.
    I have been busy reading. For other readers there is a long thread here: http://discussions.apple.com/thread.jspa?threadID=2792142&start=0&tstart=0, where I see that you have also participated.
    I have posted constructive critisim to Apple on the OS update. However I don't think there will be a quick fix.
    I will probably downgrade back to 10.6.6, but need to steel myself for the task.
    Thanks also to Larry and Michael!
    Niall

  • I keep getting this error message, why? "performance band report unit 3.pdf" failed to export to Mic

    Failed to export to Microsoft word.  THis is the error message I get, why wont it export?

    Could be some incompatibility with 10.6.8 or something you added to your system.
    Try downloading the 5.4.0.1771 version and see if you have any better luck.
    FWIW, I just downloaded 5.3.59.1093 and it worked "ok" on my 10.6.5.  Of course "ok" is a relative term when it comes to skype since Microsoft took it over!

  • Pages fails to export PDF

    I am receiving an "Unable to print" error when I attempt to export a document to PDF format. The PDF appears in Finder, but has a zero file size. I have run into this problem only recently, as I was able to export PDFs of similar documents before (about a month ago.) Does anyone know why this may be happening?

    I tried this with a new - blank Pages file with just one word on it. It still fails to export with a "print error". The work around of using Print and saving as a PDF does not address my problem. I want to Export to PDF so that my Links and bookmarks are preserved in PDF. Printing only gets the image of my Pages file to PDF but with no special features.
    Has anyone resolved this export problem yet? Could it be a bad or corupt preference file or similar system file conflict. I have seen sometimes where in some apps you can delete certain preferences and resources and then re-run to correct the problem..... could this apply to Pages and what would be removed to make it work?

Maybe you are looking for