Microsoft Content Management Server - Simple Export Fails

This is Interesting: Free IT Magazines  
Home > Archive > Microsoft Content Management Server > April 2007 > Simple Export Fails





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 Simple Export Fails
Tom

2007-04-18, 7:17 pm

I am trying to export a single Template from Site Manager and I'm getting
this error.

I have enabled Anonymous Access account to virtual directors \nr and \mcms.

What else can I try?


Thanks

Tom
Note: I'm using CMS 2002 sp2 on a Windows 2003 SP1 OS with Security hotfix

Tom

2007-04-18, 7:17 pm

In additon to
1. Ensure that the 'ASPNET' account has the "Impersonate a client after
authentication" privilege.
2. Ensure that the /MCMS virtual directory has anonymous access enabled.
3. Ensure that the /NR virtual directory has anonymous access enabled.

Here is what I had to do to get it to work.

In the root of my site (c:\inetpub\wwwroot) I am encrypting session state
password in a custom web.config file.

I then disabled sessionState from Machine.config.

So if I remove web.config from c:\inetpub\wwwroot and re-enable sessonState
in Machine.config I am able to export.

Tom

"Tom" wrote:

> I am trying to export a single Template from Site Manager and I'm getting
> this error.
>
> I have enabled Anonymous Access account to virtual directors \nr and \mcms.
>
> What else can I try?
>
>
> Thanks
>
> Tom
> Note: I'm using CMS 2002 sp2 on a Windows 2003 SP1 OS with Security hotfix
>

Stefan Goßner [MSFT]

2007-04-19, 7:17 am

Hi Tom,

it is recommended not to have a web.config in the root of the website you
are using to connect with Site Manager or client-side SDAPI to.

Cheers,
Stefan


"Tom" <Tom@discussions.microsoft.com> wrote in message
news:5037000D-317D-4228-B11E-B17532E16535@microsoft.com...[vbcol=seagreen]
> In additon to
> 1. Ensure that the 'ASPNET' account has the "Impersonate a client after
> authentication" privilege.
> 2. Ensure that the /MCMS virtual directory has anonymous access enabled.
> 3. Ensure that the /NR virtual directory has anonymous access enabled.
>
> Here is what I had to do to get it to work.
>
> In the root of my site (c:\inetpub\wwwroot) I am encrypting session state
> password in a custom web.config file.
>
> I then disabled sessionState from Machine.config.
>
> So if I remove web.config from c:\inetpub\wwwroot and re-enable
> sessonState
> in Machine.config I am able to export.
>
> Tom
>
> "Tom" wrote:
>


Tom

2007-04-19, 7:16 pm

Can you elaborate on this please?

Tom

"Stefan Goßner [MSFT]" wrote:

> Hi Tom,
>
> it is recommended not to have a web.config in the root of the website you
> are using to connect with Site Manager or client-side SDAPI to.
>
> Cheers,
> Stefan
>
>
> "Tom" <Tom@discussions.microsoft.com> wrote in message
> news:5037000D-317D-4228-B11E-B17532E16535@microsoft.com...
>
>
>

Stefan Goßner [MSFT]

2007-04-19, 7:16 pm

Hi Tom,

template projects for MCMS should not be created in the root of a web site
but in a web application inside the root. E.g. http://localhost/templates
rather than http://localhost.

This will ensure that no web.config is in the root. You already have seen
that that web.config files in the root can cause problem as they interact
with the web.config files in the MCMS virtual directory.

Cheers,
Stefan

"Tom" <Tom@discussions.microsoft.com> wrote in message
news:169E8C9B-443F-40A9-9A10-E5C24DFDED20@microsoft.com...[vbcol=seagreen]
> Can you elaborate on this please?
>
> Tom
>
> "Stefan Goßner [MSFT]" wrote:
>


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com