Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.

Insufficient user rights when upgrading to 3.0.1 from 2.2.6


I've seen several posts on this topic, but they usually don't have a solution that works for me.

I upgraded from 2.2.2 to 2.2.6 and then upgraded to 3.0.1.
The upgrade to 2.2.6 went smoothly and everyone was still able to work.
The upgrade to 3.0.1 was a disaster and I had to back out the upgrade.

Here's the problem.

The upgrade scripts run with out any issues and I followed the directions to the letter.
When my users reassign an issue back to the original poster, they get:

Insufficient user rights
and the issue is untouchable from that point on.

I had them try assigning it back to the sender and themselves and that worked fine -- unfortunately, this is an unacceptable solution (or even workaround) for our company.

The only message in the System Log is:
SendToHome() invoked                         02/06/2008 11:23:22

Which doesn't really mean anything to me.
I looked at the 3.0.1 patch -- it doesn't have anything different from the 3.0.1 scripts, so that doesn't work for me.

Please, any help would be wonderful!!!

· 1
Replies (1)
not helpful

I presume the user is (reporter) is in the assigned to box, correct?

Can you check if it hase the assignable to issues right?

What do you mean by "the issue is untouchable"?

Also, do the users click edit and then sent to the home page or click update and then sent to the home page?


Saar Cohen
· 5000
Saar Cohen