03-03-2009 01:52 AM
Hello,
If someone has an idea about this state of process, listed in the PDSHOW output .txt ?
- Transient terminated
- RC =2
The process DeviceDiscovery can't be launched. I tHink that maybe there is a mismatch in the configuration file:
Device.Properties
The RC in normal state has been set to: 0
Is is the attempts of process launching ?
Thanks
The customer is in Master -Slave mode, RME is the Master with a 16M Swap memory in W2K installed.
Solved! Go to Solution.
03-04-2009 10:28 AM
You're seeing a very old known bug. You really need to upgrade to Campus Manager 4.0.12. However, to fix the immediate problem copy the DeviceDiscovery.properties.orig to DeviceDiscovery.properties. Then edit DeviceDiscovery.properties, and change the line DEVICESROOT= to:
DEVICESROOT=C:\\PROGRA~1\\CSCOpx\\campus\\lib\\classpath
Now you should be able to reconfigure your Discovery settings in the GUI. Once they are all back, you can re-run Discovery.
03-03-2009 02:17 AM
to which .txt file do you refer ?
'Transient terminated' is the correct status for DeviceDiscovery if there is no discorvery running.
If a discovery is running the status changes to 'Program started - No mgt msgs received'
The process DeviceDiscovery cannot be started manualy through cli. It is started automatically when you start a new Discovery Job through the GUI.
03-03-2009 05:52 AM
03-03-2009 05:55 AM
Sorry i forgot that :
The pdshow has been launched in that way
C:\....\CSCOPX\pdshow > pdshow.txt
It results a txt file.
03-03-2009 07:17 AM
which version CM do you have? Have you installed any update lately?
Please post your NMSROOT\campus\etc\cwsi\DeviceDiscovery.properies file as an attachment
03-03-2009 10:40 AM
Please post the discovery.log.
03-04-2009 01:32 AM
03-04-2009 03:50 AM
you posted the DeviceDiscovery.properties.orig file not the DeviceDiscovery.properties file. The last one is used by the system while initializing the discovery process the former is the original version (without any customization like seeds etc.) as a backup. Please post your 'DeviceDiscovery.properties' file so that we can have a look if the file is broken.
03-04-2009 08:11 AM
03-04-2009 10:28 AM
You're seeing a very old known bug. You really need to upgrade to Campus Manager 4.0.12. However, to fix the immediate problem copy the DeviceDiscovery.properties.orig to DeviceDiscovery.properties. Then edit DeviceDiscovery.properties, and change the line DEVICESROOT= to:
DEVICESROOT=C:\\PROGRA~1\\CSCOpx\\campus\\lib\\classpath
Now you should be able to reconfigure your Discovery settings in the GUI. Once they are all back, you can re-run Discovery.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide