Article ID: 931008
Article Last Modified on 12/3/2007
APPLIES TO
- Microsoft Windows Small Business Server 2003 Premium Edition, when used with:
- Microsoft Windows SharePoint Services 3.0
Notice
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
You perform an in-place upgrade from Microsoft Windows SharePoint Services 2.0 to Microsoft Windows SharePoint Services 3.0. When you try to perform a search query, you receive the following error message:
CAUSE
This problem occurs when the Windows SharePoint Services 2.0 server application pool account is configured to use the NETWORK_SERVICE account.
RESOLUTION
How to obtain the hotfix
This issue is fixed in the Windows SharePoint Services 3.0 Hotfix Package that is dated April 12, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
934790 Description of the Windows SharePoint Services 3.0 hotfix package: April 12, 2007
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To enable this hotfix, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Global\Gathering Manager
- Double-click AllowNetworkService.
- In the Edit DWORD Value dialog box, type 1 under Value data, and then click OK.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kbqfe kbprb kbexpertiseinter kbhotfixserver KB931008