I just reinstalled the existing solution(upgraded from CMS2002) onto new box
w/Windows 2003/CMS Sp1a. I configured anonymous user w/proper access to all
the postings and templates, restored and re-configured the solution's
database,etc - I did everything step-by step following all the instructions
for SP1 and sp1a, but of course, I am deploying the solution on a brand-new
box with a new configuration. While transferring the solution from the
development box, I have not used site deployment import routines in Site
Manager, but all my templates show up fine in there. I simply copied the
website files (after rebuilding the solution w/VS 2003)  from the
development box that was upgraded to sp1A .

I can successfully get to MCMS homeport, but when I try to access any of the
channels of the site from the Homeport or when I try to create new page
(while logged in as an administrator) using any template - I get an error
like below (could do the same thing in development just fine after the
upgrade)
There are no errors in the event log.

It must be something really obvious - please help

Server Error in '/' Application.
----------------------------------------------------------------------------
----

The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make sure that
it is spelled correctly.

Requested Url: /websiteName/Templates/Locator.aspx

[ Post a follow-up to this message ]

Hi Ilona,

beside Mei Yings hints also check the IIS log for 404 errors.
Then double check the path logged in the error message and in the log file
and compare it with the virtual folder view in IIS MMC.
You should see the missing part easily.

Cheers,
Stefan.

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

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Mei Ying (MVP)" <anonymous@discussions.microsoft.com> wrote in message
news:1d5501c46fb8$170e8670$a301280a@phx.gbl...[vbcol=seagreen]
> Hi
>
> Have you created the virtual directory for websitename in
> IIS? Also, ensure that you have the CMS virtual directory
> createdor you will encounter problems later :-)
>
> regards
> Mei Ying
> 
> CMS2002) onto new box 
> w/proper access to all 
> the solution's 
> all the instructions 
> solution on a brand-new 
> solution from the 
> routines in Site 
> simply copied the 
> from the 
> to access any of the 
> create new page 
>  I get an error 
> fine after the 
> ------------------ 
> (or one of its 
> changed, or is 
> and make sure that 

[ Post a follow-up to this message ]

IIS Log helped - I was missing CMS virtual directory. Thank you guys, looks
like I might actually get this to work reasonably soon and will not have to
stay late -- so I am going to have my ballroom/latin dancing practice
tonight (I noticed somebody here is into dancing as well ;) ) to get ready
for a comp. Awesome!

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:%23k8GdU8bEHA.2844@TK2MSFTNGP12.phx.gbl...
> Hi Ilona,
>
> beside Mei Yings hints also check the IIS log for 404 errors.
> Then double check the path logged in the error message and in the log file
> and compare it with the virtual folder view in IIS MMC.
> You should see the missing part easily.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> MCMS FAQ:
>

> MCMS Blog: [url]http://blogs.msdn.com/stefan_gossner/category/4983.aspx" target="_blank">http://download.microsoft.com/downl...egory/4983.aspx
> MCMS Sample Code:
>
http://www.gotdotnet.com/community/...
+Server
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "Mei Ying (MVP)" <anonymous@discussions.microsoft.com> wrote in message
> news:1d5501c46fb8$170e8670$a301280a@phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi Ilona,

be sure to create the CMS virtual folder as virtual directory and not as web
application!
Whenever you create a virtual directory with IIS MMC it is automatically a
web application.
You have to open the properties of the CMS application and click the remove
button in the application section to change it to a real virtual directory.

Cheers,
Stefan.

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

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"ilona" <ieshulman@sseinc.com> wrote in message
news:ehYXGABcEHA.4092@TK2MSFTNGP11.phx.gbl...
> IIS Log helped - I was missing CMS virtual directory. Thank you guys,
looks
> like I might actually get this to work reasonably soon and will not have
to
> stay late -- so I am going to have my ballroom/latin dancing practice
> tonight (I noticed somebody here is into dancing as well ;) ) to get ready
> for a comp. Awesome!
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:%23k8GdU8bEHA.2844@TK2MSFTNGP12.phx.gbl... 
file[vbcol=seagreen] 
> rights. 
>
 
>
[url]http://www.gotdotnet.com/community/usersamples/Default.aspx?ProductDropDownList=Content+Management
+Server" target="_blank">http://download.microsoft.com/downl...
+Server 
>
>

[ Post a follow-up to this message ]

Thanks, Stefan
I already saw that from your FAQ site, so I am already pass that, i got it
up and running except for a few issues below. It would be really helpful if
you added a list of typical IIS configurations to your FAQ, because now you
have to "fish" for IIS config throughout install docs and the FAQs to make
sure you have not left out anything and install went ok.
Here is the config that we had in production for about a year and it seams
to work ok. Although even after developing and supporting CMS for a year I
am still not sure if the config that we have is the most common scenario, in
particular:
1) if you only have 1 website on the box would it make sence to combine MCMS
and myCmsSite into one Application? If so, would you remove default
web.config that is inside MCMS app?
2) do you have to have webctrl_client(App) in your website? what is it for?

* Default web site
* Another website for mcms-enabled site www.myCmsSite.com (App; Read, Log
Visits, Index This Resource; Anonymous access and Integrated Windows
authentication)
Under www.myCmsSite.com:
* NR(Virtual Directory; Read,Log Visits; Anonymous access and Integrated
Windows         authentication) points to Program Files/Microsoft Content
management Server/Server/IIS_NR
Under NR:
+
* MCMS (App;Read,Log Visits; Anonymous access and Integrated Windows
authentication)
points to Program Files/Microsoft Content management
Server/Server/MCMS
Under MCMS:
web.config
+ Site Deployment
+ CMS
* NRConfig(Virtual Directory; Read,Log Visits; Anonymous access and
Integrated Windows         authentication) points to Program Files/Microsoft
Content management Server/Server/NRConfig
* webctrl_client(App) points to Program Files/Microsoft Content
management Server/Server/Controls/Webctrl_client
* myCmsSite(App)
web.config
global.asa
+CMS (Virtual Directory)
+Templates
+Controls
etc



Now I am working on getting rid of authentication errors.
Logging Off the Edit mode for now is giving "The current user does not have
rights to the requested item"
and the site throws "Logon failed due to invalid or expired authentication"
after the site sits for a while. I have all the error conditions that the
error page mentions set correctly. What I can see from your FAQs - we should
not use current context in ManualLogin - and we do not,
we use forms authentication and the code like in Woodgrove. BTW, did
anything in Woodgrove change to accomodate SP1a?
try
{
if(NTUser.IndexOf( "@" ) == -1)
{
NTUser = FormWinNTLoginName("WinNT://", NTDomain, NTUser);
}
}
catch(ArgumentOutOfRangeException)
{
OutMessage.InnerHtml = "<tr><td colspan=3><FONT COLOR=red>" +
LTArgumentOutOfRangeExceptionMessage + "</FONT></td></tr>";
}

try
{
CmsAuthenticationTicket ticket =
CmsFormsAuthentication.AuthenticateAsUser(NTUser, NTPassword);
if( ticket != null )
{
CmsFormsAuthentication.RedirectFromLoginPage(ticket, true,
CheckPersistent.Checked);
}
OutMessage.InnerHtml = "<FONT COLOR=red>" + LTInvalidUserMessage +
"</FONT>";
}
catch(Exception)
{
OutMessage.InnerHtml = "<FONT COLOR=red>" + LTGeneralExceptionMessage +
"</FONT>";
}

[ Post a follow-up to this message ]

Hi Ilona,

never touch the MCMS web application!
This application is used by SiteManager. Any modification to this web
application can cause problems during client-side site deployment and usage
of SiteManager.
Always use a separated web application which should not be in the root of
the web site.

The webctrl_client virtual directory contain the IE web controls which are
(e.g.) used for the tree view in Web Author.
Without this virtual directory web author will not work correct and also the
navigation used in Woodgrove relies on it.

NRCONFIG should not be on a MCMS enabled web site.
NRCONFIG is the SCA and the SCA should be on a separate web site for
security reasons. Especially on a production site I would recommend to have
it on a separate site with IP restrictions enabled.

When exactly do you get the "Logon failed due to invalid or expired
authentication" error?

Cheers,
Stefan.

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

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"ilona" <ieshulman@sseinc.com> wrote in message
news:eT4eU3DcEHA.2812@TK2MSFTNGP11.phx.gbl...
> Thanks, Stefan
> I already saw that from your FAQ site, so I am already pass that, i got it
> up and running except for a few issues below. It would be really helpful
if
> you added a list of typical IIS configurations to your FAQ, because now
you
> have to "fish" for IIS config throughout install docs and the FAQs to make
> sure you have not left out anything and install went ok.
> Here is the config that we had in production for about a year and it seams
> to work ok. Although even after developing and supporting CMS for a year I
> am still not sure if the config that we have is the most common scenario,
in
> particular:
> 1) if you only have 1 website on the box would it make sence to combine
MCMS
> and myCmsSite into one Application? If so, would you remove default
> web.config that is inside MCMS app?
> 2) do you have to have webctrl_client(App) in your website? what is it
for?
>
> * Default web site
> * Another website for mcms-enabled site www.myCmsSite.com (App; Read, Log
> Visits, Index This Resource; Anonymous access and Integrated Windows
> authentication)
>     Under www.myCmsSite.com:
>     * NR(Virtual Directory; Read,Log Visits; Anonymous access and
Integrated
> Windows         authentication) points to Program Files/Microsoft Content
> management Server/Server/IIS_NR
>         Under NR:
>         +
>     * MCMS (App;Read,Log Visits; Anonymous access and Integrated Windows
> authentication)
>         points to Program Files/Microsoft Content management
> Server/Server/MCMS
>             Under MCMS:
>             web.config
>             + Site Deployment
>             + CMS
>     * NRConfig(Virtual Directory; Read,Log Visits; Anonymous access and
> Integrated Windows         authentication) points to Program
Files/Microsoft
> Content management Server/Server/NRConfig
>     * webctrl_client(App) points to Program Files/Microsoft Content
> management Server/Server/Controls/Webctrl_client
>     * myCmsSite(App)
>         web.config
>         global.asa
>         +CMS (Virtual Directory)
>         +Templates
>         +Controls
>             etc
>
>
>
> Now I am working on getting rid of authentication errors.
> Logging Off the Edit mode for now is giving "The current user does not
have
> rights to the requested item"
> and the site throws "Logon failed due to invalid or expired
authentication"
> after the site sits for a while. I have all the error conditions that the
> error page mentions set correctly. What I can see from your FAQs - we
should
> not use current context in ManualLogin - and we do not,
> we use forms authentication and the code like in Woodgrove. BTW, did
> anything in Woodgrove change to accomodate SP1a?
> try
> {
> if(NTUser.IndexOf( "@" ) == -1)
> {
> NTUser = FormWinNTLoginName("WinNT://", NTDomain, NTUser);
> }
> }
> catch(ArgumentOutOfRangeException)
> {
> OutMessage.InnerHtml = "<tr><td colspan=3><FONT COLOR=red>" +
> LTArgumentOutOfRangeExceptionMessage + "</FONT></td></tr>";
> }
>
> try
> {
> CmsAuthenticationTicket ticket =
> CmsFormsAuthentication.AuthenticateAsUser(NTUser, NTPassword);
> if( ticket != null )
> {
> CmsFormsAuthentication.RedirectFromLoginPage(ticket, true,
> CheckPersistent.Checked);
> }
> OutMessage.InnerHtml = "<FONT COLOR=red>" + LTInvalidUserMessage +
> "</FONT>";
> }
> catch(Exception)
> {
> OutMessage.InnerHtml = "<FONT COLOR=red>" + LTGeneralExceptionMessage +
> "</FONT>";
> }
>
>
>

[ Post a follow-up to this message ]

I get "Logon failed due to invalid or expired authentication token" error in
the following scenario:
* log in as administrator
* let the session expire by not using the site for some time
* navigate away to some other page
You are getting redirected to the ManualLogin.aspx with the url of
http://myCMSSite/ManualLogin.aspx? ...r />
odifyGues
t&NRMODE=Published&NRORIGINALURL=%2fCommon%2fAbout%2bUs%2f&NRNODEGUID=%7b845
03520-C67F-47BF-8E49-A441C745C7FF%7d&NRCACHEHINT=NoModifyGuest
but the error is thrown before Page_Load or initialization event is hit


I get the error below in this scenario:
* log in to the site as administrator
* expand the editing menu on the side
* log out

The current user does not have rights to the requested item.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: The current
user does not have rights to the requested item.

Source Error:


An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.


Stack Trace:


[COMException (0x80041bff): The current user does not have rights to the
requested item.]

Microsoft.ContentManagement.Interop.Publishing.CmsHttpContextClass.Initializ
e(String currentUrl, String httpHostName, Int32 serverPort, Boolean
isSecureServer, Int32 iisInstanceId, String remoteMachineAddress, String
authenticationType, String authenticationToken, Int32 windowsUserHandle,
String ClientAccountName) +0
Microsoft.ContentManagement.Publishing.CmsHttpContext.initialize(IntPtr
windowsToken, String cmsAuthToken, String clientUserName, String
clientAccountType) +297

Microsoft.ContentManagement.Publishing.CmsHttpContext.getCmsHttpContextFromI
dentity(HttpContext httpContext) +1088
Microsoft.ContentManagement.Publishing.CmsHttpContext.get_Current() +57

[CmsAccessDeniedException: The current user does not have access to the
requested item.

If you are seeing this exception when a CMS template is executing, it means
that you have removed the CmsAuthorizationModule from the
<httpModules>...</httpModules> section of your web.config.  You can only
remove this module if:
1. All requests for every CMS template in the web application will only be
accessed by anonymous users
2. Guest access is enabled in CMS (via the SCA)
3. The CMS guest user has access to all postings based on templates in the
web application

If any of these requirements are not met, you MUST register the
CmsAuthorizationModule in your web.config.]
Microsoft.ContentManagement.Publishing.CmsHttpContext.get_Current() +251
stlbsa.HttpModules.CmsSslHttpModule.OnPreRequestHandlerExecute(Object o,
EventArgs e)

System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.
Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +87





----------------------------------------------------------------------------
----

Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573

[ Post a follow-up to this message ]

Hi Ilona,

the problem is being caused by an outdated version of my CmsSslHttpModule!
The first version I uploaded to gotdotnet was not able to handle expiration
of cookies correct.

I have updated the module:
http://www.gotdotnet.com/Community/...04-2F06C5A52A89

This version should not cause this problem.
I appologize for the inconvenience.

Cheers,
Stefan.

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

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"ilona" <ieshulman@sseinc.com> wrote in message
news:erWVokNcEHA.2816@TK2MSFTNGP11.phx.gbl...
> I get "Logon failed due to invalid or expired authentication token" error
in
> the following scenario:
> * log in as administrator
> * let the session expire by not using the site for some time
> * navigate away to some other page
> You are getting redirected to the ManualLogin.aspx with the url of
>
http://myCMSSite/ManualLogin.aspx? ...r />
odifyGues
t&NRMODE=Published&NRORIGINALURL=%2fCommon%2fAbout%2bUs%2f&NRNODEGUID=%7b84503520-C67F-47BF-
8E49-A441C745C7FF%7d& NRCACHEHINT=NoModifyGuest
> but the error is thrown before Page_Load or initialization event is hit
>
>
> I get the error below in this scenario:
> * log in to the site as administrator
> * expand the editing menu on the side
> * log out
>
> The current user does not have rights to the requested item.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
>
> Exception Details: System.Runtime.InteropServices.COMException: The
current
> user does not have rights to the requested item.
>
> Source Error:
>
>
>       An unhandled exception was generated during the execution of the
> current web request. Information regarding the origin and location of the
> exception can be identified using the exception stack trace below.
>
>
> Stack Trace:
>
>
> [COMException (0x80041bff): The current user does not have rights to t
he
> requested item.]
>
>
Microsoft.ContentManagement.Interop.Publishing.CmsHttpContextClass.Initializ
> e(String currentUrl, String httpHostName, Int32 serverPort, Boolean
> isSecureServer, Int32 iisInstanceId, String remoteMachineAddress, String
> authenticationType, String authenticationToken, Int32 windowsUserHandle,
> String ClientAccountName) +0
>    Microsoft.ContentManagement.Publishing.CmsHttpContext.initialize(IntPtr
> windowsToken, String cmsAuthToken, String clientUserName, String
> clientAccountType) +297
>
>
Microsoft.ContentManagement.Publishing.CmsHttpContext.getCmsHttpContextFromI
> dentity(HttpContext httpContext) +1088
>    Microsoft.ContentManagement.Publishing.CmsHttpContext.get_Current() +57
>
> [CmsAccessDeniedException: The current user does not have access to th
e
> requested item.
>
> If you are seeing this exception when a CMS template is executing, it
means
> that you have removed the CmsAuthorizationModule from the
> <httpModules>...</httpModules> section of your web.config.  You can only
> remove this module if:
> 1. All requests for every CMS template in the web application will only be
> accessed by anonymous users
> 2. Guest access is enabled in CMS (via the SCA)
> 3. The CMS guest user has access to all postings based on templates in the
> web application
>
> If any of these requirements are not met, you MUST register the
> CmsAuthorizationModule in your web.config.]
>    Microsoft.ContentManagement.Publishing.CmsHttpContext.get_Current()
+251
>    stlbsa.HttpModules.CmsSslHttpModule.OnPreRequestHandlerExecute(Object
o,
> EventArgs e)
>
>
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.
> Execute() +60
>    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously) +87
>
>
>
>
>
> --------------------------------------------------------------------------
--
> ----
>
> Version Information: Microsoft .NET Framework Version:1.1.4322.573;
ASP.NET
> Version:1.1.4322.573
>
>
>
>
>
>

[ Post a follow-up to this message ]

Hi Stefan,
sorry it took me a while - got sidetracked with other projects.
It was a good catch about CmsSSlHttpModule! Redeployment of it seems to have
solved the "Logon failed due to invalid or expired authentication token"
problem. However, I am still having a problem
w/"The current user does not have rights to the requested item." error
message as described earlier. I'll try to figure it out and will keep you
posted.

Thanks again for your help!




"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:uI3qv%23YcEHA.1644@tk2msftngp13.phx.gbl...
> Hi Ilona,
>
> the problem is being caused by an outdated version of my CmsSslHttpModule!
> The first version I uploaded to gotdotnet was not able to handle
expiration
> of cookies correct.
>
> I have updated the module:
>
http://www.gotdotnet.com/Community/...r />
6C5A52A89
>
> This version should not cause this problem.
> I appologize for the inconvenience.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> MCMS FAQ:
>

> MCMS Blog: [url]http://blogs.msdn.com/stefan_gossner/category/4983.aspx" target="_blank">http://download.microsoft.com/downl...egory/4983.aspx
> MCMS Sample Code:
>
http://www.gotdotnet.com/community/...
+Server
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "ilona" <ieshulman@sseinc.com> wrote in message
> news:erWVokNcEHA.2816@TK2MSFTNGP11.phx.gbl... 
error[vbcol=seagreen]
> in 
>
http://myCMSSite/ManualLogin.aspx? ...r />
odifyGues
t&NRMODE=Published&NRORIGINALURL=%2fCommon%2fAbout%2bUs%2f&NRNODEGUID=%7b84503520-C67F-47BF-
8E49-A441C745C7FF%7d& NRCACHEHINT=NoModifyGuest 
> current 
the[vbcol=seagreen] 
>
Microsoft.ContentManagement.Interop.Publishing.CmsHttpContextClass.Initializ
 
Microsoft.ContentManagement.Publishing.CmsHttpContext.initialize(IntPtr[vbcol=seagreen] 
>
Microsoft.ContentManagement.Publishing.CmsHttpContext.getCmsHttpContextFromI
 
+57[vbcol=seagreen] 
> means 
be[vbcol=seagreen] 
the[vbcol=seagreen] 
> +251 
> o, 
>
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.
 
>
> --------------------------------------------------------------------------
> -- 
> ASP.NET 
>
>

[ Post a follow-up to this message ]

Hi Ilona,

I have seen this problem when an item is being saved with a reference to a
resource gallery item where this user does not have rights to.
So the problem should not happen with a MCMS administrator (e.g.).

Please verify if this problem also comes up for postings where no resource
gallery items are referenced. I would assume that not.
Btw: you need to check the placeholder content with view source - if you
remove an attachment then often the link stays in the html - only the
thumbnail image is removed.

To avoid this problem the following code can be used:
http://blogs.msdn.com/stefan_gossne.../07/175298.aspx

Cheers,
Stefan.

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

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"ilona" <ieshulman@sseinc.com> wrote in message
news:eJVAfgAdEHA.1652@TK2MSFTNGP09.phx.gbl...
> Hi Stefan,
> sorry it took me a while - got sidetracked with other projects.
> It was a good catch about CmsSSlHttpModule! Redeployment of it seems to
have
> solved the "Logon failed due to invalid or expired authentication token"
> problem. However, I am still having a problem
> w/"The current user does not have rights to the requested item." error
> message as described earlier. I'll try to figure it out and will keep you
> posted.
>
> Thanks again for your help!
>
>
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:uI3qv%23YcEHA.1644@tk2msftngp13.phx.gbl... 
CmsSslHttpModule![vbcol=seagreen] 
> expiration 
>
http://www.gotdotnet.com/Community/...r />
6C5A52A89 
> rights. 
>
 
>
[url]http://www.gotdotnet.com/community/usersamples/Default.aspx?ProductDropDownList=Content+Management
+Server" target="_blank">http://download.microsoft.com/downl...
+Server 
> error 
>
http://myCMSSite/ManualLogin.aspx? ...r />
odifyGues
t&NRMODE=Published&NRORIGINALURL=%2fCommon%2fAbout%2bUs%2f&NRNODEGUID=%7b84503520-C67F-47BF-
8E49-A441C745C7FF%7d& NRCACHEHINT=NoModifyGuest 
hit[vbcol=seagreen] 
the[vbcol=seagreen] 
information[vbcol=seagreen] 
> the 
the[vbcol=seagreen] 
>
Microsoft.ContentManagement.Interop.Publishing.CmsHttpContextClass.Initializ
 
String[vbcol=seagreen] 
windowsUserHandle,[vbcol=seagreen] 
> Microsoft.ContentManagement.Publishing.CmsHttpContext.initialize(IntPtr 
>
Microsoft.ContentManagement.Publishing.CmsHttpContext.getCmsHttpContextFromI
 
> +57 
the[vbcol=seagreen] 
only[vbcol=seagreen] 
only[vbcol=seagreen]
> be 
> the 
stlbsa.HttpModules.CmsSslHttpModule. OnPreRequestHandlerExecute(Object[vbcol=
seagreen] 
>
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.
 
Boolean&[vbcol=seagreen] 
>
> --------------------------------------------------------------------------
 
>
>

[ Post a follow-up to this message ]