Error 500 when bulk changing issues

[Nikolai Steffel]

Hello!

During the Bulk Change operation inside a project we receive an error... to reproduce it we have to tick several non-epic objects, select "Move Issues" and then move for examples Bugs to Issues etc, once you click on it Error 500 with the following message appears

"com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=10005]"

We tried following this guide as it seems to be the very same issue we have
"https://confluence.atlassian.com/jirakb/several-actions-such-as-issue-ranking-move-export-are-failing-779159169.html"

The guide worked fine until after the Diagnosis, naturally we didn't find any endmarkers for the rank ID 10005 (or any line at all for this ID actually) so we tried to execute the mentioned resolution

mysql> insert into AO_60DB71_LEXORANK values (DEFAULT,10005,7,-9223372036854775808,NULL,NULL,'0|000000:',0);
ERROR 1062 (23000): Duplicate entry '7' for key 'PRIMARY'

As you see we receive a duplicate error for this line, unfortunately the knowledgebase article doesn't offer a solution for this as nowhere is the required information which ID one should try instead

Thanks in Advance

[Nikolai Steffel · Accepted solution]

Alright, Branden McElveen's suggestion didn't provide a solution for me, but it led me on the right track... as it turns out it seems like the LeoxRank system has failed to properly initialize and thus pretty much all the initial markers were missing, the workaround suggested in the following bug report helped and now everything works just fine:

https://jira.atlassian.com/browse/JSWSERVER-10975

[somethingblue]

Thanks for circling back and letting us know what the resolution was.  I'm happy to hear all is well!

Cheers,

Branden

[somethingblue]

Hi Nikolai,

At that point you can skip it and go to the next query.  If you still get those errors:

1. delete from AO_60DB71_LEXORANK
2. Go back through Several actions such as issue ranking, move, export are failing
3. Re-balance JIRA under System Administration > System > Advanced > LexoRank Management

Cheers,

Branden

[Nikolai Steffel]

Sadly none of the adviced solutions worked, by the way running the integritiy check on the LexoRank management seems to return failures on all field ID's except 11300