Developer forum

Forum » Development » Updating index sometimes gives this error

Updating index sometimes gives this error

Martin Nielsen
Reply

Hi DW,

 

We have a customer that makes tons of changes to their products, amd therefore run a partial update multiple times a day.

 

Problems is that they sometimes get this error:

------

 

Server Error in '/' Application.


Destination array was not long enough. Check destIndex and length, and the array's lower bounds.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentException: Destination array was not long enough. Check destIndex and length, and the array's lower bounds.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace:

 

[ArgumentException: Destination array was not long enough. Check destIndex and length, and the array's lower bounds.]

   System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable) +0

   System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length) +26

   System.Diagnostics.EventLogEntryCollection.System.Collections.ICollection.CopyTo(Array array, Int32 index) +48

   Dynamicweb.Extensibility.Searching.EventLogProvider.GetEntries(Int32 max) +215

   Dynamicweb.Admin.Manage.IsLastUpdateSucceeded() +225

   Dynamicweb.Admin.Manage.FillInformationTable() +1143

   Dynamicweb.Admin.Manage.LoadDetails() +19

   System.Web.UI.Control.LoadRecursive() +71

   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3064

------

 

Any idea what might cause this behaviour?

 

// Martin

 


Replies

 
Pavel Volgarev
Reply
This post has been marked as an answer

Hi Martin,

 

Thanks for the information. Looks like a bug, I will investigate on this. But it shouldn't affect the update process itself (you can see that by looking at the call stack - it's the management UI that breaks).

 

-- Pavel

Votes for this answer: 1

 

You must be logged in to post in the forum