 |
|
|
Joined: 8/31/2004
Posts: 54
|
|
|
We recently went through a DNN migration where we started a new website based on our then production site, did a bunch of work on the new site (skinning, content, etc.), then cutover to the new site. The process took about 3 months. Right before we cutover, we exported our user database from the old production website to the new website using the Bulk User Manager module, and that seemed to go ok. However, a lot of our users (over 2,000) are now getting login error messages, as follows:
A critical error has occurred.
StartIndex cannot be less than zero. Parameter name: startIndex
So, they cannot get logged in.
Furthermore, the users who can login, are unable to post to our forums (we use the DNN core forum module). They get the same error message above. Any ideas how we can troubleshoot this to get it fixed? TIA for any help!
|
| |
|
|
 | |
|
|
Joined: 8/31/2004
Posts: 54
|
|
|
Ok, to keep the thread updated, I have fixed the user login issue. Here is what I discovered. In our user export, I noticed a field called "AcceptTerms". It is a profile property, which we were requiring on the old site. For whatever reason, users that had their "AcceptTerms" value set to True, were not having any issues logging in. However, users that had a blank value in the AcceptTerms field were receiving this error message. I'm guessing something has changed in the framework or something is misaligned somehow. At any rate, all our users are now able to get logged in, which leaves us still with users inability to post to the forum. Users are still receiving that same error message and are unable to post to the forum... However, our host accounts can post no problem. Any ideas on this?
|
| |
|
|
| |
|
|
Joined: 8/31/2004
Posts: 54
|
|
|
Does anyone have any idea why a user would be getting this error message immediately after clicking on the "New Thread" link on the forum?
A critical error has occurred.
StartIndex cannot be less than zero. Parameter name: startIndex
This is even an Admin account.
The only users currently able to post in our forums are host accounts. Any assistance is greatly appreciated!
|
| |
|
|
| |
|
|
Joined: 8/31/2004
Posts: 54
|
|
|
To further elaborate and update this thread, I have just upgraded the forum module on the site from 4.4.3 to 4.5.3. I did receive an error message when installating, but the install seemed to get past it and successfully upgrade to 4.5.3. Additionally, it is worth noting that no user other than hosts can create a new thread, edit a thread or message, reply, etc. etc. Not even admins can perform the most basic functions as it pertains to posting on the forum. Any ideas?
Consequenty, here is the error I received when upgrading from 4.4.3 to 4.5.3:
| Info |
Start Sql execution: 04.05.00.SqlDataProvider file |
| Warning |
SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. 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) DECLARE @default_constraint_name SYSNAME, @sql NVARCHAR(3750) IF EXISTS ( SELECT name FROM dbo.sysobjects WHERE parent_obj = OBJECT_ID(N'dbo.Forum_EmailQueue_TaskEmails') AND type = 'D' AND id = ( SELECT cdefault FROM syscolumns WHERE name = N'DateAdded' ) ) BEGIN SELECT @default_constraint_name = name FROM dbo.sysobjects WHERE parent_obj = OBJECT_ID(N'dbo.Forum_EmailQueue_TaskEmails') AND type = 'D' AND id = ( SELECT cdefault FROM syscolumns WHERE name = N'DateAdded' ) SET @sql = N'ALTER TABLE dbo.Forum_EmailQueue_TaskEmails DROP Constraint ' + @default_constraint_name EXEC sp_executesql @sql END System.Data.SqlClient.SqlException: Column already has a DEFAULT bound to it. Could not create constraint. See previous errors. 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) ALTER TABLE dbo.Forum_EmailQueue_TaskEmails ADD CONSTRAINT DF_Forum_EmailQueue_TaskEmails_DateAdded DEFAULT (GETDATE()) FOR DateAdded |
|
| |
|
|
| |
|
|
Joined: 8/31/2004
Posts: 54
|
|
|
The saga continues. I have discovered this problem to be more widespread than just users not being able to post to the forum. My admin users cannot even edit any content on the site. So, if they go to a regular HTML module, then click on the Edit Content link, they get this error message:
A critical error has occurred.
StartIndex cannot be less than zero. Parameter name: startIndex
Any ideas what could be going on here?
|
| |
|
|
| |