|
Home > Archive > Microsoft Content Management Server > October 2006 > CMS Page Corruption
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CMS Page Corruption
|
|
|
| System: MCMS2002, SP2
We currently have a problem on a client CMS system that results in a
strange corruption of our pages. The symptoms are this:
1) When navigating between pages in author mode with the CMS console
open, the destination page is rendered correctly but a fragment of the
previous page is appended after the closing </html> tag;
2) Because the previous page contains a console itself, two consoles
are rendered on the destination page.
At the end of the generated code for the destination page, we are
seeing a code something like this:
....
</form></body></html>oYW5uZWx0cmVlOz4+Ac/hwgL4pM93QJAaTv/2Wr7/nIY=" />
<table height="90%" width="100%" border="0" cellspacing="0"
cellpadding="0">
....
You can see that the the appended page fragment has appeared from
somewhere in the viewstate section. The appended fragment always then
carries onto the end of the previous page's html.
>From my investigations I have determined the following:
1) The error only occurs in author mode, when the console is open. If
pages are navigated with the console closed, the error does not occur.
However, it occurs when doing "save page" operations since the console
is open at this time;
2) The problem only happens with postings in a particular channel on
the CMS system. The problem is not limited to one particular template
type, any posting in this channel seems affected;
3) Clearing the CMS node cache does not help;
4) Rebooting the box does not help;
5) The problem only occurs on our production environment (2 public
facing webservers, 1 internal authoring server);
6) From examining the trace output, it appears that the appended page
is not being regenerated when the error occurs. It seems to be being
retrieved from a cache somewhere, though I can't imagine where;
7) The problem is not intermitent and can be reproduced.
Can you offer any suggestions?
Thanks in advance,
Dave
| |
| Stefan [MSFT] 2006-10-24, 1:15 pm |
| Hi Dave,
this should not happen.
Sounds more like an ASP.NET caching issue or a load balancer issue.
I have seen something like this in the past with a Big-IP load balancer
which did not have the latest patches installed.
Please check this.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Dave" <dave.tansley@gmail.com> wrote in message
news:1161697950.319063.107670@k70g2000cwa.googlegroups.com...
> System: MCMS2002, SP2
>
> We currently have a problem on a client CMS system that results in a
> strange corruption of our pages. The symptoms are this:
>
> 1) When navigating between pages in author mode with the CMS console
> open, the destination page is rendered correctly but a fragment of the
> previous page is appended after the closing </html> tag;
> 2) Because the previous page contains a console itself, two consoles
> are rendered on the destination page.
>
> At the end of the generated code for the destination page, we are
> seeing a code something like this:
>
> ...
> </form></body></html>oYW5uZWx0cmVlOz4+Ac/hwgL4pM93QJAaTv/2Wr7/nIY=" />
>
> <table height="90%" width="100%" border="0" cellspacing="0"
> cellpadding="0">
> ...
>
> You can see that the the appended page fragment has appeared from
> somewhere in the viewstate section. The appended fragment always then
> carries onto the end of the previous page's html.
>
>
> 1) The error only occurs in author mode, when the console is open. If
> pages are navigated with the console closed, the error does not occur.
> However, it occurs when doing "save page" operations since the console
> is open at this time;
> 2) The problem only happens with postings in a particular channel on
> the CMS system. The problem is not limited to one particular template
> type, any posting in this channel seems affected;
> 3) Clearing the CMS node cache does not help;
> 4) Rebooting the box does not help;
> 5) The problem only occurs on our production environment (2 public
> facing webservers, 1 internal authoring server);
> 6) From examining the trace output, it appears that the appended page
> is not being regenerated when the error occurs. It seems to be being
> retrieved from a cache somewhere, though I can't imagine where;
> 7) The problem is not intermitent and can be reproduced.
>
> Can you offer any suggestions?
>
> Thanks in advance,
>
> Dave
>
|
|
|
|
|