This means that either one of the IPM daemons is not running, or there is a firewall blocking CORBA access between your client and server. Post the output of the "ipm status" command. You can also try launching IPM directly on the server to rule out network issues.
If this is Windows, there should be an IPM DOS prompt option in your start menu. On Solaris, the command can be found in /opt/CSCOipm/bin.
Here is the output:
IPM Server Version: 220.127.116.11
IPM Server Hostname: usadc-scwk01
IPM Server Build Date: Tue Nov 30 10:00:00 IST 2004
IPM Database Server Already Running.
IPM Naming Server Already Running.
IPM Aging Server Already Running.
IPM Process Manager Already Running.
Process Manager running with processes:
PROCESS STATE PID Last Message
ConfigServer Ready 4196 Running
RTPServer Ready 4408 Running
MessageLogServer Ready 3760 Running
DataViewServer Ready 4456 Running
DataCollectionServer Ready 1124 Running
SNMPServer Ready 3848 Running
Also, when trying to run the IPM client from the CW server, I get the attached error.
# properties to be used by the IPM_ConfigMain
#Used by the client to setup the help system
webBrowser=C:\\Program Files\\Internet Explorer\\iexplore.exe
#Used by the client to enable debugging?
#NOT used by the client, needed by server?
# Used for the path echo display stats window when
# you double click a device
#Flag for determining whether IPM Standalone Client should use Gatekeeper
#to contact the server. Disabled by default, set this to Yes in case it is
#required, for example, to use IPM in an environment with a firewall
#between client and server.
#Port on which Gatekeeper is running on the server. Need to change ONLY
#if changed on the server to a value other than the default of 9088.