Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,464,367
Community Members
 
Community Events
176
Community Groups

Crowd sync sql error: CROWD207.SYS_C0020403 after upgrade

David Forsman
David Forsman Oct 17, 2012

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.

Answer
Watch
Like Be the first to like this
253 views

1 answer

1 accepted

1 vote
Answer accepted
JustinK
JustinK Rising Star Oct 18, 2012

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.

Reply

Suggest an answer

Log in or Sign up to answer
Crowd
Crowd
TAGS

Atlassian Community Events

See all events