Hi,

 

Suddenly the log stopped working on our demonstration copy of CuteChat. The error log has a number of messages like the one shown below.

 

Can you let me know what has happened?

 

Thanks

 

Gerard

 

System.Data.SqlClient.SqlException: String or binary data would be truncated.
The statement has been terminated.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.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.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.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at CuteChat.SqlServerDataProvider.LogMessage(ChatPlace place, ChatIdentity sender, ChatIdentity target, Boolean whisper, String text, String html)
   at CuteChat.ChatDataManager.b.Process(IChatDataProvider provider)
   at CuteChat.ChatDataManager.Maintain()

The length of the nvarchar columns of table CuteChat4_LogMessage is too small.

 

So , please modify it to more using SqlServer Enterprise Manager.

 

Regards , Terry .

Gerard,

 

We've updated the SQL Script file to fix this issue. You can download the control again or fix it manually using enterprise manager.

 

Keep me posted

Hi Adam,

 

Thanks for updating the download. We updated the table using SQL Server Management Studio and that cured the problem.

 

 

Gerard