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.




migrating database to 3.0 get the following errors

web-app

My Gemini version: Gemini 2.2.6   updagrading to
When executing Upgradev3-0-Step1.sql I get the following errors:

Msg 547, Level 16, State 0, Line 251
The INSERT statement conflicted with the FOREIGN KEY constraint "gemini
projectversionattributevaluesattributeidfk". The conflict occurred in database "GeminiDB", table "dbo.geminiprojectversionattributes", column 'attributeid'.
The statement has been terminated.

and

(0 row(s) affected)
Msg 2601, Level 14, State 1, Line 328
Cannot insert duplicate key row in object 'dbo.gemini
watchissues' with unique index 'uindgeminiwatchissues_id'.
The statement has been terminated.

So when I log into the gemini application all the issues that were assigned are no longer assigned.  In addition, all the roadmap and change log is gone or atleast it does not display.  How to fix it?
I'm currently running it on my test database and I have tried it 3 times from scratch with the same results.

any help will is greatly appreciated.


garifo
· 1
garifo
Replies (3)
helpful
0
not helpful

Please check your projectversionattributevalues table, seems like it has some attribute id's that are not in the versionattribute table.

Your watcher issue, seems like you have some duplicates it there (issueid and userid), remove them.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I too have discovered the same issue with my projectversionattributevalues table.  It would seem that one of our staff has been deleting projectversionattributes (presumably via the web interface).  This seems to leave the projectversionattributevaluestable inconsistent.

From this I deduce that the web interface is allowing users to delete a project version attribute regardless of whether is has been used (is currently being referenced by the projectversionattributevalues table).  Is this a bug that has been fixed already?  I would like to think that such problems can't occur if people use the web interface (or other countersoft provided interface).


mintGem
· 1
mintGem
helpful
0
not helpful

Yes, it has been addressed in 3.0.x.


Mark Wing
· 9108
Mark Wing