Toby Dickenson wrote:

...

I think Ive seen this before, when Product initialization modifies a persistent object, then causes an exception (ImportError, or whatever). You see these ConflictErrors if a subsequent Product initialization also modifies a persistent object.

Ah, okay...

So, how do you find out what the error causing the problem is? (the ImportError in your example)

The only things showing up in the stupid log file are the ConflictErrors :-(

Ive only seen it after a previous product-initialization failure traceback. sorry....