Export to Word Error

When I use the File . . . Export menu and choose Word, I get an error message. The Exporter works fine going to RTF. Anybody encountered this and know a fix? I really like Pages a lot more than Word but I have to open Pages documents in Word sometimes. If I just try to open in Word, without any export conversion, I get a window with all kinds of files and folders in it, none of which is the document. "Help" says to export. But now the error. If I export to RTF I can open fine in Word, but why do that?

What error message do you get?

Similar Messages

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

  • Exporting to word error "Directory name is not valid.. "

    Hi Experts,
    I'm getting an error when I'm exporting a Delivery document to word document, Microsoft word opens but error message appears: "Directory name is not valid. C:\Program Files\SAP\...ODLN.428.doc". I am getting the error in the client workstation.
    I tried correcting the path in the server for the word templates path, but still the error persist.
    Client is using 2007 version SP1 PL8 HF3.
    Thanks,
    Don

    Hi Don Elicor
    Check the Administration > System Initialization > General Settings > Path tab for the definition of a proper path to the Word directory.
    Hope Helpful
    Regards
    Kennedy

  • 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

  • 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

  • I have paid for a year subscription, but all the PDF's I attempt to export to Word give me a "Conversion Error" message, citing that the "file's security settings do not allow export." I want a refund. Adobe, please advise. Thank you.

    I have paid for a year subscription, but all the PDF's I attempt to export to Word give me a "Conversion Error" message, citing that the "file's security settings do not allow export." I want a refund. Adobe, please advise. Thank you.

    Hi la recruiter,
    There are a few types of files that Acrobat can't convert--and PDF files with security applied is one on them. I'm happy to cancel your subscription, if you decide that it's not going to work out for you. Please confirm that you'd like me to proceed with the cancelation, and I'll take care of it right away.
    Best,
    Sara

  • Pages shows error when trying to export to Word

    Today, without doing any updates or making any changes to my MacBook, Pages has decided that it won't export documents to Word or PDF, showing me an error message after attempting to export. I've googled forums to try & find a solution, but all I can find is that it's something to do with Style. The Page documents are in exactly the same style etc as I was working on yesterday when I was successfully able to export documents to Word. Can anyone help please? I need to upload as Word documents for uni.

    May this thread be helpful for you?
    Can't export pages to word
    Have you tried to save any other pages file as Word, not only the documents for university?. Create a new file a write a word there then try to save it as a Word document. If it does, then the problem is in your University document as it may contain something incompatible with exporting to Word.

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

  • Why am I unable to export to Word, getting an unexpected error

    I seem to no longer be able to export a Pages document to Word. I get an unexpected error message. Anybody know how to fix? Is this one of deleting preferences, or something to that effect, to get it to work again? Any help is appreciated.

    You updating MS Office shouldn't affect Pages exporting to Word.
    I think you should try uninstalling iWork/Pages and install it again. 
    To uninstall correctly iWork, go to Yvans iDisk :
    <http://public.me.com/koenigyvan>
    Download :
    For_iWork:iWork '09:uninstall iWork '09.zip
    Expand the archive and run the script.
    Restart the computer and install iWork/Pages again.

  • How to export to word when error

    I'm trying to export to word, but an error comes up halfway through

    You do try to repair acrobat xi:
    Choose Help > Repair Acrobat Installation

  • Export to Excel Error in SQL Server 2014 Report Builder/Viewer

    Hi,
    I am using the 2014 version of ReportViewer in a WinForm to display an RDL report.
    The report was originally created in Report Builder 2.0 (SQL 2008 R2), but has since been edited in Report Builder 3.0 (SQL 2014).
    The report loads and displays OK, and even exports to Word and PDF. But when exporting to Excel and then opening the Excel document, the following error occurs:
    "We found a problem with some content in <filename>. Do you want us to try and recover as much as we can? If you trust the source of this workbook, click Yes."
    If you click Yes, then a second message appears:
    "Removed Part: /xl/styles.xml part.  (Styles)
    Repaired Records: Cell information from /xl/worksheets/sheet1.xml part"
    The Excel document then opens, and the data is there, but there is no formatting (no border columns, colours, bolds etc.)
    The three interesting things are:
    - When exported from SQL 2008 R2 Report Builder 3.0, which exports to .xsl instead of .xslx, it works
    - A brand new report created in 2014 Report Builder 3.0 exports to .xslx great
    - In Report Builder 2014, I stripped everything back and removed all rows and columns so the original table in the report only has one empty row and column it the export still errors - it is only by removing the original table and creating a brand new table
    that export works OK
    It appears to be a problem with the tablix, but ideally we don't want to have to recreate our reports from scratch to fix this issue.
    Has anyone come across an issue like this before, and know of any potential resolutions to it?
    Thank you.

    Hello,
    Based on your description, you render a report originally created in Report Builder 2.0 (SQL 2008 R2) and export the report to excel with format of Excel 2007-2010.
    Edit the report in Report Builder will not upgrader the report. In that case the report still with SSRS 2008 R2 RDL schema. Please try to upgrade the report by open the report in Report Designer in SQL Server Data Tools (SSDT) and then try again.
    If you don’t want to upgrade the report, please try to export the report
    with Excel 2003 rendering extension and check if the issue persists.
    The SQL Server 2014 and SQL Server 2012 Reporting Services Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010 with .xlsx as file extension. Only the Excel rendering extension is available by default.
    You must update the Reporting Services configuration files to make the Excel 2003 rendering extension available.
    For example, changing the value of Visible to
    true in the following line in the RSReportServer.config:
    <Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"
    Visible="true"/>
    Reference:Upgrade Reports
    Exporting to Microsoft Excel (Report Builder and SSRS)
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

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

  • Export to Word using Adobe Acrobat 9 Pro (mac)

    I get an error message when I try to export to word using adobe acrobat 9 pro for mac.  Any tips?

    Hi Bill,
    Thanks for replying.  The entire message is below.  Any ideas?
    Acrobat was unable to make this document accessible because of the following error:
    Could not convert the document (exception caught).
    Please note that some pages of this document may have been changed. Because of this failure, you are advised to not save these changes.

  • Pages won't export to Word

    Running latest Pages in latest Lion on a new iMac. When I try to export to Word, I get an error message: "The file format is invalid."
    A Word doc IS actually created, but it has all Comments stripped out...making it utterly useless to me. I've tried uninstalling iWork 09, restarting the iMac, then reinstalling (and re-upgrading) iWork 09 from the original disc, but no love -- it just won't export a Word file with Comments.
    Anyone else having this problem? Anyone have a solution?
    Thanks!
    Barry

    Well, I tried export to Word before saving the document in Pages. It worked fine! I didn't finalize the changes in any way. I could open the .doc document and it still showed the changes and comment field.
    I think something is corrupt in your document. You could select the content and paste into a new blank template and save it and then export to a Word document. Then undo all changes in the original document to the point you started the changes and copy and paste  into a new document and give it a different name. Now you have a before and after the changes and hopefully the  corruption didn't get copied over.

Maybe you are looking for