Wednesday, March 29, 2017

EventID 34103 - Web TestConfig Error, Web Availability Test Not Running.

I ran into an issue the other day while researching an error in SCOM on one of my servers running as a watcher for Web availability application monitoring. What I noticed was in the Operations Manager event log different event ID 34103 entries specifying TestConfig failures.


The Web Test Module has some invalid configuration.
Config Context: TestConfig
Error: 0x80004005
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.WebApplicationTest.WebTestProbe.Performance.CollectContentTime
Instance name: Demo-Visant [Monitoring Pool - Demo]
Instance ID: {ECFB7B7D-B242-C2EB-7470-6181DED0CFCA}
Management group: Jostens_ENT_Prod

Come to find out this was due to as stated a configuration error with the content matching. We utilize the Does not match standard expression for a large number of sites. Which typically you use an enclosed fail message or content such as (FAIL) or along those lines. What had happened was when the test was created one of the enclosures was missing so it was FAIL) instead.
SCOM still allowed the test to be saved and acting like it was monitoring the site without issues, no errors were shown in the console saying it was failing and the URL health state showed green.

To help overcome this issue I build a new Manual Reset Rule, that would check the Operations Manager log for the following conditions.

EventID -eq 34103
Source -eq Health Service Modules
Event Data- $Data/Params/Param[5]$ -eq TestConfig

That would create a critical alert with a customer error stating the test was not configured properly and needs to be updated. Thus informing whomever is watching the console of the issue. I went a step further and also created a notification alert that goes to the SCOM Admins to follow up on the issue.

No comments:

Post a Comment

SCOM 2016 Update Rollup 3 Released!

Microsoft released the SCOM 2016 Update Rollup 3 which includes a number of fixes particulary a fix for the SCOM agent crashing IIS .NET 2....