Probably just a bug in Jemplode. Mike will see this thread soon and maybe ask you for a trace log to locate the problem. Not sure how to get a trace log in recent versions of Jemplode, so you'll have to let him guide you through it.