There are several keys in the exf file beginning LC000334, which would suggest custom taxa, which is probably why our copy of Recorder has trouble with the file.

I created a rucksack containing all of the keys found in the exf, but this generated an exception when the rucksack is opened. If I remove the keys beginning LC000334 I can load the rucksack.

It seems that Recorder should handle this scenario more gracefully. Obviously we cannot handle the custom taxa unless we have them in our db, but Recorder should at least say what's going on and offer to either continue without the custom taxa, or abort the process.