For the record, it's conceivable that the same error might have happened with Emplode. For instance, maybe the player is having disk trouble, or it had that known Beta-11 bug where it didn't reboot after a synch, and the database got temporarily messed up.

This might not be necessarily Jemplode's fault, but the first thing is to check what version of Jemplode he's running (my initial question was never answered).