Microsoft Knowledge Base Email Alertz

KBAlertz.com: After you add a user to a Security Group of a SharePoint Team Web site or FrontPage 2002 Web Site, you cannot log on to the Web site as that user.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 292643 - Last Review: January 31, 2007 - Revision: 2.2

FP2002: Cannot Log On to Web Site As a Newly Added User

This article was previously published under Q292643

SYMPTOMS

After you add a user to a Security Group of a SharePoint Team Web site or FrontPage 2002 Web Site, you cannot log on to the Web site as that user.

CAUSE

This behavior occurs in the following situation:
  • You configure the Web site directory security to use Basic Authentication.

    -and-
  • You add a new user to one of the following Security Groups for the FrontPage Server Extensions or SharePoint Team Services
    OWS_NUMBER_admin
    OWS_NUMBER_advauthor
    OWS_NUMBER_author
    OWS_NUMBER_browser
    OWS_NUMBER_collab

    where NUMBER is a unique identifier that is generated from the name of the of the Web site.
You cannot log on to the Web site because the Microsoft Internet Information Service (IIS) Basic Authentication password cache has not been "refreshed" to include the newly added user.

RESOLUTION

To resolve this behavior, change the delay settings that are used by IIS when updating the cache. For additional information about how to change the delay before user tokens are updated in Microsoft Internet Information Services, click the article number below to view the article in the Microsoft Knowledge Base:
152526  (http://kbalertz.com/Feedback.aspx?kbNumber=152526/EN-US/ ) Changing the Default Interval for User Tokens in IIS

WORKAROUND

To work around this behavior, stop and then restart all of the IIS services. This will manually update the IIS cache.

For more information about how to restart services, search for the word "Services" in Microsoft Windows Help.

MORE INFORMATION

When you use Basic Authentication, the user supplies an unencrypted (plain text) user name and password to the IIS server computer. The Web server stores this information in a memory cache and creates a session for the user with the same credentials as the corresponding Microsoft Windows NT account.

The IIS server stores this cached account information for up to two hours but with a minimum time of fifteen minutes (idle lifetime).

For this reason, when you add a user account to one of the Web site security groups, you may have to wait for up to fifteen minutes before the IIS cache refreshes and can authenticate the changes. These cache settings are stored in the Windows registry. To view these settings, click the article number that is referenced in the "Resolution" section of this article.

APPLIES TO
  • Microsoft FrontPage 2002 Server Extensions
  • Microsoft SharePoint Team Services
  • Microsoft FrontPage 2002 Standard Edition
Keywords: 
kbnofix kbprb KB292643
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please