After having to re-install XML Converter, it now fails to convert. Instead I get this message:


objc[200]: 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/Versions/12/MicrosoftComponentPlugin.

One of the two will be used. Which one is undefined.

Conversion failed


So, it appears I need to get rid of something but I'm not sure what. Any thoughts?

I have found two possible plists that might be at fault. Both are located in ~/Library/Preferences

com.microsoft.OfficeConverter.plist
com.microsoft.openxml.chart.app.plist

Thanks Jon. That didn't work.

I used CleanApp to uninstall everything including the entire Application Support folder to XML Converter.....but nada.

As this is a document that's gone back and forth between me and a Windows person, I went back to a couple of earlier versions. They opened.

So, it appears there's something the other person has done inside the document that XML Converter doesn't like.

I suppose I should have done that check first although the current document didn't have any changes, that I could see from a PDF version, other than some text formatting and the addition of a small graphic.

And now it appears that may not be correct. I've just tried to open a .docx file downloaded from Microsoft and it generated the same Console message.

objc[710]: 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/Versions/12/MicrosoftComponentPlugin. One of the two will be used. Which one is undefined.

Conversion failed

I guess I do need to get rid of whatever is causing a conflict.

Sounds like you might want to check for any further updates to the Microsoft Office suite on the Microsoft updates page...and install/reinstall as appropriate...if everything you have installed is current, then I might try isolating one of the the plugins that your log entry is pointing to by changing its' name temporarily (using the Terminal to drill down the path called out in the log entry) so that when called it won't answer.

Back in the day when I still had a version of Microsoft Office installed on my iMac I found that in the long term when a situation of any sort arose the quickest fix was invariably to run the Office Uninstaller and then re-install from scratch. I learned that trick while working for Microsoft training support "engineers".

I could only get access to the to plug-ins...

MicrosoftComponentPlugin.framework and MicrosoftComponentPlugin.

...by going directly to the Application Support/XML Support folder.

I removed each plug-in separately and together but each attempt to open a .docx or .xlsx document, after a plug-in removal, generated this message:

Open XML Converter cannot find the components needed to convert files. To restore these components, install the Open XML Converter again.

I then trashed the XML Converter application as well as the XML Support folder. I reinstalled XML Converter V 1.2.1 and I now have XML "sort of" working.

"Sort of" means: prior to this problem XML Converter worked in the background and simply opened and converted documents. It still does that with Excel and Power Point. However, Word is another story.

A Word conversion does not work in the background. It opens two windows. The first is a "Welcome to XML Converter...." which must be told to go away. The second window follows the conversion process and must be told to go away once it's finished.

Also, and here's the real pain, Word documents don't open as .docx documents. They open as .rtf and there doesn't appear to be anything in any preferences to change that.

So I'm wondering if your suggestion is a better approach.


However, I don't know how to do that.

I gave that a try but my original install disk doesn't seem to care for current versions of OSX. The disk simply froze.

> Also, and here's the real pain, Word documents don't open as .docx documents. They open as .rtf and there doesn't appear to be anything in any preferences to change that.

I don't know whether this is what you're looking for, but didn't the same issue come up a while back and get resolved by changing the .rtf to .docx?

I don't know. If it did, it isn't a thread I recall.

I had problems before with the XML not converting .docx documents at all, but it turned out to be an issue with a particular document from the sender. That person's previous documents had all worked fine.

This time around there are two issues:

1. Word, and only Word, is not working in the background.

2. Word is not being converted to a Word document.

I can do "Save As" to .docx but, between that and the two windows, it's a giant pain in the ......

I'm pretty sure you brought up the same issue a while back, and I believe it was I who first suggested changing the suffix, because I had run into the same issue.

As I recall, it worked for you last time.

I think you're referring to this thread which did involve the XML Converter. However the converter was neither opening with windows nor converting Word documents to .rtf files.

Nope. There's an older thread in which I participated.

But rather than going back and forth about when and where, have you tried what I suggested?

Edit: I can't say with 100% certainty that the thread to which I'm referring was yours, but I believe it was.

If I drag the email attachment to the desktop, change the suffix to .doc and double-click, it will convert as a .doc

However, before it accepts the suffix change I must answer whether that's what I want to do. Also, in order to return the document to the sender I must "Save As" to get it back to .docx There's no change in the number of steps I need to go through.

I'm trying to get Word back to what I had and which both Excel and Power Point continue to do....click on the attachment and it converts automatically and in the background.

In addition the the above I also tried installing the V.1 version of XML Converter and then updating it to 1.2.1, rather than a straight ahead installation of 1.2.1

> If I drag the email attachment to the desktop, change the suffix to .doc and double-click, it will convert as a .doc

And if you change the suffix to .docx rather than to .doc?

Edit: I realize that you'd prefer not to have to use workarounds, but...

But that's the issue. The documents are already .docx but are not being opened properly. The document that gets dragged to the desktop is already a .docx

Here's what used to happen:

1. Email would arrive with a .docx attachment.

2. I would click on it and, with the converter working in the background, the .docx would open.

3. I would modify it and save it as a .docx document that got attached to a return email.

Here's what happens now:

1. Email arrives with a .docx attachment.

2. I click on it and the converter opens a window advising that conversion is underway.

3. The document opens, but has been converted to a .rtf document.


The other two MS applications in the Office suite, Excel and Power Point, are working the same as always. It is only Word that doesn't convert correctly.

That's why I thought MacManiac's terminal idea might be worth trying but I need instructions.

> Here's what happens now:

1. Email arrives with a .docx attachment.

2. I click on it and the converter opens a window advising that conversion is underway.

3. The document opens, but has been converted to a .rtf document.

I follow that. I was just wondering what would happen if you changed that final .rtf to .docx, rather than .doc as you've described.

I do, by a "Save As", after I've modified it.

I don't know much about .rtf documents and my concern is that, if the change to .rtf loses some functionalities of a full Word document, I will have problems when I am dealing with something that is more complicated than just text.

I have lost the conversion I've always had - Word to Word - and now have a conversion to a lesser document in between.

I've stuck to this line of thought because a while back XML Converter was opening my .xls docs as .rtfs, but simply changing the .rtf to .xls got them opening correctly formatted with no further ado.

Try a command-D on one of your recalcitrant .rtfs, and see what happens if you change the dupe's suffix from .rtf to .docx.

I went into User/Library/Mail Downloads and selected one of the .rtfs. I changed the suffix to .docx and the icon changed to a .docx icon. However, when I double=clicked to open it, the conversion failed and the Console had the same message.

objc[2558]: 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/Versions/12/MicrosoftComponentPlugin. One of the two will be used. Which one is undefined.

The file is not the right file type.

Conversion failed

Damn! I was really hoping that would work.

I reread the entire thread and found that this was never addressed:


I'm not certain what MacManiac had in mind with "drill down," but since there's a conflict between two converters trying to convert your doc at the same time, and it somehow seems likely ( ) that the one in /Applications/Open XML Converter.app is the one that should be doing the work, you can "turn the other one off" by navigating to /Library/Application Support/Microsoft/Office Converter Support/Open XML for Word.framework and simply inserting an *, like so: /Library/Application Support/Microsoft/Office Converter Support/*Open XML for Word.framework.

I think that's what MM had in mind, and it's certainly worth a try, although even if it works we won't have a clue as to why. (Have you Googled the issue?)

And if it doesn't work, post back and I'll tell you how to turn the converter in the app off (after you've turned the other on back on).

Out of curiosity... Which version of Office does your original disc install that won't install in OS X 10.6.8? (I had no trouble with Office X when I was running it.)

It appear I was wrong. It's the Setup Assistant installer that freezes (V11.0.0 (040329)) at the point where it asks for personal data to be input.

I did a quick experiment with just dragging the Office folder to the desktop and it immediately began copying files. I stopped it. The Word version is (V 11.0.0 (040408))

There is no version information on either the disk or the box - just the Product Key number. Curious they should be called V11.0.0 when they must be V1.

Anyway, although it appears I could now install everything from scratch, I'd just as soon first try turning the converter off in the app - and avoid having to do all those updates.

That didn't work. I just got the message:

[color:#CC0000]Open XML Converter cannot find the components needed to convert files. To restore these components, install the Open XML Converter again.

I haven't Googled the issue.


It appears I was wrong. It's the Setup Assistant installer that freezes (V11.0.0 (040329)) at the point where it asks for personal data to be input.

I did a quick experiment with just dragging the Office folder to the desktop and it immediately began copying files. I stopped it. The Word version is (V 11.0.0 (040408))

There is no version information on either the disk or the box - just the Product Key number. Curious they should be called V11.0.0 when they must be V1.

Anyway, although it appears I could now install everything from scratch, I'd just as soon first try turning the converter off in the app - and avoid having to do all those updates.

V.11.x refers to (components of) Office 2004 (Mac). Likewise v.12 refers to Office 2008, and v.13 to Office 2012.

OK... After you turn /Library/Application Support/Microsoft/Office Converter Support/Open XML for Word.framework back on by removing the *, here's what you do:

1. Navigate to /Applications/Open XML Converter.app
2. Control/right click on the app
3. Click on "Show Package Contents"
4. Navigate to /Contents/SharedSupport/wordcvtr
5. Turn off "wordcvtr," same as before
6. Pray, but maybe read the following first

I did a Google search for "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/Versions/12/MicrosoftComponentPlugin" and came up with Open XML conversion failed after updating word and Open XML Converter, which is somewhat informative, but not the least bit helpful.

Good luck!

That didn't do it. The result was fairly quick, and terse:

Start time: 2012-11-06 04:41:41 -0800
Converting file: /Users/myname/Library/Mail Downloads/DocumentName.docx
Conversion failed
End time: 2012-11-06 04:41:41 -0800

I then returned the wordcvtr to the folder, and did a restart, which put me back to the starting point. i.e. I tried a conversion of the same file and it opened as an .rtf


It may be providing some help by mentioning the update from 11.5 to 11.6.6. That update was quite recent and I wonder if that's the key. Perhaps later today I will do a "start from scratch" but stop the updates when I reach 11.5. At that point I could try a conversion and see what happens.

Fingers crossed.

Well, thanks for the "crossed fingers" but there is no joy in Mudville.

I first removed all traces of Microsoft Office and did a reinstall from scratch by dragging the file from the original disk. It asked if it could retrieve all Office Identities, indicating it had 11.7MB of them.

A yes response generated a freeze, so basic information and production key number were entered through a series of pages.

I re-started and opened Word. It still had the list of recently opened documents, as did Power Point and Excel. I did the 11.5 Office update which included all previous updates.

After a re-start I tried to open a .docx file but the XML Converter had disappeared somewhere in the process. I re-installed it (V1.2.1) and re-started.

An attempt to convert a .docx generated the unwanted result (not in the background, opens as .rtf).

Since nothing had changed I went through the updates to get back to V11.6.6

Too bad!

I guess you're left with


from my linked post.

Nope. In fact, I checked a few older .docx files that previously opened correctly and each now suffers from the same problems - not in the background, becomes .rtf


The only problem is that I'm not comfortable with running documents through on-line sites without assurances of security. My mild paranoia is underlined by the fact that I don't own the material. It's stuff that comes to me for review and changes, and I return it to the owner.

Mexican standoff!

My final thought is that something has obviously changed, and the only way to find out when it happened is to reinstall Word again and test your docs after each update, the problem with that being that the change may have been in Open XML Converter, and unless you keep an archive or care to play with Time Machine you're dead in the water.

I thought so too......but decided to give it a couple more shots.

First I checked with my daughter who's away at university and confirmed she is using exactly same versions of the OS, MS Word, and XML Converter....and is operating without problems.

a) I reinstalled OS 10.6.8 using the combo update and and also updated Safari.

b) I used Cocktail to:

1. Reset home directory permissions and ACLs

2. Run the three maintenance scripts

3. Purge inactive memory

4. Rebuild Launch Services database & Restore default file associations

5. Clear User (Me) caches for System, User, Internet

6. Check for corrupt Preferences (there were none)

Something in those 6 almost got me there - almost because the .docx files were now all blank-looking rather than Word icons. Also, although they would convert and open directly..... they opened in Pages. Rats.

However, if I dragged a blank icon to the desktop and opened it from within Word, it would convert perfectly. And, the icon on the desktop would change to a Word icon.

I then used Disk Warrior to rebuild the directory (using the Scavenge option and the Ensure Format Case Sensitivity option).

All the icons are now reverted to Word icons and .docx documents convert as they did before. Whew!

Thanks for sticking by through this saga....it's appreciated.

If forced to guess, I'd opt for "4. Rebuild Launch Services database & Restore default file associations," which, with a bit of 20-20 hindsight, seems like it should have been step #1 from the get-go.

(Talk about out of context! )