Re: Alerts "hangs" in the queue

Tech-Archive recommends: Fix windows errors by optimizing your registry

Usual culprits

SharePoint Time Service not running (your re-boot should have started it
though)

Virus Checker software blocking port 15 (I think it's 15) (your re-boot
wouldn't clear that)

Engelbert

"Stian" <stisve@xxxxxxxxxxxxxxxxxx> wrote in message
news:40305877-4560-4D02-92C7-8C23D7647F7F@xxxxxxxxxxxxxxxx
Recently we've received comments from our users that they do not receive
alerts any longer. So I checked "Manage Alerts Settings" under Site
Settings,
and found that 184 alerts were queued up !
Tried a reboot of both the backend & the frontend servers this weekend, to
see if that would solve any hanging services - but without any luck.

In the Event Viewer on the frontend server I found a couple of error
messages related to the SP Alert service:

Event Type: Error
Event Source: SharePoint Portal Alert Service
Event Category: None
Event ID: 3524
Description:
SharePoint Portal Alerts Notification Service Failure
<More information is available in the diagnostic logs on the Configure
Diagnostic Settings page in SharePoint Portal Server Central
Administration.>

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

and:

Event Type: Error
Event Source: SharePoint Portal Alert Service
Event Category: None
Event ID: 161
Description:
The XSL file 'C:\Program Files\SharePoint Portal
Server\DATA\Alerts\1033\AlertNewsLetterNotification.xsl' cannot be loaded.
Verify that the file exists, and check the file for potential problems.
<More information is available in the diagnostic logs on the Configure
Diagnostic Settings page in SharePoint Portal Server Central
Administration.>

There are also error messages identical to the one above but with these
xsl
files mentioned:

AlertCreationConfirmation.xsl
AlertResultNotification.xsl
AlertAutoDeactivationNotification.xsl

There's nothing on it at the Help and Support Center, and the Diagnostic
logs are pretty cryptic to me.

I do, somehow, believe that this might be related to the two test Portal
Sites that we once had - that I deleted - first from the IIS, and then
just
deleted the databases. When I tried to delete them from SharePoint Portal
Server Central Administration > Manage Portal Sites, I get this message:
"Cannot open database requested in login 'TestRest1_SITE'. Login fails.
Login failed for user 'Domain\Useraccount'."
which is kind of logical, as the database don't exist any longer..

But if it has any relations to the failing Alert services - I don't know.

Do any of you have some ideas to what may solve this?.. And, any ideas on
how to completely remove the Portal Sites, when the databases already has
been deleted?

Thanks!


.

Relevant Pages

  • Re: site usage report / site alert
    ... The settings are enabled. ... I see the logfiles in the folder. ... > Check Enable Logging and Usage analysis processing. ... >> You will receive alerts in e-mail. ...
    (microsoft.public.sharepoint.windowsservices)
  • TrunkPCR version 0.89.242 Now Available
    ... Volume,Squelch,IF Shift settings. ... Channel Display Grid that allows editing of channel ... Group Alerts now display correct Group Color. ...
    (rec.radio.scanner)
  • Alerts "hangs" in the queue
    ... So I checked "Manage Alerts Settings" under Site Settings, ... messages related to the SP Alert service: ... how to completely remove the Portal Sites, when the databases already has ...
    (microsoft.public.sharepoint.portalserver)
  • Re: WSS Rocks :) one question on alerts
    ... > You can do what you wish John, it's just not done through alerts. ... Modify Columns and Settings in theleft hand column ... In the General Setting section choose Change General Settings ... > works you can also create alerts from the search engine, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Alerts and Email
    ... Otherwise search the WSS FAQ with "alerts". ... I have configured my mail settings in both ... > the sharepoint general settings and in the sharepoint virtual server ...
    (microsoft.public.sharepoint.windowsservices)