Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

8.5.1 SP2 Install Issue

I've started to patch my 5 servers (4 pollers, 1 NPM) to SP2 and so far after the 1st 2 pollers have been patched my Alerting Service will not start. I tried to run the patch again, reboot the server, etc and I have not been able to get the service to run. I see this in the event log :

Event Type:    Error
Event Source:    AlertingEngine
Event Category:    None
Event ID:    0
Date:        11/30/2007
Time:        9:19:37 PM
User:        N/A
Computer:    PRDKCWSORIPOL02
Description:
2007-11-30 21:19:37,895 [MainTaskThread] ERROR All - Error in TaskManager loop -
EXCEPTION STACK: --> Thread was being aborted. : mscorlib :    at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
   at AlertingEngine.SWAlertingEngine.TaskManager();;;

Event Type:    Information
Event Source:    AlertingEngine
Event Category:    None
Event ID:    0
Date:        11/30/2007
Time:        9:20:04 PM
User:        N/A
Computer:    PRDKCWSORIPOL02
Description:
2007-11-30 21:20:04,957 [MainTaskThread] INFO All - Alert Engine Starting. Running Version 2.0.2844.28637.

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

Event Type:    Information
Event Source:    AlertingEngine
Event Category:    None
Event ID:    0
Date:        11/30/2007
Time:        9:21:36 PM
User:        N/A
Computer:    PRDKCWSORIPOL02
Description:
2007-11-30 21:21:36,142 [MainTaskThread] INFO All - Alert Engine Stopping

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

I'm stopping until this can be fixed.

BB

Find more posts tagged with

Accepted answers

All comments

FormerMember

Did you start with the main NPM poller? One of the changes in SP2 is that the Alerting Engine service is now disabled by default on the Hot Standby, Additional Website and Additional Poller installs to reduce database contention. Consequently, the alert engine will only work on the main NPM poller.

BryanBecker

Wow...news to me. Did I just miss that in the documentation or something? It would be nice if the configuration wizard would not have the Alerting Engine as an option to check under services. Also...it is still seen under windows services...shouldn't that just remove it totally so there is not confusion?

I always upgrade my pollers 1st and then the NPM server last. I'll finish with the patches.

When this is complete should I even see the Alert Engine Service listed on any of my remote pollers? What I'm seeing now is I have upgraded the NPM server. Then I upgraded my 2 remaining pollers. On those 2 pollers I still see the Alert Enginer Service installed and running after the patch was applied. Should I uninstall that server?

Thanks.

BB

FormerMember

It's in the release notes, which we post on Thwack with the announcement and which is included in the zip file with the SP itself. Of course, we list quite a few things in those notes, and it's easy to miss any given item.

- The Alerting Engine service is now disabled by default on the Hot Standby, Additional Website and Additional Poller installs to reduce database contention

vhcato

OK, I misinterpreted the notation in the release notes. I took "disabled by default" to mean that it was disabled, but still available for use if the need arises; not that it was completely unusable. We actually downgraded the SW TFTP server we had running on our NPM server to an earlier release that supported sub-directories and it blew up NPM. In the interim, we were able to install the alerting service on one of our additional pollers, just so we could at least receive alerts until we get the Orion host server working again. It sounds as if had we had SP2 installed, that would not have been an option.

Bryan, aside from this, have you experienced any issues so far with SP2?