This seems like an SQL server permissions issue.

Please make sure that the Gemini user has permissions to insert to the issuecomments table.

Thank you for the quick reply!

Unfortunately that didn't fix the issue. User was already had those permissions (was database owner); tried creating new SQL user with full rights to all tables but same issue.

Could it be a permission that needs to be set in Gemini?

This can not be a Gemini security issue, especially if you are on 2.x.

Can you try logging in to SQL using the same credentials as Gemini and try to insert a record to the issuecomments table?

Logged in via SQL Management Studio with the Gemini user credentials. Was able to manually insert row without issue so I don't believe it's a permission issue...not sure what else to try

Can you please try and run SQL profiler to see where and when we get the permission issue?

It might be a stored procedure access issue.

Thanks. This was the last query ran before the error-

declare @p7 numeric(28,0)
set @p7=NULL
exec geminicreateissuecomment @issueid=20105,@projid=48,@note=N'cvxf',@userid=206,@isprivate=0,@isclosing=0,@commentid=@p7 output
select @p7

And then this query ran inserting error into errorlog table-

exec geminilogerror @errormessage='The user does not have permission to perform this action.',@stacktrace='   at CounterSoft.GeminiBiz.7cdfe764c33c38b0.0a66b07b4f5fba22(IssueCommentEN 732c0a0fe634473a)
   at Gemini.CreateIssComment.btnCreate_Click(Object sender, EventArgs e)',@otherinfo=''

It's also worth noting that the comment was written to the table. However error message still came up.

Ok, so the problem must be with the contents of the stored procedure.

If the comment record is created then the problem is updating the revised (date) on the issues table.

Can you try updating a record on the issue table (from SQL)?

Ok, tried creating an update manually and it showed up.

One interesting thing that may be connected - when trying to comment on issue from Gemini the comment is written and error comes up. However an email is NOT sent. When creating a new issue no errors come up and email is sent correctly.

Could the error Gemini is throwing be related to how it sends email for comments?

Not likely as the table used for alerts is the same. This is 100% an SQL permission issue.

Try using profiler and trace the SP.

Thanks everyone for the replies.

This issue is now fixed; turned out it was permissions after all on a custom trigger someone wrote. All is good now.

Glad all is well, thanks for the update.