I've spent almost 7 hours on this problem.  I have developed an MCMS on a
development server.  It looks great.  People can enter "edit" mode, change,
approve, submit pages.  Excellent.  Now, I moved it to a production server.
On the development server's Site Manager, I exported everything to a file.  
I
copied the file to the production server.  I imported that file into the
production server's Site Manager.  I then copied my aspx files using VS.NET'
s
copy project.  Everything appeared on the production server as I expected.
Now, when I hit the pages on the production server, the default console
doesn't appear and no one can enter "edit" mode.  What happened?  The
developement server and production server are on the same domain.  SOMEONE
PLEASE PLEASE HELP ME.  I AM AT A TOTAL LOSS.

Thanks,
Adam

[ Post a follow-up to this message ]

Hi Adam,

is your production site configured as a read-only site?
Then the console will never show up.

Also check if guest access is enabled. If yes, please disable it for a test.
Are you able to login to the site using an author now?
If yes the console should show up.

Background: If guest access is enabled an invalid users log in then they are
often treated as guests and these do not have authoring rights - so the
console will not show up.
Disabling guest access for the test will ensure that the user can either
login as this user or he cannot login - so you will get a dedicated state.

Also verify CmsHttpContext.Current.User. Is this the correct user?
What does CmsHttpContext.Current.UserCanAuthor return?

Chees,
Stefan

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

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------


"Adam" <Adam@discussions.microsoft.com> wrote in message
news:27542B8B-F18C-4DD3-9811-BE8B4331ACA7@microsoft.com...
> I've spent almost 7 hours on this problem.  I have developed an MCMS on a
> development server.  It looks great.  People can enter "edit" mode,
> change,
> approve, submit pages.  Excellent.  Now, I moved it to a production
> server.
> On the development server's Site Manager, I exported everything to a file.
> I
> copied the file to the production server.  I imported that file into the
> production server's Site Manager.  I then copied my aspx files using
> VS.NET's
> copy project.  Everything appeared on the production server as I expected.
> Now, when I hit the pages on the production server, the default console
> doesn't appear and no one can enter "edit" mode.  What happened?  The
> developement server and production server are on the same domain.  SOMEONE
> PLEASE PLEASE HELP ME.  I AM AT A TOTAL LOSS.
>
> Thanks,
> Adam
>

[ Post a follow-up to this message ]

The site is Read/Write
Guess access WAS enabled.  I disabled it and received an "Access Denied" on
all the homepages.  I then enabled it and did a Response.Write to return the
following:
CmsHttpContext.Current.UserCanAuthor  returns True.
CmsHttpContext.Current.User is who I want it to be.

I am at a dead end here, so I'll appreciate any suggestions.  Thanks for
responding on a Saturday.

Adam





"Stefan [MSFT]" wrote:

> Hi Adam,
>
> is your production site configured as a read-only site?
> Then the console will never show up.
>
> Also check if guest access is enabled. If yes, please disable it for a tes
t.
> Are you able to login to the site using an author now?
> If yes the console should show up.
>
> Background: If guest access is enabled an invalid users log in then they a
re
> often treated as guests and these do not have authoring rights - so the
> console will not show up.
> Disabling guest access for the test will ensure that the user can either
> login as this user or he cannot login - so you will get a dedicated state.
>
> Also verify CmsHttpContext.Current.User. Is this the correct user?
> What does CmsHttpContext.Current.UserCanAuthor return?
>
> Chees,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44[/url...nyurl.com/8ugwj
> ----------------------
>
>
> "Adam" <Adam@discussions.microsoft.com> wrote in message
> news:27542B8B-F18C-4DD3-9811-BE8B4331ACA7@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Also try ensuring that at least 1 channel does NOT allow the public
reader/guest access group. Going to this channel should force the Manual
Login Page


"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:%23IBJTFU7FHA.2036@TK2MSFTNGP14.phx.gbl...
> Hi Adam,
>
> is your production site configured as a read-only site?
> Then the console will never show up.
>
> Also check if guest access is enabled. If yes, please disable it for a
> test.
> Are you able to login to the site using an author now?
> If yes the console should show up.
>
> Background: If guest access is enabled an invalid users log in then they
> are often treated as guests and these do not have authoring rights - so
> the console will not show up.
> Disabling guest access for the test will ensure that the user can either
> login as this user or he cannot login - so you will get a dedicated state.
>
> Also verify CmsHttpContext.Current.User. Is this the correct user?
> What does CmsHttpContext.Current.UserCanAuthor return?
>
> Chees,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS:
> http://tinyurl.com/6zj44
> Check out the new book as well: Advanced MCMS development:
> http://tinyurl.com/8ugwj
> ----------------------
>
>
> "Adam" <Adam@discussions.microsoft.com> wrote in message
> news:27542B8B-F18C-4DD3-9811-BE8B4331ACA7@microsoft.com... 
>
>

[ Post a follow-up to this message ]

Hi Adam,

the access denied is the reason for this problem.
Please disable guest access again to focus on resolving this problem.
One possible reason for this is that the application pool account does not
have the SeImpersonatePriviledge.
Please double check.

Cheers,
Stefan

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

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------


"Adam" <Adam@discussions.microsoft.com> wrote in message
news:963E5788-2CC9-470E-94A6-5D3762F0E6BA@microsoft.com...[vbcol=seagreen]
> The site is Read/Write
> Guess access WAS enabled.  I disabled it and received an "Access Denied"
> on
> all the homepages.  I then enabled it and did a Response.Write to return
> the
> following:
>     CmsHttpContext.Current.UserCanAuthor  returns True.
>    CmsHttpContext.Current.User is who I want it to be.
>
> I am at a dead end here, so I'll appreciate any suggestions.  Thanks for
> responding on a Saturday.
>
> Adam
>
>
>
>
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

Paul,
I am not sure what you mean by "public reader/guest access group".  Could
you please tell me what you are referring to?

Thanks,
Adam


"Paul Devenney" wrote:

> Also try ensuring that at least 1 channel does NOT allow the public
> reader/guest access group. Going to this channel should force the Manual
> Login Page
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:%23IBJTFU7FHA.2036@TK2MSFTNGP14.phx.gbl... 
>
>
>

[ Post a follow-up to this message ]

Stefan,
I'll check this on Monday, but can you tell me how to double check this:

One possible reason for this is that the application pool account does not
have the SeImpersonatePriviledge.

Thanks,
Adam


"Stefan [MSFT]" wrote:

> Hi Adam,
>
> the access denied is the reason for this problem.
> Please disable guest access again to focus on resolving this problem.
> One possible reason for this is that the application pool account does not
> have the SeImpersonatePriviledge.
> Please double check.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44[/url...nyurl.com/8ugwj
> ----------------------
>
>
> "Adam" <Adam@discussions.microsoft.com> wrote in message
> news:963E5788-2CC9-470E-94A6-5D3762F0E6BA@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Adam,

check this using the group policy snap in for your MMC.
Use the local computer policies and then look in the following entry:

- Local Computer Policy
- Computer Confiuration
- Windows Settings
- Security Settings
- Local Policies
- User Right Assignments
- Impersonate a client after authentication.

Here your application pool account needs to be included.

Cheers,
Stefan

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

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------


"Adam" <Adam@discussions.microsoft.com> wrote in message
news:170A009D-6D57-479F-814F-7C613AC51F52@microsoft.com...[vbcol=seagreen]
> Stefan,
> I'll check this on Monday, but can you tell me how to double check this:
>
> One possible reason for this is that the application pool account does not
> have the SeImpersonatePriviledge.
>
> Thanks,
> Adam
>
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

Stefan,
Thanks for the suggestion.  The following groups were included in the
"Impersonate a client after authentication" :

Administrators
ASPNET
IIS_WPG
Service

I did not change anything because these are the groups I expected to see.
What else do you suggest?

Thanks again,
Adam


"Stefan [MSFT]" wrote:

> Hi Adam,
>
> check this using the group policy snap in for your MMC.
> Use the local computer policies and then look in the following entry:
>
> - Local Computer Policy
>    - Computer Confiuration
>       - Windows Settings
>          - Security Settings
>             - Local Policies
>                - User Right Assignments
>                   - Impersonate a client after authentication.
>
> Here your application pool account needs to be included.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44[/url...nyurl.com/8ugwj
> ----------------------
>
>
> "Adam" <Adam@discussions.microsoft.com> wrote in message
> news:170A009D-6D57-479F-814F-7C613AC51F52@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Adam,

is your application pool account a member of the IIS_WPG group?

Cheers,
Stefan

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

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------


"Adam" <Adam@discussions.microsoft.com> wrote in message
news:C6213F11-61BD-4B40-B1A3-9B0D05C16B64@microsoft.com...[vbcol=seagreen]
> Stefan,
> Thanks for the suggestion.  The following groups were included in the
> "Impersonate a client after authentication" :
>
> Administrators
> ASPNET
> IIS_WPG
> Service
>
> I did not change anything because these are the groups I expected to see.
> What else do you suggest?
>
> Thanks again,
> Adam
>
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]