Remote Delivery Down - Stalled submissions

[Sandy Wood]

Where to start troubleshooting Stalled submissions? Nothing is getting to the upstream server. I've started and stopped ISEE / OSEM many times with no sucess.

[Frank Alden Smith]

Sandy,

If this is a newly configured managed system, then check entitlement information (product number and serial number, etc.) for system. Also make sure the Company and contact information is complete.

Failing that can you browse to the HP Data Center (e.g. http://isee.americas.hp.com/mots/motserv) from the managed system?

Hope that gives you a starting point.

Take care,
frank

[Sandy Wood]

My system has been up and working for about 6 months, it only stopped being able to connect in the past month.

I did apply Windows 2003 SP2 to this machine and wonder if it may have caused any issues. I can access

http://isee.americas.hp.com/mots/motserv

and I see the

Front End Statistics for Vendor HP_Services

page. I've tried to click on the Front End link

isee-front.atl.hp.com:2112

and that times out. Should I be able to get somewhere with this link?

[Sandy Wood]

My system has been up and working for about 6 months, it only stopped being able to connect in the past month.

I did apply Windows 2003 SP2 to this machine and wonder if it may have caused any issues. I can access

http://isee.americas.hp.com/mots/motserv

and I see the

Front End Statistics for Vendor HP_Services

page. I've tried to click on the Front End link

isee-front.atl.hp.com:2112

and that times out. Should I be able to get somewhere with this link?

[Frank Alden Smith]

Sandy,

No, you shouldn't be able to navigate to another page using the front end link. However, just reaching the page indicates that there are no problems with firewall or web-proxy configuration preventing delivery of the ISEE incident.

Stalled notifications typically are a result of an internal network issue. Any changes in that area lately?

Perhaps the log file may help look in: C:\Program Files\Hewlett-Packard\OSEM\Logs.

Finally, (forgive me if you did this already) have you tried to retry the stalled notifications in OSEM?

Take care,
frank

[Sandy Wood]

Frank,

Thanks for the note. It looks like since I can get to the hp web site, perhaps it's something in our network. I have tried retrying them all to no avail The logs show the repeated attempts, but nothing more. It appears that the OESM part works, to some extent. I get alerts via email when a trap is sent to the OESM server, they just don't make it out of our network.

At this point, I'm trying to get ahold of the HP engineer who configured our installation. I've run through all the docs I can find and I just can't pin the problem down. I wish the logging was more verbose.

Thanks again for the help. This is a really good system to have, I'd like to get it going again.

[Frank Alden Smith]

Sandy,

Since events are reaching OSEM from the health agent (Insight Management Agents) and OSEM is attempting to forward them to the ISEE Client -- something may be broken between OSEM and the ISEE Client. So there is one last thing to try -- stop and then restart the WCCProxy service, which interconnects OSEM and the ISEE Client.

Take care,
frank

[Sandy Wood]

Frank,

Thanks for the tip. I tried restarting the WCCProxy service but to no avail - still stalling out. I'm trying to locate an HP person locally to figure out what's going on.

Funny how it's hard to find them when you don't want to buy anything.

[Riza Samad]

I am experiencing the same thing. some messages appear as having status stalled@osem

[Johan Sandström]

Hi Sandy,

I have the same problem as you do, been going on since february and now I can't get it to work.

And by reading the forums there seems like there are alot of people having the same problems and noone knows what this is!!??


What I see in the log that I get "Response is null ISEE connection "

Surely, some HP tech-guy who works with ISEE and OSEM should know what this is and can help us, this must be a very common problem that has been reported to HP?

I have tried all the other checks, brows to this and that site see if can see the website, restart wccproxy...and more..even installed a new OSEM, 1.4.5, but the problem remain.

BR
Johan S.

[Liem Nguyen]

Hi,
The most common problem with "Remote Delivery Down - Stalled submissions" is with OSEM configuration. There are a few things you can check and correct within OSEM:

1. If you configured Company Information (Company name, Contact, Telephone ...etc...)then you do NOT need to configure this same info on each Managed System. The duplicated info will cause OSEM fail to deliver to ISEE.

2. Check the problem System for Entitlement information, Serial number, Product number, Entitlement ID...), you need to fill them in.

3. Check the Stalled event, make sure hostname received in the event is the same as hostname you've configured in Managed Systems.

Hope this helps,

[Lawrance Lee_1]

I've decided to subscribe to this thread because I'm also seeing the problem.

If I send a test OSEM message via Start->Programs->OSEM V1.4->Test OSEM, the ISEE does deliver this to the isee.asiapac.hp.com site, so I know that OSEM is able to communicate properly with ISEE.

So why does the test work but not the "real" traps?

Is there any point in upgrading OSEM to the latest version? I am on OSEM 1.4, crsm 7.4.14

Thanks,

Lawrance

[Albert Smith_1]

I had the same issue and I resolved it. If you are using SIM remove all Company information from the OSEM viewer. Restart CSRM and your mail should get delivered to HP. Use SIM to set the contact information and the entitlement information as OSEM is just passing information from SIM to ISEE to HP.

[Stefan måhl]

Hi
I also see this on some of my server's.
As Liem wrote it's crucial to have:
Serial number
Product number
for CW to correct identify the server.
I't works OK on the server that is identified by CW.

//Stefan