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

APM2 Windows Service Monitors not working on windows 2003 server with no SP

Hi all,
seems the Windows Service Monitor in APM2 cannot handle a windows 2003 server that doesnt have SP1(or 2) installed. The error I get is - "Unexpected Error Occcured. Value cannot be null. Parameter Name: servicePackVersion"

It was working fine in APM1 - but since the upgrade the few servers I have that are running without SP1 fail to work with the above error. I can't upgrade the servers to SP1 since the application running on them doesn't support SP1 (and crashes horribly if you try to). We're already hassling the vendors to fix the issue (have been for a year!). It's horrible proprietary software so we're stuck on non-sp1 until they fix it. My current workaround is to switch to WMI or SNMP monitoring of the process - but then I lose the service name monitoring ability (some processes are running as the generic svchost.exe).

Any fix for this?

Thanks!

Find more posts tagged with

Accepted answers

All comments

FormerMember

This is a bug, and we've slated the fix for SP1, which should be available fairly soon. You should open a ticket with Support and reference this post so that we'll be sure to check that our fix works in your environment.

award147

I am having the same problem, any news on the service pack release?

Alan

PeterLyttle

I'm also getting the same issue, anyone have any news?

Thanks,
Peter