Hi, 

An error occurred while installing the module. Do you think I'll be able to use it while importing 500 records? Or, should I use a more recent version of DNN? Should I  remove the module and the files that were installed?  Thanks.

 

This is the message that the module installer provided me:

 

Warning: The table 'DataSprings_UserImport' has been created but its maximum row size (21063) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes. Warning: The table 'DataSprings_UserImport' has been created but its maximum row size (21059) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes. Warning: The table 'DataSprings_UserImport' has been created but its maximum row size (21059) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes. Warning: The table 'DataSprings_UserImport' has been created but its maximum row size (21077) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes. 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.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) /************************************************************/ /***** SQLDataProvider *****/ /***** UserImport *****/ /***** *****/ /***** Note: To manually execute this script you must *****/ /***** perform a search and replace operation *****/ /***** for dbo. and *****/ /***** *****/ /************************************************************/ Alter Table dbo.[DataSprings_UserImport] Add UseStaticFile Int Alter Table dbo.[DataSprings_UserImport] Add StaticFile nvarchar(2000) Alter Table dbo.[DataSprings_UserImport] Add UseGlobalFilter int Alter Table dbo.[DataSprings_UserImport] Add GlobalFilterField nvarchar(300) Alter Table dbo.[DataSprings_UserImport] Add GlobalFilterValue nvarchar(1000) Alter Table dbo.[DataSprings_UserImport] Add UseRecurring int Alter Table dbo.[DataSprings_UserImport] Alter Column [FileName] nvarchar(2000) Null Alter Table dbo.[DataSprings_UserImport] Alter Column [DNNFields] nvarchar(4000) Null Alter Table dbo.[DataSprings_UserImport] Alter Column [DynamicEvents] text Null set ANSI_NULLS ON set QUOTED_IDENTIFIER ON

 

Eric,

Well this is actually just a SQL Warning and not actually an error. When we increased this column size (which was necessary for a few reasons but mostly for implementations that had a large number of events) this generated a warning that the entire table could possibly exceed the allowed limit. More than likely (we have never had an incident) where this warning actually caused a problem.

Also, not all instances of SQL Server will receive this warning. Can you tell me if you are running on SQL Server Express, SQL Server 2005, or SQL Server 2005?

-Chad