Hi,

We are experiencing a situation where one posting on the site can
no-longer be updated.  The rest of the site functions normally but any
attempt to 'Save' this posting after a change (even without actually
changing anything) causes the ASP.NET worker process to consume 100&
CPU on the server for several minutes, eventually resulting in a
complete collapse of the MCMS site or an ODBC error being returned
through the Console to the web user.

Any ideas???

Thanks,

Chandy

[ Post a follow-up to this message ]

Hi Chandy,

does this only happen to one page based of the same template?
Did you test with a different page with the same template?
Just to double check if the template code causes this.

If it only happens with one posting based on this template, please double
check if the template contains content dependend logic - e.g. if content in
placeholder 1 is something then do this.

Compare if the same code is executed in the working scenario.
If yes, you should open a support call to get this analyzed in more detail
to check if this is being caused by a coding problem, a bug or a database
inconsistancy.

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Chandy" <chandy@totalise.co.uk> wrote in message
news:5af0375a.0402260923.59615f80@posting.google.com...
> Hi,
>
> We are experiencing a situation where one posting on the site can
> no-longer be updated.  The rest of the site functions normally but any
> attempt to 'Save' this posting after a change (even without actually
> changing anything) causes the ASP.NET worker process to consume 100&
> CPU on the server for several minutes, eventually resulting in a
> complete collapse of the MCMS site or an ODBC error being returned
> through the Console to the web user.
>
> Any ideas???
>
> Thanks,
>
> Chandy

[ Post a follow-up to this message ]