That might be a bug coming from eMule. IIRC, on eMule, a file with an ampersand character was never shown, but instead, it made the next character become underlined (as if it was a GUI item)... allthough aMule's bug is much more critical as you show it :-S
If the file is never into Incoming, you can be sure it is on Temp (with it's old xxx.part name). Anyway, as of what I read in the log you paste, it seems like it cannot open it once it's been copied, so, please use the console to cd into ~/.aMule/Incoming and check if it's there and with which name. It could happen that it's the Preview code that has the wrong code and that's why it cannot open the file, allthough it's there with the right name...
Please report. Serious bug
Greetings!