I've been working with CMS for a while. Today I started getting the followin
g
error when try to create postings in my dev environment. My guess is that I
have something screwed up in my configuration but I have not been able to
find a solution. Any tips on what to look at would be greatly appreciate.

Error Details:
Invalid mode for update. The requested action modifies the state of an
object and can only be performed when the session is in the 'Update' mode.


By the way, I have read the Web Author FAQ on this error and I am not
putting templates in the root the directory. All our pages are one down from
root in a web app.

Thanks,
Mike

[ Post a follow-up to this message ]

I have determined that it is only an issue with pages that were created in
2003. When I create a new page in 2005 and create a new posting with it I do
not get the error.
Mike

"Mike" wrote:

> I've been working with CMS for a while. Today I started getting the follow
ing
> error when try to create postings in my dev environment. My guess is that 
I
> have something screwed up in my configuration but I have not been able to
> find a solution. Any tips on what to look at would be greatly appreciate.
>
> Error Details:
> Invalid mode for update. The requested action modifies the state of an
> object and can only be performed when the session is in the 'Update' mode.
>
>
> By the way, I have read the Web Author FAQ on this error and I am not
> putting templates in the root the directory. All our pages are one down fr
om
> root in a web app.
>
> Thanks,
> Mike
>

[ Post a follow-up to this message ]

Hi Mike,

there is either some code in your template or in the global.asax.cs which
tries to perform updates while the posting is not in update mode or there is
a custom ISAPI filter or httpmodule which modifies the incoming query string
parameters.

Cheers,
Stefan
"Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
message news:F6EFE9D6-3695-486F-9A70-437C37130D37@microsoft.com...[vbcol=seagreen]
>I have determined that it is only an issue with pages that were created in
> 2003. When I create a new page in 2005 and create a new posting with it I
> do
> not get the error.
> Mike
>
> "Mike" wrote:
> 

[ Post a follow-up to this message ]

Hi Stefan,

I have encountered the issue you are referring to in the past when we tried
to update a posting and we used the wrong context or were not in the right
mode. We are not doing that in this code. I have even tried stripping all th
e
controls out of the apsx and commenting out the all the cs code in the code
behind. I still got the problem. If the problem were in the global.asax,
wouldn't it still be an issue when I created a new page?

Is there a way to turn on tracing or debug in CMS? It would be great to be
able to get a more detailed error message or an exception with a stack trace
.

Thanks,
Mike

"Stefan Goßner [MSFT]" wrote:

> Hi Mike,
>
> there is either some code in your template or in the global.asax.cs which
> tries to perform updates while the posting is not in update mode or there 
is
> a custom ISAPI filter or httpmodule which modifies the incoming query stri
ng
> parameters.
>
> Cheers,
> Stefan
> "Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
> message news:F6EFE9D6-3695-486F-9A70-437C37130D37@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Mike,

you cannot trace this with MCMS methods.
You need to identify the line of code that causes the problem.
Is there a callstack that comes with the error?

Cheers,
Stefan

"Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
message news:F1C6A774-F11B-4D3C-AA66-DE7D023F5655@microsoft.com...[vbcol=seagreen]
> Hi Stefan,
>
> I have encountered the issue you are referring to in the past when we
> tried
> to update a posting and we used the wrong context or were not in the right
> mode. We are not doing that in this code. I have even tried stripping all
> the
> controls out of the apsx and commenting out the all the cs code in the
> code
> behind. I still got the problem. If the problem were in the global.asax,
> wouldn't it still be an issue when I created a new page?
>
> Is there a way to turn on tracing or debug in CMS? It would be great to be
> able to get a more detailed error message or an exception with a stack
> trace.
>
> Thanks,
> Mike
>
> "Stefan Goßner [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

Stefan,

No I'm getting that message after I seleft save new page using the cms
authoring interface. It's displayed in the console error module. Is there a
way I can trap that exception? By the way, I am only getting this error when
I try to create new pages. I can update existing pages without a problem.

Thanks,
Mike


"Stefan Goßner [MSFT]" wrote:

> Hi Mike,
>
> you cannot trace this with MCMS methods.
> You need to identify the line of code that causes the problem.
> Is there a callstack that comes with the error?
>
> Cheers,
> Stefan
>
> "Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
> message news:F1C6A774-F11B-4D3C-AA66-DE7D023F5655@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Mike,

this sounds as if the problem occurs either in a workflow event.
Please disable all workflow events and check if the problem is gone.

Cheers,
Stefan

"Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
message news:AB6E10D2-0D35-4122-A6EC-1CA24CA4CB83@microsoft.com...[vbcol=seagreen]
> Stefan,
>
> No I'm getting that message after I seleft save new page using the cms
> authoring interface. It's displayed in the console error module. Is there
> a
> way I can trap that exception? By the way, I am only getting this error
> when
> I try to create new pages. I can update existing pages without a problem.
>
> Thanks,
> Mike
>
>
> "Stefan Goßner [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

Hi Stefan,

How do I disable workflow?

Thanks,
Mike

"Stefan Goßner [MSFT]" wrote:

> Hi Mike,
>
> this sounds as if the problem occurs either in a workflow event.
> Please disable all workflow events and check if the problem is gone.
>
> Cheers,
> Stefan
>
> "Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
> message news:AB6E10D2-0D35-4122-A6EC-1CA24CA4CB83@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Mike,

usually you implemented it in your global.asax.cs or you did this in a
custom http module.
Check where your workflow events are implemented and remove them.

Cheers,
Stefan


"Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
message news:AB2D0CD9-C7E7-4F17-BBA0-C761291F9A92@microsoft.com...[vbcol=seagreen]
> Hi Stefan,
>
> How do I disable workflow?
>
> Thanks,
> Mike
>
> "Stefan Goßner [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

Hi Stefan,

We do not do anything with CMS in the global.asax. In some pages we capture
work flow events but even templates without this work flow code error out on
creation. For some reason new pages with the same code and html does not hav
e
this problem. I am puzzled.

Thanks,
Mike

"Stefan Goßner [MSFT]" wrote:

> Hi Mike,
>
> usually you implemented it in your global.asax.cs or you did this in a
> custom http module.
> Check where your workflow events are implemented and remove them.
>
> Cheers,
> Stefan
>
>
> "Mike Buckingham" <MikeBuckingham@discussions.microsoft.com> wrote in
> message news:AB2D0CD9-C7E7-4F17-BBA0-C761291F9A92@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]