Hey All,
I wasn't exactly sure where to place this since it fall sunder .NET more than anything.
So the background, I have this one Windows Server 2008 R2 VM I was using for my backup server. It been a great server. So lately it was determined that we were having some extreme difficulties managing to monitor our SAN. Due to technical deficiencies within
the design of the firmware. So we decided to take a simple approach (at least for simple network moniroting of our Storage network.
Since this backup server was the only server to have network legs in these locked down network segments we decided to add PRTG's Remote Probe software, then have the backup server have ping sensors in place to check each IP in said subnet. This work around
provides at least active alerts on hose networks, but doesn't help much with other monitoring requirements. Anyway!
I noticed after I installed the Prob I would get this very odd spike in my CPU usage, and I would only catch it when I'd leave teh console open and not use it, just have task manager open. To which I discovered it was a process mscrosvw.exe which from googling
shows its part of this CLR optimization service. After more research and analysis I figured it was normal as the way I'd catch the usage spike. However!
This is where it gets weird after a couple days I noticed the processes wouldn't go away, unlike what was said about the process once it was done optimizing it would go away. I kept seeing the same CPU spike, all the time, almost as if it would trigger,
and something would seem to fail and cause the process to be stuck repeating. I attempted to reboot the server and to my dismay it still happens.
So Looking at
this and
this.
I decided to see what I could do to resolve this and get that pesky process out of my task manager once n for all (well at least till patch Tuesdays, or manual trigger) A couple things to note..
1) In my Windows Dir I have multiple instances of .NET version installed.
(1.0.3705, 1.1.4322, 2.0.50727, v3.0, v3.5, v4.0.30319) based on the folders under the framework DIR.
2) I wasn't sure which version the remote probe used or had as a dependency and have reached our to Paesller support for comment. Since I had no "proof" of this issue before the remote probe install they seem to not want to be the ones to take
blame. Also cause .NET isn't managed by them, it's MS. So here I am....
Anyway... reading the second blog I attempted to clear all queried items manually. here were my results ( I assumed .NET 4 as being used by PRTG as its the most current one on the system)...
"
Microsoft (R) CLR Native Image Generator - Version 4.0.30319.36365
Copyright (c) Microsoft Corporation. All rights reserved.
Failed to load the runtime. (Exception from HRESULT: 0x80131700). Assembly c:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\Microsoft.SqlServer.ForEachFileEnumeratorWrap.dll requires version v4.0 of the runtime to run.
Assembly will be compiled once the correct runtime is installed.
Failed to load the runtime. (Exception from HRESULT: 0x80131700). Assembly c:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\Microsoft.SqlServer.SQLTaskConnectionsWrap.dll requires version v4.0 of the runtime to run.
Assembly will be compiled once the correct runtime is installed.
Uninstalling assembly C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn
\ManagementStudio\Extensions\Application\Microsoft.SqlServer.Management.Reports.
pkgdef because of an error during compilation: The given assembly name or codeba
se was invalid. (Exception from HRESULT: 0x80131047)."
This was not the results I was expecting. Can anyone provide me some help as to what i can do to resolve this issue? and get the CLR Opt service to bugger off?