Error message when you try to connect to a site in a Windows SharePoint Services 3.0 site collection after you configure a document library to inherit permissions: "HTTP 500 - Internal server error"

Article translations Article translations
Article ID: 935958 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario. You create a site collection in Microsoft Windows SharePoint Services 3.0 that contains several sites. You configure the permissions of a document library in one of the sites to inherit permissions. This operation is successful and the document library inherits its permissions as expected.

However, when you try to connect to a site in the site collection, you receive the following error message:
HTTP 500 - Internal server error
All sites in the site collection are inaccessible.

For example, you experience these symptoms if the following conditions are true:
  • You create a site that is named Site A. Site A inherits permissions from the parent site. Then, you configure Site A to stop inheriting permissions.
  • Under Site A, you create a subsite that is named Site B. Site B inherits permissions from the parent site. Then, you configure Site B to stop inheriting permissions.
  • You configure Site A to inherit permissions from the top-level site.
  • You create a document library in Site B, and then you configure the document library to inherit permissions from Site B.
In this scenario, the document library inherits permissions from Site B. However, you receive the error message when you try to access a site in the site collection.

CAUSE

This problem occurs if Windows SharePoint Services 3.0 incorrectly processes the inheritance of certain permissions. This condition causes the content database to contain incorrect information.

RESOLUTION

How to obtain the hotfix

This issue is fixed in the Windows SharePoint Services 3.0 hotfix package that is dated May 15, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
936867 Description of the Windows SharePoint Services 3.0 hotfix package: May 8, 2007
Notes
  • This hotfix package includes a hotfix that applies to scenarios in which the content database has not yet been created on the server. This hotfix helps prevent the issue. It does not fix sites that are inaccessible.
  • This hotfix package includes a hotfix that cleans up the content database to fix sites that are inaccessible. To enable this hotfix, make sure that you run the "SharePoint Products and Technologies Configuration Wizard" after you apply the hotfix.
This hotfix package resolves the problem. However, this hotfix does not prevent the problem. If the problem recurs, follow these steps:
  1. For the content database where you have the site, run the following command:
    exec proc_DetectSecurityCorruption
  2. If records are returned when you run the command in step 1, run the following command for each ID that is returned:
    exec proc_SecFixFoldersInSubWeb <ID_from_step 1>

    Note In this command, <ID_from_step 1> is a placeholder for the ID that is returned in step 1.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 935958 - Last Review: October 8, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft Windows SharePoint Services 3.0
Keywords: 
kbwss30postrtm kbexpertiseinter kbqfe kbbug kbfix KB935958

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com