Recent installs of VMM 2016 have shown nice improvements over 2012, especially a much needed performance boost with storage operations through SMI-S.
Our latest SMI-S provider from NetApp (for ontap 9.1) in combination with VMM 2016 – seems to be light years ahead of 2012 R2. It’s responsive and carries out tasks in a tenth of the time that VMM 2012 took with ontap 8.
All issues with the SMI-S provider going unresponsive have been found to be due to a little service running in windows:
This little chap seems to randomly keel over – with system and application logs revealing nothing as to why.
- Log Name: Application
Source: Application Error
Date: 28/04/2017 17:44:20
Event ID: 1000
Task Category: (100)
Faulting application name: svchost.exe_MSStrgSvc, version: 10.0.14393.0, time stamp: 0x57899b1c
Faulting module name: concrete.dll, version: 10.0.14393.0, time stamp: 0x57899a8c
Exception code: 0xc0000005
Fault offset: 0x0000000000002eb0
Faulting process ID: 0xe38
Faulting application start time: 0x01d2c03e31b6c56d
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: c:\windows\system32\concrete.dll
Report ID: 1bc955fe-6a3b-469b-8c0c-de7992f3858d
Faulting package full name:
Faulting package-relative application ID:
I have logged it with premier support – they know about it, but a fix isn’t available as yet. Frustrating, but not the end of the world – just start the service again, wait 2 mins, then refresh the provider in SCVMM – all is good!
As soon as a fix is available – I will post an update here.
- WinCXE is planning of hotfix for Windows 10 version 1607. The KB article ID is going to be 4019472.
This should be available towards the end of May 2017.