If I remember correctly, it is related to an entry that is broken in the ldscnhlp.ini file which can be found on your clients at:
Check this file on one of the affected systems, see what entries are there, they may not be needed... this file is not used much, mostly for custom stuff.
Make a backup or rename this file, rescan with either no file named, or a blank file and see if that helps.
Please post back what you find
We've had this same error on Win7 clients with LD9 SP3 and found that, as mentioned, you edit the LDSCNHLP.INI file and change the following line under the [EXECUTE WIN32] section from:
...the error goes away. Presumably something to do with UAC/permissions. We have a ticket in with LANDesk and I am just recently told that a patch is expected soon for this. In the meantime, as we migrate WIN7 machines over to LD9 from LD8.8, we are following up the client install with a package that edits this setting in the .ini file.
I see the same error in SP3 on Win7, even with UAC disabled entirely. This is definitely a new issue with SP3. Hopefully a fix comes out soon, because I have written several custom inventory extenders that MUST run as the logged on user.
Also, I think LANDesk really needs to add an [EXECUTE WIN64] section and environment variable support to LDSCNHLP.INI, because right now we have to have to put separate 32-bit and 64-bit paths to the scripts we want to call and data we want to gather. Even prior to SP3, anyone running LDISCN32 with the UI enabled will get errors trying to launch the nonexistent scanners referenced in LDSCNHLP. For example, on Service Pack 2 the INI below throws 4 errors on 32-bit OS, 4 errors on 64-bit OS, and now with SP3, two additional errors for not being able to run as logged in user.
6 errors to the end-user when they run a scan = very annoying! Especially since I could cut the LDSCNHLP size in half by using %LDMS_LOCAL_DIR%, but environment variables are not allowed in LDSCNHLP...
[EXECUTE WIN16] [EXECUTE WIN32] LAUNCH1=wscript //B "C:\Program Files (x86)\LANDesk\LDClient\Data\enptMappedDrives.vbs" ERROR on 32-bit and SP3 LAUNCH2=wscript //B "C:\Program Files (x86)\LANDesk\LDClient\Data\enptMappedPrinters.vbs" ERROR on 32-bit and SP3 LAUNCH3=wscript //B "C:\Program Files (x86)\LANDesk\LDClient\Data\enptUninstallStrings.vbs" ERROR on 32-bit LAUNCH4=wscript //B "C:\Program Files (x86)\LANDesk\LDClient\Data\enptLocalGroupMembers.vbs" ERROR on 32-bit LAUNCH5=wscript //B "C:\Program Files\LANDesk\LDClient\Data\enptMappedDrives.vbs" ERROR on 64-bit and SP3 LAUNCH6=wscript //B "C:\Program Files\LANDesk\LDClient\Data\enptMappedPrinters.vbs" ERROR on 64-bit and SP3 LAUNCH7=wscript //B "C:\Program Files\LANDesk\LDClient\Data\enptUninstallStrings.vbs" ERROR on 64-bit LAUNCH8=wscript //B "C:\Program Files\LANDesk\LDClient\Data\enptLocalGroupMembers.vbs" ERROR on 64-bit TIMEOUT1=300 TIMEOUT2=300 TIMEOUT3=300 TIMEOUT4=300 TIMEOUT5=300 TIMEOUT6=300 TIMEOUT7=300 TIMEOUT8=300 RUNASLOGGEDINUSER1=TRUE RUNASLOGGEDINUSER2=TRUE RUNASLOGGEDINUSER3=FALSE RUNASLOGGEDINUSER4=FALSE RUNASLOGGEDINUSER5=TRUE RUNASLOGGEDINUSER6=TRUE RUNASLOGGEDINUSER7=FALSE RUNASLOGGEDINUSER8=FALSE [DATA FILES] DATANOPREPEND1="C:\Program Files (x86)\LANDesk\LDClient\Data\enptMappedDrives.dat" DATANOPREPEND2="C:\Program Files (x86)\LANDesk\LDClient\Data\enptMappedPrinters.dat" DATANOPREPEND3="C:\Program Files (x86)\LANDesk\LDClient\Data\enptUninstallStrings.dat" DATANOPREPEND4="C:\Program Files (x86)\LANDesk\LDClient\Data\enptLocalGroupMembers.dat" DATANOPREPEND5="C:\Program Files\LANDesk\LDClient\Data\enptMappedDrives.dat" DATANOPREPEND6="C:\Program Files\LANDesk\LDClient\Data\enptMappedPrinters.dat" DATANOPREPEND7="C:\Program Files\LANDesk\LDClient\Data\enptUninstallStrings.dat" DATANOPREPEND8="C:\Program Files\LANDesk\LDClient\Data\enptLocalGroupMembers.dat"
Sounds like a good ER, add it and I will vote.
Man up to 70 points already.....
I posted that ER a while ago actually It was originally not related to any SP3-specific issues, but I updated it.
Does anybody Know if a fix forthis has been released or dowe still have to modify the ldscnhlp.ini file? Just starting to look at using custom data froms and this is hindering my a bit.
Yes, it was fixed in the march CP-BASE update, current CP-BASE info can be found here (http://community.landesk.com/support/docs/DOC-24787), but you have to get the update through LANDesk support.