MS10-072: Description of the security update for Windows SharePoint Services 3.0: October 12, 2010

More information about this security update

Back to the top | Give Feedback

Prerequisites to apply this security update

• You must have Windows SharePoint Services 3.0 Service Pack 2 or a later version installed to apply this security update. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  949582

  (http://support.microsoft.com/kb/949582/ )

  How to obtain the latest service pack for Windows SharePoint Services 3.0

Back to the top | Give Feedback

Known issues with this security update

• Known issue 1
  
  Symptom
  If the SharePoint Products and Technologies Configuration Wizard does not finish its task, SharePoint may be left in an inconsistent state. You may be unable to browse the Central Administration or SharePoint site, and you receive one of the following error messages:
  
  Error message 1
  
  

  Server Error: http://go.microsoft.com/fwlink?LinkID=96177

  
  Error message 2
  
  

  HTTP 404 Not Found

  
  Error message 3
  
  

  Cannot connect to the configuration database
  
  Resolution
  
  For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  944267

  (http://support.microsoft.com/kb/944267/ )

  How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007
• Known issue 2
  
  Symptom
  
  Users are prompted for authentication when they try to browse a SharePoint site. Windows Server 2003 SP1 and Windows Server 2008 include a loopback check security feature that helps prevent reflection attacks on your computer. Therefore, authentication fails if the fully qualified domain name (FQDN) or the custom host header that you use does not match the local computer name.
  
  Workaround
  
  There are two methods to work around this issue. Use one of the following methods, as appropriate for your situation.
  
  Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
  322756

  (http://support.microsoft.com/kb/322756/ )

  How to back up and restore the registry in Windows
  
  Method 1: Specify host names (the preferred method for NTLM authentication)
  
  To specify the host names that are mapped to the loopback address and can connect to websites on your computer, follow these steps:
  1. Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
     281308

     (http://support.microsoft.com/kb/281308/ )

     Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
  2. Click Start, click Run, type regedit, and then click OK.
  3. In Registry Editor, locate and then click the following registry key:
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  4. Right-click MSV1_0, point to New, and then click Multi-String Value.
  5. Type BackConnectionHostNames, and then press ENTER.
  6. Right-click BackConnectionHostNames, and then click Modify.
  7. In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
  8. Exit Registry Editor, and then restart the IISAdmin service.
  
  Method 2: Disable the loopback check (the less-recommended method)
  
  Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
  
  The second method is to disable the loopback check by setting the DisableLoopbackCheck registry entry.
  
  To set the DisableLoopbackCheck registry key, follow these steps:
  1. Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
     281308

     (http://support.microsoft.com/kb/281308/ )

     Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
  2. Click Start, click Run, type regedit, and then click OK.
  3. In Registry Editor, locate and then click the following registry key:
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  4. Right-click Lsa, point to New, and then click DWORD Value.
  5. Type DisableLoopbackCheck, and then press ENTER.
  6. Right-click DisableLoopbackCheck, and then click Modify.
  7. In the Value data box, type 1, and then click OK.
  8. Exit Registry Editor, and then restart your computer.
  For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  926642

  (http://support.microsoft.com/kb/926642/ )

  Error message when you try to access a server locally by using its FQDN or its CNAME alias after you install Windows Server 2003 Service Pack 1: "Access denied" or "No network provider accepted the given network path"
• Known issue 3
  
  After you install this security update on a Windows Small Business Server-based computer that is running Windows SharePoint Services 3.0, in some scenarios, the SharePoint Companyweb and Central Administration pages may not be available. For more information about this issue and about how to resolve the issue, visit the following Microsoft TechNet webpage:
  http://blogs.technet.com/b/sbs/archive/2010/06/18/companyweb-and-sharepoint-central-admin-not-accessible-after-installing-kb983444.aspx

  (http://blogs.technet.com/b/sbs/archive/2010/06/18/companyweb-and-sharepoint-central-admin-not-accessible-after-installing-kb983444.aspx)
• Known issue 4
  
  This security update may appear multiple times in the Installed Updates list after you install it. This occurs because this update is applied to multiple Office applications.

Back to the top | Give Feedback

Restart information

Back to the top | Give Feedback

Security update replacement information

Back to the top | Give Feedback

Removal information

Back to the top | Give Feedback

File information

For Windows SharePoint Services 3.0, 32-bit Edition:

For Windows SharePoint Services 3.0, 64-bit Edition:

Back to the top | Give Feedback