When I open the .docx file in iMac 10.5 for office 2004 by using the XML open
converter.It is working.
But I use the Mac Book Pro iMac 10.6.
It come up a error message said"There is not enough memory or not enough space
to convert this document ".
This is my computer condition:
Model Name: MacBook Pro
Model Identifier: MacBookPro5,5
Processor Name: Intel Core 2 Duo
Processor Speed: 2.26 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 2 GB
Bus Speed: 1.07 GHz
I also try it in another iMac 10.6. It come up the same error message.
But it is working in iMac 10.5.
Is it a BUG?
Does anyone can help me? Thanks
John McGhie wrote:
You have not told me what the problem "is" so I cannot help you.
18-Feb-10
You have not told me what the problem "is" so I cannot help you.
Remember: I cannot see your screen from here
On 17/02/10 8:00 PM, in article (e-mail address removed)2ac0,
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
--
John McGhie, Microsoft MVP (Word, Mac Word); Consultant Technical Writer,
McGhie Information Engineering Pty Ltd, Sydney, Australia.
Ph: +61 (0)4 1209 1410; mailto:
[email protected]
Previous Posts In This Thread:
Open XML Converter 1.1.3 for Mac failures
Version: 2004
Operating System: Mac OS X 10.6 (Snow Leopard)
Processor: Intel
I am experiencing problems opening Word .docx files. I have open xml converter
1.1.3 installed and use Word for Mac 2004 (office 2004) on a 2006 MacBook Pro.
This is what the converter log file error message says: <br><br>S <br>
Converting file: /[file name] <br>
objc[2140]: Class NLAssertionHandler is implemented in both /Applications/Open
XML Converter.app/Contents/SharedSupport/wordcvtr and /Library/Application
Support/Microsoft/Office Converter Support/Open XML for
Word.framework/Versions/12/../../../MicrosoftComponentPlugin.framework/Version
s/12/MicrosoftComponentPlugin. One of the two will be used. Which one is
undefined. <br>
There was an error opening the file. <br>
Conversion failed <br><br>I have noticed one other reference to this problem
on the Macworld forums, but no answers have appeared. <br><br>Any help would
be appreciaed.
Several key points you do not address:First, please clarify what you mean by
Several key points you do not address:
First, please clarify what you mean by "experiencing problems"... Just will
not
convert? Converter crashes? Presents an error message but converts
successfully? Vague generalities are not at all useful.
1- Is Office 2004 fully updated (11.5.6)? What about OS X (10.6.2)?
2a- Has the converter been working but now fails or is this a recent
installation of the converters?
2b- If the converter was working OK but has now has a problem, what else has
changed on your system (installations, removals, etc.)?
3- Does this happen with one particular file or does it happen with any OXML
files you attempt to convert (including those other than Word files)?
4- Are you dragging into the converter app or are you attempting to open the
file through Word's File> Open method?
5- What can you disclose about the source & content of the problem files as
well as how they came to you (email attachments, network server, USB stick)?
Regards |:>)
Bob Jones
[MVP] Office:Mac
On 1/19/10 3:36 PM, in article (e-mail address removed)2ac0,
Overview: The converter produces an .
Overview: The converter produces an .rtf file that when opened in Word 2004
produces an empty document (0 characters), as well as producing the error
message on the Console file. <br><br>1. Office 2004 is fully updated (11.5.6)
and the MacBook Pro is running 10.6.2 with all relevant Software Udpates.
<br><br>2a. The converter was installed shortly after it appeared in November
2009. To the best of my recollection, it was working when initially
installed, but I cannot swear to it. <br><br>2b. These programs have been
added since the 1.1.3 converter: Scrivener, Adobe Flash Player, EndNote X3,
QT Sync 0.3.3. There have also been a few Adobe Acrobat/Reader updates.
There have been no removals that I can remember. <br><br>3. The problem has
happened with two different Word .docx documents sent as email attachments by
two different work colleagues. One was received on January 14, and the other
on January 19. I have tested some email attachment .docx files received in
December, and they still convert successfully. I do not have any OXML files
that are not Word documents. <br><br>4. I have used the following methods to
attempt to convert these files: double-click from mail.app, double-click from
desktop, drag to the converter, file>open in the converter. All methods
produce the same result. <br><br>5. The files should be ordinary text
documents with simple formating (course syllabus). They came from email
attachments from work colleagues.
I have noticed the nearly identical problem as dbhingst.
I have noticed the nearly identical problem as dbhingst. My version of XML
converter 1.0.3 worked fine on my MacBook until I upgraded to SL. I then
upgraded XML converter to 1.1.3, but still receive the same error message as
db. The only change was going from 10.4.11 to 10.6.2. So db, you are not
alone.
Thanks for the detail ?
Thanks for the detail ? that makes a BIG difference
.
From what you have supplied I am inclined to believe that the problem with
those documents is due to the encoding of the attachments you have received
rather than a problem with the converters or with Word. Can you have the
originators send you new attachments? But have them zip the files first. See
if the added layer of protection is enough to insulate the files from the
email servers. Alternatively, can they get a copy to you using a different
method, such as a USB stick, network drive, web service, etc.?
If you still have a problem it very well may be related to Font issues that
have arisen with Snow Leopard. Launch Apple's Font Book & run both the
Resolve Duplicates & Validate Fonts routines. Once you have handled that, shut
down the Mac for a minute or two & see if things improve after starting up.
Also see the inline responses below;
On 1/19/10 5:30 PM, in article (e-mail address removed)2ac0,
Well, except for 0 characters & error message that is what should happen
Good ? you might also run Disk Utility - Repair Disk Permissions.
That does not appear to be relevant now because (IMHO) the converter is still
"working", but there is something preventing its success.
I do not know that any of them would cause a conflict, but you might try (a)
Logging in while holding Shift, & (b) using the converter in a different
User Account. See what happens in each case.
This points to the fact that the converter is far less likely to be at fault
than the documents themselves or the manner in which they have been forwarded.
What about File> Open in Word? Although I'd expect the same result.
Again, pointing to the likelihood of an issue with the transmission method.
HTH |:>)
Bob Jones
[MVP] Office:Mac
Hi Mark;Please see the response to the other posting. BTW...
Hi Mark;
Please see the response to the other posting. BTW...
On 1/20/10 12:00 AM, in article (e-mail address removed)2ac0,
As for:
I do not now about you, but I consider pulling one Operating System out from
under my software & replacing it with a totally different one 2 generations
removed to be a change of significant magnitude
Regards |:>)
Bob Jones
[MVP] Office:Mac
Bob- <br><br>You are correct - updating the OS two generations is a
Bob- <br><br>You are correct - updating the OS two generations is a
significant change. But it also the only one, so some interaction between the
XML converter and the OS is the likely culprit. <br><br>I did review
duplicate fonts (none found) and removed one problem font (MT Extra) that Font
Book said not to use. Rebooted, but still unable to open my problem .docx
file. <br><br>But there are a few .docx files that I can still open. I will
research to see if I can understand why. But in general, I use only Times New
Roman and Arial in my documents. <br><br>So to recap- <br><br>OS 10.6.2 on
MacBook (Intel) <br>
Office 2004 11.5.6 <br>
XML Converter 1.1.3 <br><br>My problem file was created on my system, e-mailed
to a PC, and sent back with edits via e-mail as a .docx. I do not have the
capability of using USB drives and I am not real comfortable asking my client
to help me with a computer problem. <br><br>db's observation that he(?) can
still open files from older e-mails is interesting. Did MS update anything on
the PC side that might alter the structure of Office '08 files? Just a
thought...
Bob, I upgraded only one level, from 10.5.6 to 10.6.
Bob, I upgraded only one level, from 10.5.6 to 10.6.2 and the problem is
there. I reinstalled Open XML and it made no difference. One thing that may
be relevant, when clicking on the docx attachment in an Entourage message, it
sometimes now reaches for Pages, rather than looking for Open XML.
Mike
---
frmsrcurl:
http://msgroups.net/microsoft.public.mac.office.word/Open-XML-Converter-1.1.3-
for-Mac-failures
I gave up and bought a copy of Office 2008, but kept Office 2004 installed so
I gave up and bought a copy of Office 2008, but kept Office 2004 installed so
that I can use the VBA tools in Excel. The other benefit to 100% compatibility
is that Office 2008 seems to crash less than 2004.
I have two iMacs I have this problem with my Intel based machine using SL.
I have two iMacs I have this problem with my Intel based machine using SL. The
conversion works fine on my older Power PC iMac that cannot use SL.
You have not told me what the problem "is" so I cannot help you.
You have not told me what the problem "is" so I cannot help you.
Remember: I cannot see your screen from here
On 17/02/10 8:00 PM, in article (e-mail address removed)2ac0,
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
--
John McGhie, Microsoft MVP (Word, Mac Word); Consultant Technical Writer,
McGhie Information Engineering Pty Ltd, Sydney, Australia.
Ph: +61 (0)4 1209 1410; mailto:
[email protected]
Submitted via EggHeadCafe - Software Developer Portal of Choice
C# And The Little Iterator That Could
http://www.eggheadcafe.com/tutorials/aspnet/f0cfca12-7398-4b84-a232-0ae26adaa5
33/c-and-the-little-iterato.aspx
