PreparePageValues: ERROR#9, Index was outside the bounds of the array.

[Daniel Petroff]

I have never seen this before today... The error occurs on one page (tried several pages on same and different level of navigation and they are all fine). Other instances of the template are working fine. The mention of "Index" makes me think NavMan is involved. I cleared navigation cache (didn't help), but I am reluctant to Reset Navigation Structure unless I absolutely have to since it will mean having to manually sort the whole navigation index afterwards as it will be reset to alphabetical order.

Anyway those are the two quick fix options I could think of...

Any ideas on what this cold be and how to fix it? as I just cannot think of what could be the cause. According to the editor who reported it - it happened after some day to day content editing activity and everything looks fine from what I can see...

Thanks for your help all!

Daniel

[Jian Huang]

Hi Daniel,

I think I had seen this error before, but it was back in the days before rendertag.  I think I had 2 lists inside a list blockmark, or 2 anchors inside a dynamic blockmark.

Best way to find out which code caused the issue is start removing 50% of the code at once.

Best of luck,

-Jian

[Daniel Petroff]

Thanks Jian. We restarted the server a minute ago and it seems to have cleared the error. But if it occurs again, I will keep that in mind!

Daniel

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-use...@googlegroups.com.
To post to this group, send email to reddot-c...@googlegroups.com.
Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Christoph Straßer]

"Index was outside the bounds of the array." is a generic .NET - error. Not specific to OTWSM.
Example: If an array contains 5 entries and programm code tries to access position 9 .NET raises this error.
In an ideal world such error´s should not happen, if programmers write only perfect code.

A server-restart should be a appropriate solution if it occur´s rarely. If it happens often it will help to track down the root cause and try to open a ticket/defect at OT.
In our enviroment (11.0 SP1 HF1 (November to March), 11.0 SP1 HF6 (March until today) we did not need to restart our server a single time during the last half year.

[Daniel Petroff]

Hi Sara

Restarting the server seem to have helped. We are on CMS 11

Daniel

Sent from my iPhone

On 13 May 2013, at 11:33, Scodazzi <coda...@gmail.com> wrote:

Hi Daniel,
can i ask you wich version of the WSM you are using?

Sara

--

[Scodazzi]

Hi Daniel,
just for information...

I had the same problem on a 9.0 version and opened a ticket to the OT Support.

After checking on active template code the Support confirmed that it wasn't due to a code error but it was due to a product defect fixed in an upgraded version.

But if you are detecting it in 11 version i guess it's not fixed yet!

Thanks.
Sara.

[Daniel Petroff]

Yeah we restarted the server and it solved the issue. :)

On Tue, May 21, 2013 at 2:10 PM, Neil Fegen <n.fe...@gmail.com> wrote:

Hi

I've seen this on a page where this is an anchor link to a page in another project.

Turns out the RedDot ProcessServer service had stopped running on the application server - once we restarted it, the error disappeared.

Worth checking if you have server access.

Neil

--