Hi everyone,
I'm using 5.2.0 Community edition and when ever I go to re-index Content using the Host>Search Admin page it will sit there and think for a few mintues then eventually throw an error. In IE of course it just sits and thinks and then I look in the event viewer and find the actual error. Everything else actually shows the error on screen.
Here is the error:
AssemblyVersion: 5.2.0
PortalID: 0
PortalName: xxxxxxxxxx Intranet
UserID: 3
UserName: xxxxxxxxxx
ActiveTabID: 29
ActiveTabName: Search Admin
RawURL: /tabid/29/portalid/0/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: https://xxxxxxxxxxxx.com/tabid/29/por...
UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; Tablet PC 2.0; .NET4.0C; .NET4.0E)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 1b8363a5-1a8a-4557-a546-16aca6ebafda
InnerException: Thread was being aborted.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: .SNINativeMethodWrapper.SNIPacketGetConnection
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being aborted.at SNINativeMethodWrapper.SNIPacketGetConnection(IntPtr packet)at System.Data.SqlClient.TdsParserStateObject.ProcessSniPacket(IntPtr packet, UInt32 error)at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()at System.Data.SqlClient.TdsParserStateObject.ReadByte()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 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues)at DotNetNuke.Data.SqlDataProvider.DeleteSearchItemWords(Int32 SearchItemId)at DotNetNuke.Services.Search.SearchDataStore.StoreSearchItems(SearchItemInfoCollection SearchItems)
Does anyone know why this happens? I'm assuming that it does actually complete the indexing because I can search and pick up new items. But I'd love to have it get rid of this error just for usability sake.
Thanks