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.




(Gemini v2.0.3) - Correct project id reported on issue table, but incorrectedly reported on issuehis

web-app

I am looking at my production gemini database and seeing the following problem which i think is the "show stopper" error for my upgrade (stuck at step1 script) to Gemini V3.0.4

Production database (v2.0.3)
Issue table, issueid = 3267, projid=11  (this is valid projid)
Issuehistory table, issueid=3267, projid=-1 (very invalid projid)

Question: I don't know how -1 appears on issuehistory table while the same issueid appears on Issue table with correct/valid (but different) projid.  Can anyone tell me how this -1 error appear?  I know user cannot do this on the Gemini website.  Also, I don't believe any admin created this -1 on the database.
kha
· 1 		kha
Monday, December 1, 2008, 9:13:04 PM
Replies (1)
helpful
0
not helpful

This might happen if the session has expired or timed out.

I suggest updating these records to the valid project id.
Saar Cohen
· 5000 		Saar Cohen
Monday, December 1, 2008, 10:53:09 PM