cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2993
Views
0
Helpful
6
Replies

Campus Manager 4.0 Device Discovery problem

woodsbc
Level 1
Level 1

Campus Manager (that comes with LMS 2.5) Device Discovery has been running since the 2nd of April (today is the 21st of April).

Prior to the 2nd, it was able to run a discovery within 15-20 minutes, no problem.

I have rebooted the server and it still shows that the Device Discovery operation is still running. The last completed time is listed 2nd of April.

How do I go about cancelling this Device Discovery operation? The other functions in LMS work just fine (and actually finish), including the Campus Manager, Campus Data Collection & User Tracking Acquisition operations.

Thanks

6 Replies 6

Keyan
Level 1
Level 1

I've also had this "stick". Go to Sever -> Admin -> Processes. Sort by process name and find DeviceDiscovery. Note the Process State and see if there is an error. At any rate, check the box next to it and click Start to force the server to start the process. It should then run normally. If the process manager thinks discovery is running when you get there you can also choose to manually stop it.

Just curious but did this start happening only after you installed SP1 for common services?

I have gone to the processes and tried to force it to start. It runs for about 30 seconds or so and then it terminates with the process state of 'Transient terminated'.

I haven't installed SP1 for common services. That looks like it came out the 6th of April and my problems started on the 2nd. Maybe the SP1 would clear this up?

Thanks.

Interestingly mine got stuck again so I forced it to start. The same as yours, it runs briefly and then goes into "transient terminated". What other processes do you have that end that way? I have three - UT major acquisition and something called FHPurgeTask in addition to discovery. The erros look like something is broken in the "log4j" subsystem, whatever that might be. I've also seen a transient terminated on device collection. This is using SP1, so I don't think it will fix the problem.

What OS are you running ciscoworks on?

Windows 2003 server. The Device Discovery process was the only one of my in the 'transient terminated' status.

Windows 2003 server as well here. Wonder if there is an issue with LMS 2.5 and the OS?

I am having the same problem with User Tracking aquisition. I'm running Windows 2003 & LMS 2.5 SP1. Has anyone opened a TAC case yet? I'm about to...