Console Initialization Error: Could not load file or assembly 'AmpLicensingProxy'

Version 6

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6


    As seen when you attempt to login to the console (local or remote)

    Console Initialization Error:  System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IO.FileNotFoundException: 
    Could not load file or assembly 'AmpLicensingProxy, Version=, Culture=neutral, PublicKeyToken=null' or one of its dependencies. 
    The system cannot find the file specified. 
    File name: 'AmpLicensingProxy, Version=, Culture=neutral, PublicKeyToken=null' at LANDesk.ManagementSuite.MBSDK.MBSDK.GetRights(Boolean clearCache) 
    WRN: Assembly binding logging is turned OFF. 
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. 
    Note: There is some performance penalty associated with assembly bind failure logging. 
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. 
       --- End of inner exception stack trace ---.


    The error on a German console.

    Konsoleninitialisierungsfehler: System.Web.Services.Protocols.SoapException: Die Anforderung konnte vom Server nicht verarbeitet werden. ---> System.Data.OleDb.OleDbException: Invalid object name 'ConsoleUser'. bei LANDesk.ManagementSuite.MBSDK.MBSDK.GetRights(Boolean clearCache) --- Ende der internen Ausnahmestapelüberwachung ---.



    More Info:

    The error message seem to indicate that a file [AmpLicensingProxy] could not be loaded.While this is technically true, it is not specific to AmpLicensingProxy.



    This is caused by the MBSDK not having the access it needs.  Since a variety of issues can interfer with the MBSDK, a variety of solutions exist.



    One or more of these *may* work for you.  All are not required.

    • add the local "NETWORK SERVICE" user to "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files" and "install:\Program Files (x86)\LANDesk\ManagementSuite" with FULL CONTROL
    • If you have the database on a seperate SQL instance, be sure "hostname\instance_name" is set as the database server name
    • Clear the temporary ASP.NET files.
    • reboot the SQL server followed by the core server