Hey avidan,
I checked the code and unfortunately we are not printing the real SQL exception that we got from the DB while inserting a new row in the jiveRoster table. I’m going to change the code so that we can see the real error. As delimiter mentioned this could be related to a bad value in the jiveID table. That could happen if you played with your DB directly. Anyway, I would recommend using a DB tool to capture the SQL statement being executed and then execute it manually to see the real SQL exception. For 3.4.0 I will print the SQL exception so it’s easier to know what’s going on.
Thanks,
– Gato