-
1. Re: EBookExport.InDesignPlugin error on document open
kevin.cecil Oct 30, 2012 12:53 PM (in response to kevin.cecil)Anyone?
-
2. Re: EBookExport.InDesignPlugin error on document open
Markus bei Plutonika Nov 2, 2012 7:39 AM (in response to kevin.cecil)I second this.
I’m not sporting a superfresh install, but the problem surfaced overnight and out of the blue …
Markus
-
3. Re: EBookExport.InDesignPlugin error on document open
kevin.cecil Nov 2, 2012 7:47 AM (in response to Markus bei Plutonika)Did someone else (outside of your normal production process or team) open the file that is throwing the error?
-
4. Re: EBookExport.InDesignPlugin error on document open
Markus bei Plutonika Nov 2, 2012 7:50 AM (in response to kevin.cecil)Nope. And it’s my machine only. The other 4 people on my team don’t experience this.
I’ll see if I have any luck resolving this and keep you posted …
-
5. Re: EBookExport.InDesignPlugin error on document open
Markus bei Plutonika Nov 2, 2012 8:11 AM (in response to kevin.cecil)Hi Kevin,
maybe a bit dirty, but did the trick for me: I just copied the plugin from my colleague’s machine over AFP and – tada! Either the thing got corrupted somehow or it’s a version issue. The one that works for me is 8.0.1.406
Please mail me at mmr@plutonika.com for an unspoiled copy …
Markus
-
6. Re: EBookExport.InDesignPlugin error on document open
kevin.cecil Nov 6, 2012 11:06 AM (in response to Markus bei Plutonika)I have been working with Adobe support. They have a known issue with Extensions not loading properly that is supposed to be fixed with 8.0.1.407. My InCopy will not update past 8.0.1.406, even though teh curetn versipon is supposed to be 8.0.1.407. The engineers that I have been working with have been able to replicate my issue. Maybe help is on the way!
-
7. Re: EBookExport.InDesignPlugin error on document open
Markus bei Plutonika Nov 6, 2012 11:29 AM (in response to kevin.cecil)Let’s keep our fingers crossed …
-
8. Re: EBookExport.InDesignPlugin error on document open
kevin.cecil Nov 8, 2012 6:50 AM (in response to Markus bei Plutonika)I have been working with Adobe over the past week to identify the root cause and try to find a resolution. After providing them with some sample files and walking them through the steps to reproduce the issue, I got this response from our engineer yesterday:
"Our Engineering team identified the problem as Bug and the number is 3361590 for your reference.
They are currently working on it and the bug has been logged under Cosmetic category as it has zero impact on the working of the file."
Due to the annoying nature of error popping up every time the document is updated, I challenged the "cosmetic" classification and the engineer agreed to "provide feedback under bug records regarding impact user is facing."
At least it the error is reproducible and is on their radar…

