I wasn't sure if it was Veeam related or not or if it was another product (Paesller PRTG) Veeam and these guys have the best support around so I figured between them and you guys and MS techNet. I believe we can figure this one out.
For the back story. Installed Veeam on VM, as All-in-One, works great.
Couldn't monitor VNXe SAN via SNMP or otherwise (*Cough* VNXe sucks *Cough*). So as a work around decided to just monitor the IP addresses of the storage network (our monitoring server doesn't have legs in those subnets, and for good reason) The only server that does, Veeam! for backup purposes. So we decided to install the PRTG remote probe. All good!
However I noticed that I would get these strange CPU spike (They were distinguishable, like the same pattern every time I caught it, and when I did I discovered it was mscrosvw.exe). So Googles to the rescue... or not... after much research it seemed to make sense why I only caught it when I did, but what didn't match was the fact it was suppose to finish optimizing then go away, instead the same pattern emerged day after day, even after reboot. This is when I figured something is wrong. So I took to technet. For full details seemy TechNet Post https://social.technet.microsoft.com/Forums/windowsserver/en-US/d0a17c5a-97b6-4780-a22f-b104b7f2d248/clr-optimization-service-odd-behaviour?forum=winservergen#d0a17c5a-97b6-4780-a22f-b104b7f2d248
. (Yes I am all over the place when it comes to fourms, I'm even on IRC, hope to see some of you on freenode someday)
after I ran the manual command to run and finish the process. I discovered it was complaining about a "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."
Does Veeam use this SQL path, or not? I'm just trying to track down which of the two products uses it.