Errors: "Unable to find an active license" and "The authorization file is invalid" when running inventory scan

Version 4

    Verified Product Versions

    Endpoint Manager 2016.xEndpoint Manager 2018.x


    When trying to process inventory scans, the core server will show the following error in the Application Log in the Event Viewer:
    Unable to find an active license.
    If you try to activate the core server, this error appears:
    The authorization file is invalid.
    The activation file at this location appears to be invalid. 'C:\...\authorization file.txt' Make sure an inventory scan has been run for this core server and run this utility again. Contact customer support for further assistance.





    Step 1


    1. Delete the following registry keys from the core server:
      HKLM\Software\Intel\LANDesk\Common Api
      HKLM\Software\LANDesk\Common Api
    2. Execute this file on the core server, which will initiate an inventory scan on the core:

      Program Files\LANDesk\ManagementSuite\Ldlogon\ipscan.bat
    3. Reactivate the core server through the core server activation utility:
    4. Start > Programs > LANDesk > Core Server Activation. Specify the appropriate contact name and password (and proxy settings on the proxy tab if necessary) and click Activate.

    5. After the core successfully activates, restart the LANDesk Inventory Server service. Inventory scans will now process successfully.


    If this fails the issue could be caused by Cert key was changed/missing or copied over.


    Step 2


    To Generate and install new keys:



    The following steps are done on the Core Server


    1. Open the command line and change the path to
      "C:\Program Files\LANDesk\Shared Files\keys\"
    2. There you will find the "genkey.exe" utility which creates the certificate (see genkey.log for details).
    3. The certificate is then installed and added to the Default Client configuration by "installkey.exe" (see installkey.log for details).
    4. Copy the previously backed up Certificate files over in the root of this directory (.CRT / .0 / .key -fileset).
    5. Execute the following command from this path:

    "installkey.exe "filename" "/LDMS=C:\Program Files\LANDesk\ManagementSuite\ldlogon"


    CAUTION: Instead of "filename" take the certificate file-name (as from the .CRT-file), WITHOUT the .CRT extension!

    Log information will be found in "installkey.log"-file which gets updated.

    To create a Certificate and/or install extra certificates (so they appear in the Trusted Certificates list – Agent Configuration) do the following:


    1. Open a command prompt on the Core Server and type the following: "cd C:\Program Files\LANDesk\Shared Files\keys"

    2. Then run "genkey.exe "test1" "test2""


    Exchange "test1" with your Organization Name and "test2" with your Certificate Name.


    Log information will be found in "genkey.log" file which gets updated.


    On the Core Server go into the registry and change the Certname in the following key to the newly created key.





    If the above fails, it could be caused by a faulty/infected/corrupt LDPGP.EXE.


    Step 3



    From a command prompt, in the ManagementSuite directory on the Core, run:

    landesk.managementsuite.licensing.activatecore debug all


    On a NORMAL Core, this should ONLY give out a "debug.txt" to help you along.


    In a case of a virus-infected/corrupt LDPGP.EXE, you'll get a 0 kb "debug.txt" and a new log-file called "licensing.log".


    This one would then have entries such as:


    Validate ldpgp arguments = validate -f "C:\DOCUME1\landesk\LOCALS1\Temp\tmpCB2.tmp" -o "C:\DOCUME1\landesk\LOCALS1\Temp\tmpCB3.tmp" -c "C:\Program Files\LANDesk\ManagementSuite\LANDesk2004.crt"
    VerifyExternalSignature filepath = C:\Program Files\LANDesk\ManagementSuite\ldpgp.exe
    VerifyExternalSignature return value = False
    Validate exception = AuthValidationException: Unable to validate the authorization file
    at LANDesk.ManagementSuite.Database.LicenseManager.xa33cdd2792a23ee8(String xd011938348d0e2dc)


    You may also need to replace the ldpgp.exe file on the problematic core server with the ldpgp.exe file from a working core.