David Baldaro – XMPie and the “Missing Plug-in” issue

XMPie and the “Missing Plug-in” issue

I have seen several posts and blogs reference the error message that designers sometime get when they open up a document stating that “XMPBackEnd5.pln.InDesignPlugin” is missing.

This is caused when the XMPie uDirect or uCreate plug-in has been installed on the creator’s system and a document created and sent to another. Even if the XMPie plug-in is not used to personalise a document this issue can be created.

I recently asked Gal, from tthe R&D team about this and this is what he said…

“The problem that is experienced is a result of XMPie adding properties to certain components of the document. For example – A spread gets the property of whether it has a visibility ADOR or not. A box gets the property of whether it has text length handling (auto flow, copy fitting) and if so In what way.”

“The way this is implemented is by using the only technology available for this by Adobe which as a by-product forces that the properties are added to the document whether you actually place valid values or not (meaning – whether you set them or not). If they are not set to specific values they simply get null values – but still the properties are there. Since the properties are there taking the document and opening it in another InDesign installation provides a warning that there is no support for these properties – i.e. the “missing plug-in” warning.”

So, the answer here is not straight forward, and XMPie is talking to Adobe about this matter it would seem. Gal goes on to mention that they have seen this issue replicated in several other Adobe Plug-ins that make changes to the document in the same way; so it would seem that this is not solely an XMPie issue.

The best way to overcome this?

You could always install the XMPie plug-in I guess; free-of-charge and fully functional from www.xmpie.com.
If you are the creator of the document then disabling or removing the XMPie Plug-in; before resaving the document should work.
Exporting the document to an INX or IDML file will also do it’s best to remove any conflicting tags.

[message type="info"]Full disclosure: At the time of writing this article the author was employed by XMPie, a Xerox Company. [/message]

About the Author: David Baldaro

A seasoned, passionate technical sales and marketing professional.A solid and experienced background in digital printing, multi-channel campaigns and transmedia. I am always seeking out new technologies and ways of working.

4 Comments

Isabel Zawislak December 19, 2010 at 3:29 pm - Reply

Excellent information it is actually. My friend has been waiting for this content.
Rich Larson November 4, 2009 at 4:55 pm - Reply

This info was very helpful in solving the XMPie issues I was having. The “INX method” worked well with no loss as far as document content or structure. I guess I got lucky. However, in both this Blog and Claudia’s Blog a Free Plugin is mentioned. I have not found such a plugin on the XMPie or Adobe website. Do I have to install the trial version to get it?
More on the XMPie Plug-in Issue March 26, 2009 at 4:52 pm - Reply

[...] “Folks, I’ve been chatting with the R&D team on this issue. For all the details check out my blog, http://david.baldaro.me.uk/2009/03/xmpie-and-the-missing-plug-in-issue/” [...]
Claudia McCue March 25, 2009 at 3:14 pm - Reply

David,

Thank you so much for pursuing this! It seems to have shined a light on some deeper issues; we’ll stay tuned, and try to fine-tune the INX/IDML process. My clients with CS3 are stuck with the INX route, of course, but it will be interesting to see if IDML does a better job of preserving the document.