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.




Restore project created in ver 3.7 into ver 4.0 creates an error

projects
custom-fields
database

I recently upgraded to ver 4.0 but when I tried to restore a project ceated in ver 3.7 into the ver 4.0. The purpose of the restore was to avoid building the project from scatch. I get the error below on the system log. I realized that ver 4.0 creates a new column "listlimiter" that does not exist in ver 3.7 under custom field definitions.

Samwel


Cannot insert the value NULL into column 'listlimiter', table 'ATTXCC.dbo.geminicustomfielddefinitions'; column does not allow nulls. INSERT fails. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.getMetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader() at NHibernate.AdoNet.AbstractBatcher.ExecuteReader(IDbCommand cmd) at NHibernate.Id.IdentityGenerator.InsertSelectDelegate.ExecuteAndExtract(IDbCommand insert, ISessionImplementor session) at NHibernate.Id.Insert.AbstractReturningDelegate.PerformInsert(SqlCommandInfo insertSQL, ISessionImplementor session, IBinder binder)

User15255
· 1
User15255
Replies (3)
helpful
0
not helpful
··· The workaround is to allow nulls for that column in SQL and update it to empty string afterwards.Mark WingWednesday, April 27, 2011, 4:48:01 PM

Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Is this a bug that will be addressed in ver 4.5 or will the projects have to created from scratch always?

Samwel


User15255
· 1
User15255
helpful
0
not helpful

Yes, it will be fixed in 4.5 No need to re-create.


Mark Wing
· 9108
Mark Wing