Error: "exception - Method not found" in PolicySync.exe log file

Version 7

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.xLANDESK Endpoint Manager 2017.x

    Note: If you are using  Ivanti EPM to patch your devices, this issue has been corrected and is only applicable if MS15-092 was installed on your device prior to 7 Dec 2015 and .Net Framework 4.6 is NOT installed on your Windows 8.1 device. From an Ivanti perspective, our Patch and Compliance definition's detection logic has been updated to check for the existence of .NET Framework 4.6 prior to detecting the patch as a vulnerability to the device.




    When attempting to synchronize policies through portal manager on a Windows 8.1 device the following error is displayed:




    If you're distributing a push or required policy file over to the target, the package won't appear in portal manager. The policysync.exe log file will contain the following error message:

    GetAPMServiceResponse: exception - Method not found: 'Void System.Diagnostics.Tracing.FrameworkEventSource.BeginGetResponse(System.Object, System.String)'





    This issue is related to the installation of a Microsoft vulnerability:

    MS15-092_MSU (KB3083185): Vulnerabilities in the .NET Framework could allow elevation of privilege: August 11, 2015



    Microsoft allows the installation of this vulnerability without the .Net 4.6 framework being installed.


    To check for the installation of Microsoft hotfix (KB3083185), conduct the following from an admin command prompt (there are a number of ways to do this, this is simply one method):


    systeminfo > systeminfo.txt



    This will generate a "systeminfo.txt" file from the directory you initiated the command from. Please open up the output file and search for the KB to verify its existence.





    Install Microsoft .Net Framework 4.6 to your affected client device.


    .Net Framework 4.6 Installer


    If you do not want to install .Net Framework 4.6 in your environment, please ensure your LANDESK patch content is up to date and re-scan your environment to avoid detection of the vulnerability.