Commvault: Agent install fails on Windows 2016 Core

We just installed Windows 2016 CORE. As recommened you typically should install all available Windows Updates before you move forward and install other software.

When we started to install Commvault File Agent and Virtual Server Agent setup failed with errors in eventlog and never completed. If you search Application event log you will find two errors logged:

Log Name: Application Source: .NET Runtime Date: 8/3/2017 3:59:44 PM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: HOST1.example.local Description: Application: setup.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ComponentModel.Win32Exception

Exception Info: System.DllNotFoundException
at MS.Internal.NativeWPFDLLLoader.LoadNativeWPFDLL(UInt16*, UInt16*)
at MS.Internal.NativeWPFDLLLoader.LoadCommonDLLsAndDwrite()
at .CModuleInitialize.{ctor}(CModuleInitialize*, Void ())
at .?A0x78f04fc8.CreateCModuleInitialize()
at .?A0x78f04fc8.??__E?A0x78f04fc8@cmiStartupRunner@@YMXXZ()
at ._initterm_m(Void* ()*, Void* ()*)
at ..LanguageSupport.InitializePerAppDomain(.LanguageSupport*)
at ..LanguageSupport._Initialize(.LanguageSupport*)
at ..LanguageSupport.Initialize(.LanguageSupport*)

Exception Info: .ModuleLoadException
at ..LanguageSupport.Initialize(.LanguageSupport*)
at ..cctor()

Exception Info: System.TypeInitializationException
at InstallCommon.CommonUtils.ShowMessageWithLogLink(System.String, System.Object[])
at InstallerBA.InstallerBootstrapperApplication.Run()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Event Xml:

1026
2
0
0x80000000000000

464
Application
HOST1.example.local

Application: setup.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception

Exception Info: System.DllNotFoundException
at MS.Internal.NativeWPFDLLLoader.LoadNativeWPFDLL(UInt16*, UInt16*)
at MS.Internal.NativeWPFDLLLoader.LoadCommonDLLsAndDwrite()
at <Module>.CModuleInitialize.{ctor}(CModuleInitialize*, Void ())
at <Module>.?A0x78f04fc8.CreateCModuleInitialize()
at <Module>.?A0x78f04fc8.??__E?A0x78f04fc8@cmiStartupRunner@@YMXXZ()
at <Module>._initterm_m(Void* ()*, Void* ()*)
at <Module>.<CrtImplementationDetails>.LanguageSupport.InitializePerAppDomain(<CrtImplementationDetails>.LanguageSupport*)
at <Module>.<CrtImplementationDetails>.LanguageSupport._Initialize(<CrtImplementationDetails>.LanguageSupport*)
at <Module>.<CrtImplementationDetails>.LanguageSupport.Initialize(<CrtImplementationDetails>.LanguageSupport*)

Exception Info: <CrtImplementationDetails>.ModuleLoadException
at <Module>.<CrtImplementationDetails>.LanguageSupport.Initialize(<CrtImplementationDetails>.LanguageSupport*)
at <Module>..cctor()

And another error with

Log Name: Application Source: Application Error Date: 8/3/2017 3:59:44 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: HOST1.example.local Description: Faulting application name: setup.exe_Commvault ContentStore, version: 11.80.80.0, time stamp: 0x52974fc4 Faulting module name: KERNELBASE.dll, version: 10.0.14393.1378, time stamp: 0x594a13be Exception code: 0xe0434352 Fault offset: 0x000da9f2 Faulting process id: 0x188c Faulting application start time: 0x01d30c60beb756ac Faulting application path: C:\CVMedia\setup.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 9118f9bc-e2fd-4cfb-97d7-a14d12d19a7f Faulting package full name: Faulting package-relative application ID: Event Xml: 1000 2 100 0x80000000000000 465 Application HOST1.example.local setup.exe_Commvault ContentStore 11.80.80.0 52974fc4 KERNELBASE.dll 10.0.14393.1378 594a13be e0434352 000da9f2 188c 01d30c60beb756ac C:\CVMedia\setup.exe C:\Windows\System32\KERNELBASE.dll 9118f9bc-e2fd-4cfb-97d7-a14d12d19a7f

Contacted Commvault support and asked whats wrong and I have been told to uninstall .NET 4.7 via wusa /uninstall /kb:3186568 because of a known bug WPF window can't be loaded after you install the .NET Framework 4.7 on Windows Server 2016 (Server Core). Followed these suggestion and the setup completed. Commvault noted that I could install the NET 4.7 after the installation, but I stayed away as you never know if you may need to uninstall and reinstall again later. These .NET 4.7 uninstall takes a really long time and requires a reboot, too.

A week later on 8th of August I had the unlucky job to install another Hyper-V cluster with latest updates and as you may expect I have already blocked the .NET 4.7 update in WSUS just to make sure I'm not installing it on CORE servers again. But there was the 2017-08 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4034658) now. It has some important iSCSI fixes that you should better install if you run iSCSI storage. After this is installed on a brand new Windows 2016 CORE the Commvault Agent installation fails, too.

Log Name: Application Source: .NET Runtime Date: 8/9/2017 2:45:21 PM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: HOST1.example.local Description: Application: setup.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ComponentModel.Win32Exception

Exception Info: System.DllNotFoundException
at MS.Internal.NativeWPFDLLLoader.LoadNativeWPFDLL(UInt16*, UInt16*)
at MS.Internal.NativeWPFDLLLoader.LoadCommonDLLsAndDwrite()
at .CModuleInitialize.{ctor}(CModuleInitialize*, Void ())
at .?A0x4676cc04.CreateCModuleInitialize()
at .?A0x4676cc04.??__E?A0x4676cc04@cmiStartupRunner@@YMXXZ()
at ._initterm_m(Void* ()*, Void* ()*)
at ..LanguageSupport.InitializePerAppDomain(.LanguageSupport*)
at ..LanguageSupport._Initialize(.LanguageSupport*)
at ..LanguageSupport.Initialize(.LanguageSupport*)

Exception Info: .ModuleLoadException
at ..LanguageSupport.Initialize(.LanguageSupport*)
at ..cctor()

Event Xml:

1026
2
0
0x80000000000000

604
Application
HOST1.example.local

Application: setup.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception

Exception Info: System.DllNotFoundException
at MS.Internal.NativeWPFDLLLoader.LoadNativeWPFDLL(UInt16*, UInt16*)
at MS.Internal.NativeWPFDLLLoader.LoadCommonDLLsAndDwrite()
at <Module>.CModuleInitialize.{ctor}(CModuleInitialize*, Void ())
at <Module>.?A0x4676cc04.CreateCModuleInitialize()
at <Module>.?A0x4676cc04.??__E?A0x4676cc04@cmiStartupRunner@@YMXXZ()
at <Module>._initterm_m(Void* ()*, Void* ()*)
at <Module>.<CrtImplementationDetails>.LanguageSupport.InitializePerAppDomain(<CrtImplementationDetails>.LanguageSupport*)
at <Module>.<CrtImplementationDetails>.LanguageSupport._Initialize(<CrtImplementationDetails>.LanguageSupport*)
at <Module>.<CrtImplementationDetails>.LanguageSupport.Initialize(<CrtImplementationDetails>.LanguageSupport*)

Exception Info: <CrtImplementationDetails>.ModuleLoadException
at <Module>.<CrtImplementationDetails>.LanguageSupport.Initialize(<CrtImplementationDetails>.LanguageSupport*)
at <Module>..cctor()

And the second error:

Log Name: Application Source: Application Error Date: 8/9/2017 2:45:21 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: HOST1.example.local Description: Faulting application name: setup.exe_Commvault ContentStore, version: 11.80.80.0, time stamp: 0x52974fc4 Faulting module name: KERNELBASE.dll, version: 10.0.14393.1532, time stamp: 0x5965adf8 Exception code: 0xe0434352 Fault offset: 0x000da9f2 Faulting process id: 0x18bc Faulting application start time: 0x01d3110d59655f37 Faulting application path: C:\CVMedia\setup.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 52aec55e-294f-4cdd-88e1-ec90122e063a Faulting package full name: Faulting package-relative application ID: Event Xml: 1000 2 100 0x80000000000000 605 Application HOST1.example.local setup.exe_Commvault ContentStore 11.80.80.0 52974fc4 KERNELBASE.dll 10.0.14393.1532 5965adf8 e0434352 000da9f2 18bc 01d3110d59655f37 C:\CVMedia\setup.exe C:\Windows\System32\KERNELBASE.dll 52aec55e-294f-4cdd-88e1-ec90122e063a

This means you now need to uninstall the 2017-08 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4034658), too. Run wusa /uninstall /kb:4034658 to remove it. As before this takes much longer... do not forget to block this in WSUS. The August 2017 service stack update can be installed without any known issues. You can also install the 2017-07 Cumulative Update for Windows Server 2016 for x64-based Systems without issues.

I made Commvault aware that the rollup is causing this issue now, too. But a week after this broken rollup has been released by Microsoft, this is still not documented and Commvault has not yet forwarded this new info to Microsoft. I have no idea as of now when Microsoft will fix the issue in their rollups. So the only ugly workaround is to remove these packages and stay away from them.

Microsoft has released a new rollup August 16, 2017—KB4034661 (OS Build 14393.1613) that fixes the issue. Any newer rollup solves the issue, too.

History:

17.08.2017: Microsoft has released a new rollup August 16, 2017—KB4034661 (OS Build 14393.1613) that fixes the issue.
15.08.2017: Published article
09.08.2017: Setup fails with 2017-08 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4034658).
03.08.2017: Setup fails with .NET 4.7 installed.

Rating

Commvault: Agent install fails on Windows 2016 Core

Tags