Sharepoint Alerts Not Working after deleting database
From: sean.swords
Newsgroups: microsoft.public.sharepoint.portalserver
Subject: Sharepoint Alerts Not Working
Date: 5 Dec 2005 03:24:16 -0800
Hi,
Recently, I deleted some old profile, site and server databases that we were not using anymore. After I did this, my alerts topped working and I started getting the following messages in my SPSNOTIFICATIONSERVICE.LOG file:
001C50C8 UNK 00000000 0000160C Alerts are active for the following
site:
Site Name: 'CIL' Site ID: '2a3c4d05-672f-443e-bd65-ce5950adced4' SMTP
Server: 'sps1.cil.ie(Normal)' Loaded templates:
D:\SharePoint Portal
Server\DATA\Alerts\1033\AlertAutoDeactivationNotification.xsl
D:\SharePoint Portal
Server\DATA\Alerts\1033\AlertResultNotification.xsl
D:\SharePoint Portal
Server\DATA\Alerts\1033\AlertCreationConfirmation.xsl
D:\SharePoint Portal
Server\DATA\Alerts\1033\AlertNewsLetterNotification.xsl<BR>
001C50C8 UNK 00000000 0000160C AppDomain:
SPSNotificationService.exe<BR>
001C50C8 UNK 00000000 0000160C Exception thrown while getting web properties data from datareader: System.InvalidOperationException:
Unable to load web information from STS database
at
Microsoft.SharePoint.Portal.WebControls.SiteInfo.GetNewSiteInfo(PortalC
ontext
ctx, Boolean fAllowPortalApplicationRefresh)<BR>
Our alerts do not now work, but they are still going in the queue, just not actually making it to the users. I think the problem is that there are still alerts tied to database tables which no longer exist. Has anybody else had this problem, and how did you go about fixing it?
Thanks,
Swordsy.
*************************************
From: sean.swords
Newsgroups: microsoft.public.sharepoint.portalserver
Subject: Re: Sharepoint Alerts Not Working
Date: 5 Dec 2005 08:07:40 -0800
Sorted this one out myself. The problem was that I still had config db references to old profile, site and serv databases which no longer existed. The solution was to delete all references to the old databases and virtual server from the tables in the config db, they are joined on the key Portalsites.portalsiteID. The tables affected are:VirtualServers, Portalsites, Sites and Databases. As soon as I deletet the offending record from table Portalsites, all of my alerts came flooding through.
Cheers