Seems like you have project version attribute values with not attributesI suggest excluding these from the upgrdae by adding an SQL in statment (step 1.sql):

DELETE FROM geminiprojectversionattributevalues
SET IDENTITYINSERT geminiprojectversionattributevalues ON
INSERT INTO geminiprojectversionattributevalues (attributevalueid, attributeid, projectid, versionid, attributevalue)
 SELECT attributevalueid, attributeid, projid, verid, attributevalue FROM projectversionattributevalues WHERE attributeid IN (SELECT attributeid FROM geminiprojectversionattributes)
SET IDENTITYINSERT gemini_projectversionattributevalues OFF

thank you that did the trick...one more questions:
in CounterSoftGeminiv311 there is one last db upgrade file Upgradev3-1.sql, do we execute this...The gemini documentation does not mention this file.
I'm currently doing this in my test enviorment...I executed Upgradev3-1.sql but there are a few errors that display:

Msg 2705, Level 16, State 4, Line 5
Column names in each table must be unique. Column name 'parentcomponentid' in table 'geminicomponents' is specified more than once.
Msg 3726, Level 16, State 1, Line 5
Could not drop object 'geminiprojectlabels' because it is referenced by a FOREIGN KEY constraint.
Msg 2714, Level 16, State 6, Line 2
There is already an object named 'geminiprojectlabels' in the database.
Msg 2705, Level 16, State 4, Line 2
Column names in each table must be unique. Column name 'projectlabelid' in table 'geminiprojects' is specified more than once.
Msg 2705, Level 16, State 4, Line 5
Column names in each table must be unique. Column name 'apikey' in table 'gemini_users' is specified more than once.


Thanks again for you time.

garifo

You do not need to run this script. Please remember to run createviews and createprocs at the end of the upgrade.

thank you..
Yes I created them.

thank you for your help.