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.




Invalid object name 'gemini_components'

web-app

Hi,

after upgrading from version 3.04 to 3.11 i got this error:

- Invalid object name 'gemini_components'

- .Net SqlClient Data Provider

when i try to open a project - Startpage, roadmap or protocol.

With the Query Analyser the Gemini SQLAccount is able to open this table.

Whats wrong? During the update all SQL Update scripts where successfull without errors.

Thanks,

Michael

MTCP
· 1
MTCP
Replies (8)
helpful
0
not helpful

It seems that we fixed this error.

After the Update the Stored Procedure "gemini_getprojectsummarycomponents "

was gone. (Don't ask me why!).

We restored it from a test installation and now it works.

 

Best regards,

Michael


MTCP
· 1
MTCP
helpful
0
not helpful

I was getting the same error.  the user I am running these scripts under was not the db owner.  In the scripts, dbo is specified for a few of the stored procedures when being created

[geminigetissueupdatedata2]
[gemini
getlut1]
[gemini
getprojectsummarycomponents]
[gemini_getissueupdatedata]

These were created under the dbo account and I could not access them.  I removed the [dbo] and it created them like all the others.  This worked.


jruez
· 1
jruez
helpful
0
not helpful

so geminigetprojectsummarycomponents was not actually gone in mine, it was just listed as

dbo.gemini
getprojectsummarycomponents


jruez
· 1
jruez
helpful
0
not helpful

This depends on the sql user used to run the stored procedures.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

That is what I said in my first post

"the user I am running these scripts under was not the db owner"


jruez
· 1
jruez
helpful
0
not helpful

In the setup script I have - there are several SP's that are created as DBO.

It is 3.1.1 but not sure when this was downloaded, renaming them to not be dbo fixed my installation.


Simon@MailboxPro
· 1
Simon@MailboxPro
helpful
0
not helpful

How did you remove [dbo]?


galaxyking
· 1
galaxyking
helpful
0
not helpful

right click on the procedure, script it and change dbo to your new owner.


Saar Cohen
· 5000
Saar Cohen