LM.Detection_x64.exe fails after release of VisualStudio-Patches

Hi all,  

all of a sudden ZPM doesn't work anymore : Detection stopped working yesterday, after applying the DAU yesterday every client fails during lm.detection.

A "debug scan" gives some more information, of course it's just the very last part of the (temporary) lmdetection.log:

2021/09/17 11:43:05.110 _WmiQuery: Namespace='root\cimv2' Query='select * FROM MSFT_VSInstance where Version = "15.9.28307.1440" AND ChannelId LIKE "VisualStudio.15.Release"'
2021/09/17 11:43:05.117 Error: Ausnahmefehler aufgetreten.
[80020009] Line: -1
2021/09/17 11:43:05.118 _LMDetect-OSPX: Removing OSPX directory
2021/09/17 11:43:05.118 LM.Detection: Removing extraction directory [C:\Program Files (x86)\Novell\ZENworks\zpm\tmpScan\lm.detection.cache]
2021/09/17 11:43:06.611 LM.Detection: Removing extraction directory [C:\Program Files (x86)\Novell\ZENworks\zpm\tmpScan\lm.detection.cache]
2021/09/17 11:43:08.165 LM.Detection: Unable to delete path [C:\Program Files (x86)\Novell\ZENworks\zpm\tmpScan\lm.detection.cache] [0]
2021/09/17 11:43:08.165 LM.Detection: Done

Any thoughts?

( Running ZPM 2017 U1 , Windows only )

  • You could check debug zmd-messsages.log file and also here's what's needed for debug lm.dectection.log file:

    1.        Go to "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Patchlink.com" in
    the registry.

    Rename the "cache" folder/key there to something else like "cache1" or

    2.       delete the following before running the command below:

    C:\Program Files (x86)\Novell\ZENworks\zpm\Cache\lm.detection.cache

    (If present)

    3.       open up command prompt as run as admin ‑> CD over to

    "C:\Program Files (x86)\Novell\ZENworks\zpm\" and run
    "LM.Detection_x64.exe /ErrorStdOut /registry /loglevel 4 /d 0 /e temp"

    (this could take a while to run and complete)

    Collect C:\Program Files (x86)\Novell\ZENworks\zpm\lm.detection.log
    *This file should be over 90-100MB

  • Thx: I already did the steps before , the part of what I called "debug log" was taken from the log - lmdetection didn't finish (so the log had like 10MB only), caused by a problem within the data (download):

    I created a SR on Friday and the problem was solved at hosting/provider-site (from hat I heard they removed the bad entry that caused the bad behaviour). Client turned back to work well on Saturday ;)