Crowd sync sql error: CROWD207.SYS_C0020403 after upgrade

After upgrading Crowd 2.0.7 to 2.5.1 yesterday I've seen a SQL error a couple times in atlassian-crowd.log. See attached stack trace. (actually seen it twice, ~24hrs between.)

Looks like a uniqe constraint violation in table cwd_token.

Can this be fixed easily in a nice way?

(Or hacker-style: Stop crowd & clear table?)

(crowdStack.txt)

Otherwise Crowd seems to be working fine after the upgrade. But it would be nice to not have this error in logfile.

1 answer

1 accepted

I would suggest the SQL approach, unless you can find the row in question that is causing the violation, and removing just that record.

Removing all tokens would logout all sessions for all users + applications currently using Crowd for authentication.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Feb 27, 2018 in Crowd

The Crowd team is looking for feedback on Server & Data Center customers' identity strategies!

Do you own more than one Server or Data Center product? Do you have challenges provisioning users across your Atlassian products? Are you spending a lot of time integrating each Atlassian product wit...

1,219 views 6 14
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you