SEATEST event callout reports 'Undelivered: ISEE' --- HP Insight RS

[Matthew P Simms]

Hello all,

When I issue a 'wccproxy test', the WEBES notification status reports 'Undelivered ISEE' and I can't figure out why.
I've checked Entitlement type, Serial Number, Product Number and Entitlement ID (I entered our SAID number number here).
I've also checked the proxy settings (which are the same settings that RSSWM used to install Insight RS).

Is there a log file somewhere that says exactly why WEBES cannot deliver the ISEE event? Or anybody know what else I should be checking?

Thanks,
Matt

[Uwe Zessin]

I've had to make corrections to the proxy configuration from that GUI - see attachment for the ICON to select.

[Stefan Liljenberg_1]

Hello all,

I Have the same problem , no problem
during installation but got undelivered
ISEE.

What exactly did you have to change in
proxy configurations in WEBES.

/stefan

[Frank Alden Smith]

Matt,

Here are two possible causes for your problem:

1) Notifications are not being directed to the HP Remote Support Client. To verify notifications are correctly configured open a command window (on the CMS) enter c:>wsea status. You should see the following:

C:>wsea status
System Event Analyzer for Windows V5.5 (Build 61)
Service Tools Home: C:\Program Files\HP\CM\svctools
Service Obligation Start Date: Fri Apr 24 08:53:12 EDT 2009
Service Obligation End Date: Sat Apr 24 08:53:12 EDT 2010
ACHS/SICL/DSNlink notification: disabled.
OSEM/CSG/QSAP notification: disabled.
ISEE notification: enabled.
HPSIM notification: enabled.
MOM notification: disabled.
SNMP notification: disabled.
DTCS notification: disabled.
SMTP notification: enabled.
LOG notification: enabled.
INDICTMENT notification: disabled.
EVT notification: disabled.
VMSMAIL notification: disabled.

Make sure ISEE notification is enabled. If not enable it with C:>desta ISEE on

2) The HP Remote Support Client service is not running on the CMS.

Of course, there are other possible causes but these are the most frequent.

Take care,
frank

[Matthew P Simms]

The HP ISEE support rep (tier 2) found the following problem in the iseeclient.log file:
"IseeClient | Warning| TransportManager.cxx:69 | Registration token load failed, client may NOT registered"

So he issued the following fix via cmd prompt:
"C:\Program Files\HP\RemoteSupport\bin\registereClient.cmd -forcereg"

and now it works. :)

Thanks.