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.




Search over all issues crashes

usage
database

Hello there, I get an exception from the database when doing a full text search. (See attachment)

I can leave the search field blank - then I do receive results. I can enter an Issue ID - then I do receive results.

But I may not enter a text string, then I get the error page.

Unfortunately, I can not identify the original source (there is no "lower" in the script) in order to figure out if this is perhaps a configuration issues.

Please help.

Heiko

[ message.htm ]
Heiko Scharnberg
· 125 		Heiko Scharnberg
Thursday, August 11, 2011, 11:37:05 AM
Replies (9)
helpful
0
not helpful

Which version of SQL server are you running? It seems like 2000, which is no longer supported.
Mark Wing
· 9108 		Mark Wing
Thursday, August 11, 2011, 11:43:49 AM
helpful
0
not helpful

No, it's a SQLExpress. I migrated the database from SQLServer2000 to 2008 SQLExpress during the 4.1 upgrade.
Heiko Scharnberg
· 125 		Heiko Scharnberg
Thursday, August 11, 2011, 11:51:43 AM
helpful
0
not helpful

Ok, open sql management studio and expand the databases folder. Right click on the Gemini database and select properties. Now click on the options page in the properties window. Change the compatibility level to SQL 2008 and click ok. That should do the trick.
Mark Wing
· 9108 		Mark Wing
Thursday, August 11, 2011, 11:56:33 AM
helpful
0
not helpful

Changed the compatibility level. Same behaviour still.
Heiko Scharnberg
· 125 		Heiko Scharnberg
Thursday, August 11, 2011, 12:14:34 PM
helpful
0
not helpful

Table: dbo.gemini.issues Field: longdesc has datatype: ntext

possibly more of these. should I change to ... what ?

··· Change to nvarchar(max)Mark WingThursday, August 11, 2011, 12:17:44 PM
Heiko Scharnberg
· 125 		Heiko Scharnberg
Thursday, August 11, 2011, 12:16:26 PM
helpful
0
not helpful

How did you upgrade to 4.1? did you change the scripts from nvarchar(max) to ntext?
Mark Wing
· 9108 		Mark Wing
Thursday, August 11, 2011, 12:17:07 PM
helpful
0
not helpful

Can't recall the details I surely tried w/ SQL2000 first, then the scripts did not run. So i tried to alter the scripts first but then decided to upgrade the database.

I believe I DID recover the original scripts for use after the upgrade but who knows.

So I figure I just replace ntext with nvarchar(max) wherever I see one?

tnx!
Heiko Scharnberg
· 125 		Heiko Scharnberg
Thursday, August 11, 2011, 12:25:21 PM
helpful
0
not helpful
ANSWER

Yes, ntext becomes nvarchar(max). There are quite a few of them but the main ones to change are on the geminiissues and geminicustomfielddata tables.
Mark Wing
· 9108 		Mark Wing
Thursday, August 11, 2011, 12:29:24 PM
helpful
0
not helpful

With the DB being in a sort of mixed migration state, I only found three.

The behaviour is back to normal now. Thanks for your support.
Heiko Scharnberg
· 125 		Heiko Scharnberg
Thursday, August 11, 2011, 12:48:58 PM