We have the same issue here. I've had a support call in for over a week now on it. While I was on the phone with them the scan worked several times when we tested it, release the call and the problem returned. I've stopped our roll out of 9.5 because of this and a clientdbutil.exe crash issue we are seeing as well.
We have also suspended our rollout of 9.5 as well. We currently have all agents on 9.0 SP3 reporting to the 9.5 core. We have provided our SEP client install and our 9.5 agent to support for testing.
I tested the new SEP 12.1.2015.2015 on one of the clients yesterday, no change. Looking back I opened the ticket on Nov 15, last support comment Nov 20.
We are using SEP 12.1.671.4971. We have been working on this issue with support since Nov 15 as well. We first started to notice the issue when issuser.exe would crash as well as the LDSECSVC.EXE being blocked by Symantec Tamper Protection.
Try to exclude ldclient directory in SEP. See if that works. I don't think it is a problem caused by inventory scanner, but most likely by SEP 12 preventing certain actions on inventory scanner.
I am Chetan Savade from Symantec Technical Support Team.
You can try by creating centralized exception.
Articles: Creating Centralized Exception Policies in Symantec Endpoint Protection Manager
@luce & genmanl - Could you please share the Symantec case id's so we can try to look into them.
Thanks and Regards,
Technical Support Engineer
End Point Security
Enterprise Technical Support
No Symantec case number. I've only addressed the issue with LANDesk at this point in time. I've had a centralized exception on the landesk folder for years now, hasn't change. Same policy on Windows 7 and XP machines. This issue is only happening on XP with the 9.5 client. Older clients do not experience the problem.
Hi! We are experiencing the same issue as well. Only affects the inventory scan on Windows XP machines. Windows 7 seems to work ok. We have tried adding exceptions in SEP for ldiscn32, for the entire program files\landesk folder, and for all other folders we can see landesk uses from using procmon to track whats happening. We have used a managed version of Sep 12, and an unmanaged version, have tried uninstalling sep components to see if its one component causing the issue, but even with all sep components uninstalled except the core components it still causes the inventory scanner to hang. Uninstall SEP from the XP machine and all works normally. So we then installed the unmanaged SEP and tried with all the exceptions again, and disabling all components (threat protection, intrusion prevention, tamper protection, AV, Firewall etc) but again, inventory scanner will not work correctly on XP unless SEP is uninstalled.We also tried different versions of SEP (RU1 MP1, MP3 and Ru2) but no difference.
but Landesk agent 9.3 works fine on XP machines. very strange. Using Procmon to track the processes etc, enabling inventory scanning debug logs still hasnt shed any light on whats causing the issue :-(
Can someone please attach your ldiscn32.log? There is a log in \...\LANDesk\ldclient\ and there is one in \...\LANDesk\ldclient\data\. Please attach both. Also is there any entry in Windows application even log related to this issue? The more information you can give us, the better we can help.
I would also recommend opening a case with the support. Ideally you would make available your SEP client and send it to the support for testing too.
Phillip: We already have a case open with LANDesk Support (588552). We have been working with Tony Hart on this since 11/15. We have sent our LANDesk agent as well as our SEP client install to support for testing. Support could not replicate the issue on their XP VM.
I have a laptop I can run down to you if it would help. I'm just in SLC.
We shipped one of our HP 8460p laptops overnight to Scott Tenney at LANDesk and it arrived today. We are waiting on feedback from support.
1 of 1 people found this helpful
LANDesk support is aware of the problem and we have this logged this with the developers. If you have an existing case open, the problem ID number will be indicated on the ticket. Developers are looking at this defect for solutions.
I think I am having this same issue on my win xp machines also and i am running landesk 9.5. Only difference is that I am running Symantec endpoint protection 11.5.
I got a call from one of my remote sites reporting machines running mulitple ldiscan processes in task manager. I remoted into the machine to look closer at the issue. I killed the ldiscan processes there were about 7 then proceeded to launch an inventory scan manually but it doesnt complete, it just just hangs after a certain point. I removed symantec 11.5 after seeing this thread and the inventory scan now completes without SEP installed on the machine. He reported this from a few dozen machines that i need to fix. This seems to be causing the machine to not be able to be rebooted cuase of so many hung ldiscan processed. I assume the inventory scan i run causing another ldiscan process to run. No problems on win 7 machines only xp
I added a centralized except in symantec console but still no luck
Have there been any fix from landesk on this or any update on this?