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

Similar Messages

  • Macs: Export to Word fails

    Take one simple Word file containing one line...
         simple document.
    On MacOS I'm using Word 2008.
    Export this file as a PDF - this appears to use the native Mac PDF export.
    Open PDF with Acrobat DC and attempt to export as a Word - or any complex format.
    I get the dreaded
    Save as failed to open this document
    No file was created.
    This works on one of my machines, and fails on another. There are no problems with file permissions because I am working on the Desktop.
    Is there ANY log which tells me why this is failing? There appears to be nothing in the system log.
    I don't seem to have the option of repairing the installation which some people ask - it's not in my Help menu.
    Re-installing from Creative Cloud seems impossible without losing Acrobat completely - which doesn't seem to be good engineering - what happens if I cannot get it back?
    Anyone with good ideas about
    a)     why this fails?
    b)     can I stop it happening?
    This is Yosemite BTW.

    Thanks for this.  However, after some experimenting, I found the SAME file exports on my laptop but not my desktop. So this is not the file format. It's the installation - OR some library that Acrobat is using or failing to use or it's processor related. Both Laptop and Desktop are running 10.10.3 and are at identical update levels.
    The lack of any diagnostics from Acrobat doesn't help either. Is there some preference which says Tell me everything that is happening?
    Now if Creative Clould allowed me to either verify an installation OR update one - without removing the old one - I might be able to cure it.  CC should allow me to re-install anything, just in case.

  • 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

  • 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.

  • 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

  • 'Unknown Error' on Export or Word!

    Any attempt to export any document (even a blank one) to Word format fails with an "unknown error".
    This is a new error that did not occur before, even with complex documents. I have rebooted, deleted the preferences file, etc. Does anyone else have this problem? Any thoughts on how to fix it?

    I have been FIGHTING with the "Unknown export error" problem all day long, and I just figured out what the problem with my particular document was: it was because I had pasted an outline from Keynote into my document.
    Here's a run-down of the other possible causes of this problem (all of which I tried and none of which worked): I tried deleting my preferences, activating and validating all my fonts, unclicking the "Include preview in document" box in the "Save as" menu. Because I was able to export a blank .pages document to Word, I went through my entire document, deleting bits of it until I was successfully able to export to Word.
    I discovered that it was because I had pasted a little outline from a Keynote presentation and that the style (either paragraph or character, I'm not sure which) of the pasted bit confused Pages. Just highlight the [potential] problem area and choose "Normal" from the drop-down "Choose a character style" button, then for good measure choose "Normal" from the drop-down "Choose a paragraph style" button. Breathe a sigh of relief.

  • Pictures from my iphoto library can't be exported to word

    I am trying to import a picture from my iphoto library into Microsoft Word and it will not work. When I attempt the transfer it says: This application cannot open this file. This file is an unsupported graphic format or may be damaged. Try opening the graphic in another application.
    When I try to import photos that have been downloaded to my computer through a source other than my digital camera, it works.
    Also, after working with a recently imported roll of pictures from my digital camera, the program iphoto unexpectedly quit. Could it be that my camera is causing these problems?
    iBook G4   Mac OS X (10.3.9)   i am using iphoto 4

    Your subject line says you can't export to Word, and your post says you cannot import into Word -- these are diametrically opposite problems. You have apparently described the distinction between a successful import and one that fails. If you are able to import photos from the desktop, then export your iPhoto images to the desktop, before you import the images to Word from the desktop.

  • Crystal Report error exporting to Word

    My company recently deployed a Microsoft Security Patch to our workstations that's causing a problem with Crystal Reports. When exporting a Crystal report to a Word file (from a VB 6 application) the following error is generated when opening the file: "You are attempting to open a file that was created in an earlier version of Microsoft Office. This file type is blocked from opening in this version by your registry policy setting."
    My company uses Crystal Reports v 8.0.1.0. Is there a more recent release that provides a fix for this error?
    Thanks.
    David
    Edited by: David Verbinski on Nov 5, 2008 10:35 PM

    I know 100mb works because I have created word document reports with that size before using the crystal export.  Just really big reports.  I'm not sure on the exact size because it doesnu2019t work but I know there is more data in the report than the 100MB report which works so it doesnu2019t work on some reports larger than that (don't know the specific size because it doesnu2019t work) sorry for being redundant.
    Not sure about a size limitation on an RTF formatted document that is saved as a *.doc (word document).
    It's my understanding that exporting to a .doc is the same as exporting to .rtf because the .doc is in .rtf format.  I may be wrong but if you change a .rtf extension to a .doc extension, you get the same thing when opening the file in word.
    When exporting to RTF format I get the same error, so I believe they are using the same or similar process.
    Yes I tried on other machines and different servers and the error only occurs when exporting large documents to word.  Small documents work fine.
    If there are file constraints in exporting to word, I believe a more distinct error message could be displayed related to the specific error.
    No I did not upgrade my pc or software, I developed the report and am running specificly for 11.5 release 2 with service pace 3 installed. 
    Thanks,
    K

  • Creation of the export data source failed

    trying to activate ods but getting this message that the creation of the export data source failed.
    and it also gives message that RFC Connection to source system is damaged===> no metadata upload
    Please can someone help me with this.
    Thanks in advance.
    Michelle

    Hi,
    Check ur source system connection. by going to RSA1-> Source System-> right click and then select check.
    U will get the info about the source system Connection. IF RFC has failed then better be in touch with ur basis.
    Or try restoring ur source system connection by
    Source system-> Restore.
    Its sets all the default conenctions b/n ur systems.
    Once again check the connection now. if it says ok.. then try do the export data source and then assign the data source to info source and then maintain the Update rules..
    Hope this helps-
    Regards-
    MM

  • Purchased export to word etc

    1. I purchased export to word etc., paid iTunes - still does not work asks me to pay again., 1. I purchased export to word etc., paid iTunes - still does not work asks me to pay again., 1. I purchased export to word etc., paid iTunes - still does not work asks me to pay again.

    Did you sign in with your Adobe ID?
    [topic moved to Acrobat.com Services forum]

  • Export to WORD - what's with these boxes around the text?

    Post Author: Emily
    CA Forum: Exporting
    I am new to CR.  I am using version 10.0.0.533  We use CR with ClearQuest for problem reporting and other data collection.
    Rational (ClearQuest Vendor) tells me it's a CR X problem.
    I use a CR report exported to MS WORD as a template for taking meeting minutes.  With our old CR version, the ClearQuest export was great and I was able to add text into the report.  With CR X, the report in MS WORD comes out in text boxes and editting this output is not pretty.   I do not want the boxes, I just want free flowing text as if I had written a WORD doc so I can edit it easily during the meetings.  I have tried export to text, copy, paste but I loose all of the formatting.  I have tried HTML and then copy, paste, but this is even worse than the text output.  RTF also has the text in boxes. 
    Someone out there MUST have run into this problem also.  Help me... 

    Post Author: kepner
    CA Forum: Exporting
    Hi,
    Did you find the solution to export to Word in the free flow text format? Could you please share with me the resolution.
    Has any body foud the resolution to this issue? any updates from MIcrosoft or BO.
    Regards,
    Kepner.

  • Export to Word loses tab setting

    Post Author: HmCody
    CA Forum: .NET
    I am very new to Crystal Reports with VS.net and have run into a problem that I hope isn't a bug.
    I am creating a report that needs to be able to be exported to Word (it gets sent to the printer for inclusion in a program).  Several of the text objects are formatted with right tabs set at the right edge of the object.  Everything lines up perfectly when the report is viewed in the Report viewer and when I export to a pdf, but when I export to Word the right tabs are converted to left tabs and the text aligned to them is out of view.
    Anyone have a clue as to why this is happening and if there is a way to fix it?
    Thanks for your help.
    Helenmary

    Sorry - no pointers. Other than patience - this is a known issue, probably to be addressed in Service Pack 3 of Crystal reports. See Kb [1643979 - Crystal Reports for Visual Studio 2010 does not look for ForceLargerFonts registry key|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333633343333333933373339%7D.do]
    I have seen one or two reports of people using the below KBase with success (you'll have to modify the reg key to reflect CRVS2010). But most have no success. Testing this I did not have any success either, nor did I see the CRVS2010 engine looking for any of the keys noted in the KB....
    [1644563 - How to create the ForceLargerFonts registry key when using Crystal Reports 2008 (12.x)|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333633343334333533363333%7D.do]
    Ludek
    Follow us on Twitter http://twitter.com/SAPCRNetSup
    Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]
    Edited by: Ludek Uher on Jan 19, 2012 6:37 AM

Maybe you are looking for