Webes HeartBeat test failed

[Patrik Priess]

Mine webes still not working. Still getting the "Webes HeartBeat test failed to log event. Webes may not be in running state
" error.

Anyone got webes to work? The ISEE EOL is comming just around the conor :(

[Simon Ho (UK)]

If the WEBES log notification setting in the SEA is enabled (see my previous posting), then I'm afraid I'm out of ideas.

[Gustavo Nunes]

Hello,

if you enabled the Webes logs, then you must restart DESTA and wccproxy.

On the Webes system:

DOS>net stop desta_service

DOS>net stop wccproxy

DOS>net start wccproxy

DOS>net start desta_service

Worked for me.
Good luck!

[Cameron Todd]

After several months of no errors the 3 times a day (every 8 hours) Webes Heartbeat E-E detection failure error has started again as of 1pm local time this Monday.

No-one has touched the system. Is it possible that an update to any s/w component has been delivered and automatically installed??

[Cameron Todd]

I stopped the Desta Service and WCCProxy Service as listed above (and restarted in reverse order) and it has not errored at the usual 1pm time, so looks like might have, for the moment, fixed the fault.

[Simon Ho (UK)]

As per my posting of May 8th, HP agreed that the cause of the heartbeat failures on our SIM was that the automatic update had left WEBES log notification disabled, even though I had previously set it enabled.

On our other SIM, I've also seen more serious issues with Remote Support in general, which required HP to patch a corrupted configuration file. The issues on that SIM also first arose following an automatic update - to me this appears to be more than just coincidence.

Since these updates are causing us problems more often than not, I have disabled automatic updates on both our SIMs for the time being. The option is accessed via the RSSWM GUI under Options -> Preferences.

Disclaimer: Whether anyone else decides to do likewise is their call - I'm sure HP would recommend leaving auto updates enabled.

[Simon Ho (UK)]

Btw, there are various logs that might help in shedding some light on these issues. Here's a list of some of the log directories (this list isn't exhaustive):

C:\Program Files\HP\CM\Log

C:\Program Files\HP\CM\RSSWM_Pkg_Logs

C:\Program Files\HP\svctools\specific\Webes\logs

[D.Glass]

We started getting the exact same E2E messages after installing the ISEE replacement last week. So it is still a problem with Webes 5.5.

I have managed to get the messages stopped. It appears to be an issue with Java versions. The version of Java used by the Webes Health Check script desta.bat is bundled with Webes and is out of date, so was not enabled on my server.

I manually added it using Control Panel:
1) Click on Java
2) Click on Java tab
3) Click on one of the Java Application Runtime View buttons
4) Click on Find
5) Browse to the Webes Java version folder - probably C:\Program Files\HP\svctools\common\jre\bin
6) Click on Finish to add it.

You may still have to flush the Java cache and restart Desta service etc, but this appears to have worked for me.

I suspect the next Java update from Sun will disable this version of Java and I will have to do this again.

It is staggering to see this problem has persisted for two years without anyone at HP being able to resolve it.

[Patrik Priess]

Thanks David. It helped me alot! No more errors for me now.

[DELAHAYE_2]

Hello.
I have exactly same problem of E2E error with different Webes version.
The first time I removed Java from the server and It works fine since 2 years (we can only access Webes from another station).
DL380 Windows 2K3 SE US Webes 5.2 no internet access.

The second Time I just try to change the Sun Java by MS Java but after 2 days the error came back (With Webes 5.5).
It seem that this problem is affected by Java, but on this system I can't remove it.
VMWARE Windows 2K3 SE US Webes 5.5 No internet access.

I test again with another config DL380G4 W2K3 french and again the same error.
DL380G4 Windows 2K3 French Webes 5.5 internet acccess.

if someone had a solution.
PS : I have tested all ITRC solutions given previously.

regards

[Víctor Cespón]

Log notification is not enabled on WEBES 5.5 RSS installations. This will cause E2E failures.
WSEA Information
====================
System Event Analyzer for Windows V5.5 (Build 61)
....

LOG notification: disabled.
INDICTMENT notification: disabled.
EVT notification: disabled.

Go to SEA user interface - WEBES notification settings enabled

[Randy B]

The issue is related to DEP settings at the time of RSP installation. If DEP is turned on RSP needs to be uninstalled completley DEP turned off and RSP re-installed after a reboot.

I am not sure why HP has not noted this but I have Louis to thank (case 3600381167)

[ShreeS]

May be will this help

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1250764547642+28353475&threadId=1270131

[Armin Kerl]

After Updating to IRSS 5.6 (WEBES) I have got the E2E Messages again.

I checked the WEBES Log Notification and after the Update it was OFF.
(Open System Event Analyzer and go to the 6th Icon in the second group above, the yellow triangle with the ? in the middle, make sure that the "Event Log Notification" is turned "ON")

So I change it to ON.
But it does not Fix it.

What I have see is that the EVA's in the "Default Group" of SEA are no longer shown, but the are Green in the new Web GUI.
The Issue was that the Update also put ELMC to OFF.
Change it back to ON and the EVA's come back and also the E2E error have gone.
(You can enable it with the new WEB GUI or in SEA. In SEA go to the Entities > Server and change ELMC to "defaultCV" if this Server have EVA CV Installed or "default ELMC" if it is non CommandView Server.)
Don't forget to Restart WCC Proxy.

In my Case the EVA's are now displayed again and the E2E error is gone.

Btw.:
The E2E Test was generated by an AT1-3 Shedule Command all 8h, to test it without waiting you can run it NOW.

[juan quesada]

all,
I faced the same problem. I recommend the following procedure to fix it.

â ¢ uninstall RSSWM Startâ All Programsâ Hewlett-Packardâ Remote Support Software Manager â Uninstall Remote Support Software Manager.
â ¢ From control panel, remove in this exact order the following components (some of this may or may not apply to you, if not listed just skip it)

1.Remote Support Configuration Collector (RSCC)
2. WMI Mapper
3. Web-Based Enterprise Services (WEBES) for Windows
4. Remote Support Eligible Systems List
5. Remote Support Device Discovery And Update (RSDDU)
6. Event Log Monitoring Collector installation depot for x86/x64 Windows servers
7. Remote Support Client
8. Remote Support Common Components (MC3)
9. Insight Remote Support Standard Release Notes
â ¢ Run Webes clean up Utilities founf at http://www.compaq.com/support/svctools/webes/webesdownloads.html#cleanup
â ¢ Restart server
â ¢ Make sure Java and .net framework 2.0 are installed (SNMP is optional depending of your needs)
â ¢ Re-install product
â ¢ Confirm Webes notification is enabled at Start menu...Systems Event Analyzer -> WEBES Notification Settings. WEBES log notification ON


Please reply to let us all know if this fixes your issues.


Juan Quesada

[Andres Montenegro]

This is in reply to Juan Quesada's Procedure.
I'm running WSEA version 5.5 build 61 and I'm still getting the same problem with the heart beat detection failed. After applying your procedure the issue persists. Does HP have an official patch for this issue. It is annoying!!!

[Dennisb_2]

This is also happening on WEBES 6.1 version, mine is running on VMWARE ESX/ESXi. I submitted a case to HP support and the engineer said its not supported but it is. They gave me a link I guess the HP engineer doesn't read the documentation. And it is annoying.

Any resolution for this bug?

[Mauricio Gimenez_1]

Menssagem is showing the same to me, and I'm also using VMware.

Does anyone have a solution for this case?

[Jiad Elkadri]

We're also running Webes 6.1 on an HP DL360 G6 and are getting the same error. We're going to try some of the suggestions here and see if the issue goes away.

[Jiad Elkadri]

Here's the steps that we were given by hp. I will update if this fixes our issue:

Please check the windows application log size configuration is equals to 16000 (16mb), if not please put that value on the size properties. After this please clear the log

As well check if the Event log notification is on:

Start menu...Systems Event Analyzer -> WEBES Notification Settings (Yellow triangle with question mark Icon). From there please switch the WEBES log notification to ON.

To refresh changes:

1. DOS>net stop desta_service
2. DOS>net stop wccproxy
3. DOS>net start wccproxy
4. DOS>net start desta_service

Last step:

A. Open a command prompt
B. Browse to:
C:\Program Files\HP\CM\RemoteSupport\bin
C. Enter the command:
1.registerclient â forcereg

[sparky256DSL]

has anyone solved this? I have three server sending this notification.