ISEE failed to show new incident after installation

[Tammy Liang]

I got pop up window showing WARNING: Unable to connect to http://hostname:80/mots/motserv using proxy:......
I setup proxy server, login user id and password via configuration option.
I can use IE on my desktop with the same proxy server, user id and password to go out firewall, different web sites.

I run iseeConnectivityTest.sh and get following message
ERROR: Failed to submit incident because CL_ERROR_ESCALATE_FAILED

Please help...

Appreciate any suggestion and advice...

Thanks...

[Jim Mallett]

Do a "ps -ef | grep ems" and see if the EMS listener is installed.

I just recently moved from predictive to ISEE and I had the same message on two of my machines. Check your swinstall.log and make sure all five components of the install were successful.

Also: Be sure that you have loaded any required patches and then reinstall ISEE.

Jim

[Jim Mallett]

Also, you do have internet connectivity on that machine, correct?

Jim

[Zeev Schultz]

Couple of tricks ...
1)check EMS version (swlist -l bundle | grep OnlineDiag),I think it should be newer that Dec 2001.There is also an EMS patch.
2)put isee.europe.hp.com (if you are in Europe) into /etc/hosts.I did it with DNS resolving and found that ISEE is somewhat sensitive to lookups,so gone the sure way.
3)check that via you proxy you can reach the site HP mentions in 'Getting started with ISEE' paper (search docs.hp.com for that one)
4)Was new installation ok and did you receive any emails from HP/saw the 'New installation' incident in the ISEE incidents table?
5)swlist -l fileset -a state | grep instal -
check that some ISEE related filesets are not only installed but also configured...

Zeev

[Jack C. Mahaffey]

Has this problem been solved? I'm having the same problem on one of my servers.

[Tammy Liang]

It is resolved. I am using SPOP in stead of trying to configure as stand alone systeme. It is the firewar issue.