I'd say one thing you could do to try and recreate it is, upload a Word file on that instance and see if it gets indexed and see if the error gets triggered. My guess is, this is a "Heisenbug", one that we won't be able to recreate. We could perhaps put a little more forensics in the exception logging to see more about the actual files that are triggering the issue, though that might not be too valuable.
At a minimum, we could change it from an error that triggers the "big" alarm, into something that just logs a warning.
Subscribing Chris to this.
I'd say one thing you could do to try and recreate it is, upload a Word file on that instance and see if it gets indexed and see if the error gets triggered. My guess is, this is a "Heisenbug", one that we won't be able to recreate. We could perhaps put a little more forensics in the exception logging to see more about the actual files that are triggering the issue, though that might not be too valuable.
At a minimum, we could change it from an error that triggers the "big" alarm, into something that just logs a warning.