Error 0x8007007e/0x80020009 while connecting to WSUS Server

Error 0x8007007e/0x80020009 while connecting to WSUS Server

Summary

You are under Patching menu in SVM2018 and you attempt to connect to your WSUS/SCCM instance using the connection dialog in SVM. The SVM display connection error 0x8007007e and error message "Unable to load DLL "SusNativeCommon.dll" :: The specified module could not be found. (Exception from HRESULT: 0x8007007E)"

Symptoms

While connecting the SVM patching module to WSUS or SCCM server instance, SVM displays the following error message:

"Error connecting to WSUS Server:Error : -2147352567 , (0x80020009) : Exception occurred., In 'AdminProxy_t.invoke' Code: -2146233052 Unable to load DLL 'SusNativeCommon.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) --> System.DllNotFoundException: Unable to load DLL 'SusNativeCommon.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args) at Plugin.DotNetType<Microsoft::UpdateServices::Administration::AdminProxy>.invoke(DotNetType<Microsoft::UpdateServices::Administration::AdminProxy>* , PluginBstr* name, Arguments* args, PluginMarshal* marshal)"

Cause

The machine which has the SVM Patching Plugin installed should contain the file "SusNativeCommon.dll" under C:\Windows\SysWow64\ directory. 

For some reason, the host where the SVM web interface and the Patching plugin for IE is installed does not have this file present . This problem has been seen on specific Windows 10 builds. This file is required for any publishing to occur to WSUS API and it represents a local system problem, and a missing SVM requirement (and missing WSUS publishing requirement) on the host. 

Steps To Reproduce

Delete the "SusNativeCommon.dll" under C:\Windows\SysWow64 to replicate the problem.

Resolution

Move the SVM installation to another machine which was predetermined to have the file present under %Windows% directories.

Workaround

Alternatively, you can try copy/pasting the file from another machine which has it, but you should make sure to copy 32-bit file in the 32-bit %Windows% directory and the 64-bit into x64 %Windows% path.

Was this article helpful? Yes No
No ratings
Version history
Revision #:
3 of 3
Last update:
‎Oct 10, 2019 06:53 PM
Updated by:
 
Contributors