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 V3.6 Upgrade SQL script failures

web-app

I just upgraded from v3.1.2 and ran the 3 required upgrade scripts(Upgradev-35, Createviews and Create_Procs). The two Create scripts generated errors. Create Procs generated:

Msg 207, Level 16, State 1, Procedure geminigetcreateissuelookups, Line 27 Invalid column name 'parentversionid'. Msg 207, Level 16, State 1, Procedure geminigetcreateissuelookups, Line 31 Invalid column name 'parentversionid'. Msg 207, Level 16, State 1, Procedure geminigeteditissuelookups, Line 13 Invalid column name 'parentversionid'. Msg 207, Level 16, State 1, Procedure geminigetissuefilterlookups, Line 36 Invalid column name 'parentversionid'. Msg 207, Level 16, State 1, Procedure gemini_getissuefilterlookups, Line 58 Invalid column name 'parentversionid'.

And Create Views Generated:

Msg 207, Level 16, State 1, Procedure geminiissuesview, Line 25 Invalid column name 'originatortype'. Msg 207, Level 16, State 1, Procedure geminiissuesview, Line 26 Invalid column name 'originatordata'. Msg 207, Level 16, State 1, Procedure geminiissuesview, Line 27 Invalid column name 'originatorreply'. Msg 207, Level 16, State 1, Procedure geminiissuesview, Line 28 Invalid column name 'originatorprocessed'.

When I try to login I get:

Gemini Application Error

An application error has occured - please advise the Gemini administrator within your organization.

View System Log

grant.gardner
· 1
grant.gardner
Replies (6)
helpful
0
not helpful

You need to run upgrade 3.6 before the 2 create scripts.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

So, 3.5 then 3.6 and then the two create scripts?


grant.gardner
· 1
grant.gardner
helpful
0
not helpful

yes. The create scripts are always at the end.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I understand that, but the upgrade instuctions say to run script Upgrade_v3-5 and then the two scripts for users that are currently running version 3.1.x. Did not know I had to also run v3.6 script.


grant.gardner
· 1
grant.gardner
helpful
0
not helpful

Re-ran the scripts and was successful at upgrading the database. I've been poking around in the new version and it appears that comments are not visible. Old items that have a comment show that a comment is available but it is not visible. I created a comment and it also behaves the same way, it shows Comments(1) but does not show the content.


grant.gardner
· 1
grant.gardner
helpful
0
not helpful

Do you get any javascript errors?


Saar Cohen
· 5000
Saar Cohen