Horrible error message with missing plugin

[Risord]

I tried to run sample file (test.dita) from lightweight project: https://tools.oasis-open.org/version-control/svn/dita/trunk/subcommittees/LightweightDITA/org.oasis.lwdita/samples/

I wasn't installed lightweight dita plugin correctly so it wasn't working but error message was very miss leading:

DOTA069F: Input file '[FILENAME]' cannot be located or read. Ensure that file was specified properly and that you have permission to access it.

And since problem from input file perspective is content related error message is clearly wrong (and caused me to debug filesystem / permissions instead of plugin).

[jelovirt]

Which DITA-OT version? How did you run DITA-OT?

[Risord]

Version 2.2.2 (most recent one from http://www.dita-ot.org/download). Run: "dita -i test.dita -f pdf" in sample folder. After installing plugin correctly it works fine.

[jelovirt]

So you mean in the error message [FILENAME] part is a placeholder for the path, not exactly that string?

[Risord]

Yes its place holder.

I just replicated this once more. There is direct copypaste from my console. Compilation works, unistall plugin, compilation give this not so good error.

C:\samples>dita -i test.dita -f pdf

C:\samples>dita -uninstall org.oasis.lwdita

C:\samples>dita -i test.dita -f pdf
Error: Failed to run pipeline: [DOTA069F][FATAL] Input file 'file:/C:/samples/test.dita' cannot be located or read. Ensure that file was specified properly and that you have permission to access it.

[robander]

I think it's more correct to say "cannot be located or parsed" - this message will show up when the file cannot be parsed because the DTD is not properly integrated. As I understand it, that was the case here. The problem is that I've run into a lot of people who still wouldn't understand what's wrong if we say "parsed" instead of "read". Maybe we should also change the second part of this to "Ensure that the file was specified properly, and that the document type is supported by the toolkit or a toolkit plugin." I have nothing to back this up, but I'd bet missing / invalid plugins result in this message more often than a lack of permission to read the file.

[stale]

This issue has been automatically marked as stale because it has not been updated recently. It will be closed soon if no further activity occurs. Thank you for your contributions.

[raducoravu]

At some point I think @robander changed the error message and added to it a "Ensure that grammar files for this document type are referenced and installed properly."

[robander]

Indeed - fixed recently in 3.2 with #3124

I marked that one at the time as fixing another long-open defect - appears to be another case where we didn't realize we had a duplicate report of an issue deep in the backlog.