Microsoft KB Archive/888809

= You receive an &quot;An error has occurred on the server&quot; error message when you click Alert Me to add an alert in a child portal site of a SharePoint Portal Server 2003 server farm that uses shared services =

Article ID: 888809

Article Last Modified on 7/14/2006

-

APPLIES TO


 * Microsoft Office SharePoint Portal Server 2003

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
In a server farm deployment of Microsoft Office SharePoint Portal Server 2003 that is configured to use shared services, you cannot add an alert to an area of a child portal site. You locate the Web page of the child portal site that displays the area, type your user name and your password to access the child portal site, and then click Alert Me. After you type your user name and your password to access the parent portal site, you receive an error message that is similar to the following:

An error has occurred on the server.



CAUSE
This problem may occur if certain data in the request that is redirected from the child portal site to the parent portal site is not retained. This problem may occur if the following conditions are true:
 * The virtual server of the parent portal site and the virtual server of the child portal site are configured to use Basic authentication.
 * You access the child portal site before you access the parent portal site.



RESOLUTION
This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest SharePoint Portal Server 2003 service pack, you do not have to install the hotfix.

Service pack information
This problem is corrected in Microsoft Office SharePoint Portal Server 2003 Service Pack 2.

To resolve this problem, obtain the latest service pack for SharePoint Portal Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889380 How to obtain the latest service pack for SharePoint Portal Server 2003

After you install the service pack, follow the steps that are listed in the &quot;Enable the hotfix&quot; section to set the NoAlertCreationRedirectToMaster registry entry and to enable the hotfix.

How to obtain the hotfix
This issue is fixed in the SharePoint Portal Server 2003 Hotfix Package November 1, 2004. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

888807 Description of the SharePoint Portal Server 2003 hotfix package: November 1, 2004

Enable the hotfix
To enable this hotfix after you install it, you must do both of the following:  Add the NoAlertCreationRedirectToMaster registry entry to the following registry subkey, and then set the registry entry to 1:

 Grant the administrator of the child server farm access to search and to index resources on the parent server farm.

To do this, follow these steps.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.  Add the NoAlertCreationRedirectToMaster registry entry, and then set the registry entry to 1. To do this, follow these steps:  Click Start, click Run, type regedit in the Open box, and then click OK. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\Software\Microsoft\SharePoint Portal Server

</li> On the Edit menu, point to New, and then click DWORD Value.</li> Type NoAlertCreationRedirectToMaster, and then press ENTER.</li> Right-click NoAlertCreationRedirectToMaster, and then click Modify.</li> Type 1 in the Value data box, and then click OK.</li> On the File menu, click Exit to quit Registry Editor.</li></ol> </li> Add the account that is configured as the portal site application pool identity of the child server farm to the SPS_WPG local group of the server that is configured as the job server for the parent server farm. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> On the job server for the parent server farm, click Start, point to Administrative Tools, and then click Computer Management.</li> Under System Tools, expand Local Users and Groups.</li> Click Groups.</li> Double-click SPS_WPG, and then click Add.</li> Type the name of the account that is the portal site application pool identity of the child server farm, click Check Names if you want to examine the name, and then click OK two times.</li></ol> </li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in SharePoint Portal Server 2003 Service Pack 2.

<div class="moreinformation_section">

MORE INFORMATION
For more information about alerts, see the &quot;Managing alerts&quot; topic in the &quot;Administration&quot; section of the Microsoft Office SharePoint Portal Server 2003 Administration Guide. The Microsoft Office SharePoint Portal Server 2003 Administration Guide (Administrator's Help.chm) is located in the Docs folder in the root of the SharePoint Portal Server 2003 CD.

Additional query words: sps

Keywords: kbregistry kbshareptportalsvr2003sp2fix kbshareptportalsvr2003presp2fix kberrmsg kbqfe kbbug kbfix kbhotfixserver KB888809

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.