Alerts Stop Working After Migraton


 

Migrating SharePoint is a task all on its own, but not having things working correctly in production after the migration can be devastating.

Recently the issue of user alerts came up.  When migrating users were not getting existing alerts from 2003.  it did not take long to figure out this is a common problem with database migration when you change the URL of the SharePoint sites.  The good news is a quick run of an stsadm command, and it was done – we already had installed the admin pack of course.

Here is the information from Microsoft:

http://support.microsoft.com/kb/936759

 

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

SYMPTOMS

Consider the following scenario. You perform a database migration to upgrade Microsoft Windows SharePoint Services 2.0 to Microsoft Windows SharePoint Services 3.0. To do this, you deploy Windows SharePoint Services 3.0. Then, you add the content databases to the Web applications in the new Windows SharePoint Services 3.0 environment.
However, after the migration, Windows SharePoint Services 3.0 does not send e-mail notifications when content changes in a migrated list or in a migrated document library. Users experience the following symptoms:


Users do not receive e-mail notifications for existing alerts for a list or for a document library that was migrated from Windows SharePoint Services 2.0.


Users do not receive e-mail notifications for new alerts that they create for a list or for a document library that was migrated from Windows SharePoint Services 2.0. To receive e-mail notifications, the user must first delete the existing alert. Then, the user must create a new alert.

Additionally, if you enable verbose tracing, an error message that resembles the following is logged in the Uls log file:

FileNotFound Exception

Back to the top

CAUSE

This issue occurs if the URL of the Windows SharePoint Services 2.0 server differs from the URL of the Windows SharePoint 3.0 server. For example, this issue occurs if the URL of the Windows SharePoint Services 3.0 server is http://ServerNameVersion3, and the URL of the Windows SharePoint Services 2.0 server is http://ServerNameVersion2.
The ImmedSubscription table in the content database has a Siteurl column. If the value in the Siteurl column does not match the URL of the Web application, Windows SharePoint Services does not send e-mail notifications when content in a list or in a document library changes.

Back to the top

WORKAROUND

To work around this issue, use one of the following methods.

Back to the top

Method 1: Use the new "stsadm -o updatealert" command

The new stsadm -o updatealert command was released in the SharePoint Administration Toolkit. For more information and to download the toolkit, visit one of the following Microsoft Web sites, depending on the version of Windows SharePoint Services that you are running.

SharePoint Administration Toolkit x64

http://www.microsoft.com/downloads/details.aspx?FamilyId=F8EEA8F0-FA30-4C10-ABC9-217EEACEC9CE&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=F8EEA8F0-FA30-4C10-ABC9-217EEACEC9CE&displaylang=en)

SharePoint Administration Toolkit x86

http://www.microsoft.com/downloads/details.aspx?FamilyId=263CD480-F6EB-4FA3-9F2E-2D47618505F2&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=263CD480-F6EB-4FA3-9F2E-2D47618505F2&displaylang=en)

For more information, see the "Microsoft SharePoint Administration Toolkit" white paper. To do this, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=117212&clcid=0x409 (http://go.microsoft.com/fwlink/?LinkId=117212&clcid=0x409)

Advertisements
This entry was posted in MOSS Migrating. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s