Deadlock in Device Discovering LMS3.2 / CS3.3 Win

Unanswered Question
Jan 25th, 2010


Is there any hint how to unlock this deadlock in Device Discovering. Every Time I want to start a Device Discover Job manually (immediately) I get:

" An instance of discovery is running already. Please try to start once it gets completed. "

If I want to debug the problem, the ngdiscovery.log keeps empty.

If I order the Jobs after job-type in the Job-browser, I will see the only Jobs devices has been discovered was "Peridic Jobs" and all immediatly Jobs found 0 devices or crashed with " An instance of discovery is running already ...". Knowing that during the whoole history of Job-browser we did many reboots, I can imagine that a new reboot will not improve the situation.

What can we do?


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Mon, 01/25/2010 - 20:26

Try starting CSDiscovery manually from the server's command line:

pdexec CSDiscovery

That should cause a Discovery to run, then allow it to run from the GUI.


This Discussion