That’s right, today we are crossing to the dark side of the monitoring moon to discuss a shiny new toy I’ve been working with for the last week or so. As with any new product installation and configuration there are a number of small hurdles that require jumping to get the software working and in regular roshamboot style I’d like to share solutions to those hurdles.
It’s also worth noting that I’m using Windows Server 2012, so you may need to adjust accordingly if you are using Server 2008.
Can’t clear ASP.NET 4.X registration check
Aka: The ASP.NET 4.X Handler is not registered with IIS
So you’ve installed the .NET 4.0 application components as well as the HTTP Activation roles from the Features and Roles menu in the server dashboard and you’re furiously clicking verify and wondering what on earth you’ve done wrong.
Fix: If you have installed the above two components then you’ve done nothing wrong. You just need to restart the installer because it doesn’t seem to properly verify those components. Once you get back to the requirements screen, low and behold, it has passed!
Server Error in ‘/OperationsManager’ Application.
This error message took a little more poking around and trial and error to resolve, I actually came across the same problem with a different message in System Center Orchestrator as well. If we check the eventlog we will find a few different errors one of which (if you are experiencing the same problem) will be something like this:
Process information: Process ID: 5376 Process name: w3wp.exe Account name: IIS APPPOOLOperationsManager Exception information: Exception type: HttpCompileException Exception message: (0): error CS0016: Could not write to output file 'c:WindowsMicrosoft.NETFramework64v4.0.30319Temporary ASP.NET Filesoperationsmanager41359ad1e7f4add4App_global.asax.r3omjpfz.dll' — 'Access is denied. ' at System.Web.Compilation.AssemblyBuilder.Compile() at System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp) at System.Web.Compilation.BuildManager.CompileGlobalAsax() at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
Fix: The path in the eventlog message is actually a little bit misleading. You need to actually change permissions on C:Temp, so bring up the permissions window and add NETWORK SERVICE and IIS_IUSRS with Read/Write permissions to your C:Temp directory and that should make this particular problem go away!
I’m still not exactly sure why though, I changed this on a hunch as I’ve seen it solve similar errors before. I suspect there may be junctions at play, though I didn’t really investigate… If you happen to know the real reason, leave a comment as it would be interesting to find out.
Using case insensitive Regex in SCOM
This very obviously has nothing to do with installation but I dare say soon after installation when you begin creating your first groups you are more than likely going to bump into the issue that the regex matches by default are case sensitive. In MS Regex you can use the characters ?i to set something to be case insensitive, you can also use this in a global context by using the colon.
So instead of doing:
This will make the full pattern match case insensitive. You can find more information about regex options here: http://msdn.microsoft.com/en-us/library/az24scfc.aspx
Happy Regexing!comments powered by Disqus