Developer forum

Forum » Rapido » Error UrlHelper.ResetPageIndex failed

Error UrlHelper.ResetPageIndex failed

Cristina Santos
Reply

Hi,

Two or three times a day, we get this error:

Description:  UrlHelper.ResetPageIndex failed: From UrlHelper.CheckResetNeeded

Exception type: InvalidOperationException

The trace of the error is:

2021-05-20 15:32:58.326: UrlHelper.ResetPageIndex failed: From UrlHelper.CheckResetNeeded. System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
at Dynamicweb.Frontend.UrlHandling.UrlIndex.BuildIndex()
at Dynamicweb.Frontend.UrlHandling.UrlIndex.BuildIndexes()
at Dynamicweb.Frontend.UrlHandling.UrlHelper.ResetPageIndex(String fromWhere)
2021-05-20 15:32:58.341: Request headers: [   "Connection",   "Accept",   "Accept-Encoding",   "Accept-Language",   "Host",   "Referer",   "User-Agent" ]
2021-05-20 15:32:58.341: Request item keys: [   "alternateUrlKey",   "Dynamicweb.Environment.Web",   "owin.Environment",   "ExecutionTableMapper",   "MS_HttpRequestMessage" ]
2021-05-20 15:32:58.341: Request form: []

Any help?

Regards

Cris


Replies

 
Nicolai Pedersen
Reply

Hi Christina

We will look into that. Expect this to be fixed in next Dynamicweb nuget package.

BR Nicolai

 
Cristina Santos
Reply

Thank you very much Nicolai.

And can you tell me if this error can affect the speed of the page?

Does it affect the user?

I do not know exactly when it occurs or what it consists of ...

I would appreciate any explanation ...

Thank you very much!

Regards,

Cristina

 
Nicolai Pedersen
Reply

There is no performance problems.

This comes when a change to a page has been made that is detected to affect one or more urls. That will trigger a url recalculation (which is fast). Problem here is that 2 recalculations can be triggered at once, causing this. It happens rarely.

BR Nicolai

 
Cristina Santos
Reply

That is good news.

We wait to be fixed in next Dynamicweb nuget package.

Regards,

Cristina

 

You must be logged in to post in the forum