Microsoft KB Archive/305354

= FIX: Paging an Operator May Not Work After You Apply Service Pack 1 =

Article ID: 305354

Article Last Modified on 10/15/2002

-

APPLIES TO


 * Microsoft SQL Server 2000 Service Pack 1

-



This article was previously published under Q305354



BUG #: 355093 (SHILOH_BUGS)



SYMPTOMS
Operators that are configured for notification through a pager e-mail message, which you can see in the Pager e-mail name textbox in SQL Agent, may not work after you apply SQL Server 2000 Service Pack 1 (SP1).

No error messages occur and you should still see a dialog box that indicates that the message was sent successfully. Nevertheless, the operator is never notified.

If the same e-mail address is specified in the E-mail name textbox and sent to an e-mail operator, the notification is successful.

This behavior does not occur in SQL Server 2000.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack



WORKAROUND
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

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.

To work around this behavior, follow these steps to add two values to the Registry:  Start the Registry Editor (Regedt32.exe). If SQL Server 2000 is the default instance then:  Locate and expand the following key in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent

 On the Edit menu, click Add Value, and then type the following name: AlertPagerToTemplate

  For the value type select: REG_SZ </li> For the string in the value, type: <#A#>

</li></ol>

Repeat the steps and add a second value in the following manner:

<ol style="list-style-type: lower-alpha;"> On the Edit menu, click Add Value, and then type the following name: AlertPagerSubjectTemplate

</li>  For the value type select: <pre class="fixed_text">REG_SZ </li> For the string in the value, type: <#S#>

</li></ol>

If SQL Server 2000 is not the default instance then:

<ol style="list-style-type: lower-alpha;"> Locate and expand the following key in the registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\'Instance Name'\SQLServerAgent

NOTE: Replace 'Instance Name' with the name of the instance.

</li> On the Edit menu, click Add Value, and then type the following name: AlertPagerToTemplate

</li>  For the value type select: <pre class="fixed_text">REG_SZ </li> For the string in the value, type: <#A#>

</li></ol>

Repeat the steps to add the second value in the following manner:

<ol style="list-style-type: lower-alpha;"> On the Edit menu, click Add Value, and then type the following name: AlertPagerSubjectTemplate

</li>  For the value type select: <pre class="fixed_text">REG_SZ </li> For the string in the value, type: <#S#>

</li></ol> </li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000 Service Pack 1.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Additional query words: Operator Pager Paging SP1 SQL 2000 2k Notification

Keywords: kbbug kbfix KB305354

-

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

© Microsoft Corporation. All rights reserved.