Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to authenticate JIRA 5.0.2 with Crowd 2.4.1 after upgrade

We recently performed an upgrade from JIRA 4.1.2 and Crowd 2.0.7 to 5.0.2 and 2.4.1 respectively. After the upgrade, we are unable to authenticate users against Crowd and are receiving the following error in the Crowd logs:

org.hibernate.StaleStateException: Batch update returned unexpected row count from update 0 ; actual row count: 0; expected: 1

We also upgraded out Confluence from 3.3.3 to 4.1.7 and found a similar issue where it seemed that Confluence was holding onto an old stale state with the older version of Crowd. To resolve that issue, we reset the Confluence internal directory password for the admin account and went through the steps to re-establish a Crowd integration.

We didn't seem to have an admin account in our JIRA instance so we followed the steps in https://confluence.atlassian.com/display/JIRA050/Retrieving+the+JIRA+Administrator but that didn't seem to help us any and we still cannot login (locally nor crowd related). We've been looking through all of the knowledge base, documentation, submitted to the Ask Atlassian forums, but we're stumped at this point.

2 answers

1 accepted

0 votes
Answer accepted

it was actually a mispelling of the password in the crowd.properties. Pretty simple and stupid on my part. Thanks for helping.

Assuming you have a valid licence, I'd raise a support call with Atlassian? http://support.atlassian.com

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

300 views 9 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you