Webes HeartBeat test failed

[Armin Kerl]

Get on two Customers following E-Mail Notification all 8h:

Error Code: E2E
Description: Webes HeartBeat test failed to log event. Webes may not in running state
Callstack:
Recommended Action:
Restart Webes Director or Contact HP Services.
+++++++++++++++++
C:\wsea status
System Event Analyzer for Windows V4.5 RU1 (Build 290)
Service Tools Home: C:\Program Files\Hewlett-Packard\svctools
Service Obligation Start Date: Fri Feb 09 11:49:45 GMT 2007
Service Obligation End Date: Sat Feb 09 11:49:45 GMT 2008
ACHS/SICL/DSNlink notification: disabled.
OSEM/CSG/QSAP notification: disabled.
ISEE notification: enabled.
MOM notification: disabled.
SNMP notification: disabled.
DTCS notification: disabled.
SMTP notification: enabled.
LOG notification: enabled.
VMSMAIL notification: disabled.

C:\>desta status
Checking for DESTA director with PID 5960
The Director process is running.

[Sam Cofield · Accepted solution]

Sometimes it appears that desta is running when all acpects of it actually aren't.

You can try to doing the following:

CMD> net stop desta_service
CMD> wccproxy stop

Then I suggest you clear the Windows "Application" Log file.

Restart desta with CMD> net start desta_service
NOTE: wccproxy will automatically start.

If you still get Heartbeat failures, then I suggest upgrading to the latest WEBES kit (v4.5.1). It is suppose to address "false" heartbeat errors, if that is what this is.

Te verify when the Heartbeats are scheduled to run, you can check it under Control Panel - Scheduled Tasks. They will be listed as At1, At2, & At3. Right click and select Properties, then selected the Schedule Tab.


.....
Sam Cofield
HP Services
WEBES Support

[Armin Kerl]

Hello,

I have Updated to v4.5.1 and no more Error since 2 Days.

Thank`s Armin

[ADFT]

Hi,

I have the same issue
Do stopping these services have any affect on the SAN and users connected to it or the Virtual Servers that are also running on the SAN, or can the be stopped during business hours with no issues?

Cheers

[Armin Kerl]

Hi,

you can stop the Desta and WCC Proxy Service at any Time.
This will only affect the EVA Event Notification to HP and to Yourself.

Armin

[Sam Cofield]

Please keep in mind that WEBES v4.5.1 is no longer supported. It is supported on a Best-Effort Basis, as there have been new device support and improvements.

So if you have major issues, WEBES Engineering will not accept an elevation.

I would suggest getting WEBES upgraded to the latest (V5.2 patch2).

You are even at a point that the latest will not upgrade. V4.5.1 will have to be removed and then v5.2 installed. The WEBES install will upgrade automatically if you are within 2 version.

If you like, you can wait and be on the lookout for WEBES v5.3 to be released in mid-October.

You can always sign up for notification of new releases by doing the following:

****************
You can receive news about WEBES, as well as notification of new WEBES software releases via e-mail. E-mail alerts are available to both internal HP employees as well as HP customers. Follow these steps to register for Analysis Service Tools e-mail alerts:

1. Go to www.hp.com/go/myalerts

2. On the main â Driver, Patch, Security and Support alerts sign-upâ page, in step 1A, do a search for "WEBES" and then select "WEBES" from the list in step 1B. "WEBES" will then be added to "My Product List" in step 1C.

3. Fill out the rest of the form with preferences, email address, etc. In step 2, it is recommended that the selection "As they become available" is chosen to the question "How often would you prefer to have alerts emailed to you?â

4. Save the completed form.

5. As new versions of WEBES are released, an email alert will be sent to the registered email address with details about the new release and where it can be downloaded.
****************

....
Sam Cofield
Remote Technology & Enterprise Serviceability Tools Support

[Gustavo Nunes]

Hello,

I am having this E2E issue with WEBES 5.2, with Patch 2. I get this error:

---------------------------------------------
Webes Health Check reported a problem at Dom, 5 Out 2008 13:01:02 +0100

Hostname: .......
Version: 1.0
Error Code: E2E

Description:

Webes HeartBeat test failed to log event. Webes may not be in running state

CallStack:

Recommended Action:

Restart Webes Director or Contact HP services.
------------------------------------------

I already tried to restart WEBES director, the DESTA service, tried reinstalling the wccproxy and nothing had good results.

Do you have some help for me or think it's better to wait for the WEBES 5.3 release?

Thank you,
Gustavo Nunes

[Sam Cofield]

Gustavo,

With the release of v5.3 due out either this week or next, I feel it may be best to wait.

This way we don't have WEBES Engineering trying to work issues that are already resolved in the new release.

....
Sam Cofield

[Andrew M Matheson]

I am getting this as well, WEBES 5.2 patch 2...and it's november already and I don't see WEBES 5.3 yet, so I can't upgrade.

Webes Health Check reported a problem at Fri, 21 Nov 2008 05:01:00 -0500

Hostname: glhsms01
Version: 1.0
Error Code: E2E

Description:

Webes HeartBeat test failed to log event. Webes may not be in running state

CallStack:



Recommended Action:

Restart Webes Director or Contact HP services.


Thanks.


Andrew

[Kevin Shannon_1]

I'm getting this too, is there any update on when a patch is coming. Support just says its forthcoming.

[Sam Cofield]

The last update from WEBES Engineering on Dec. 2nd, is now looking like Friday (Dec. 5th) or Saturday (Dec. 6th) barring any issues with beta testing.

As listed above, you can setup to be notified when it is released.

FYI, it will actually be WEBES v5.4, because the v5.3 was only for EAP testing for IRS (Insight Remote Support).

Be patient, it is coming.

[David B. MacKenzie]

I started receiving the same "HeartBeat test failed" notifications with WEBES V5.3 from our SAN appliance that had been stable at that release for months. I upgraded to V5.4 (Build 24) which was released on Dec. 11th and still occassionally receive the same notifications.


Subject: End to End detection failed

Webes Health Check reported a problem at Sat, 3 Jan 2009 10:01:00 -0600

Hostname: sanapp
Version: 1.0
Error Code: E2E

Description:

Webes HeartBeat test failed to log event. Webes may not be in running state

CallStack:



Recommended Action:

Restart Webes Director or Contact HP services.

[Uwe Zessin]

One of our customers received the following workaround:
- stop services "desta_service" and "wccproxy"
- clear Application event log
- restart the services

[MrGoran]

I'm getting this error also. Running Webes 5.4. I've restarted the desta service, cleared the application log, re-installed Webes 5.4. Nothing seem to help. After a day at max the error is back. I've not yet done a full clean-up of Webes with HP's clean-up tool, but if I do so I'll surely loose configuration.
What is the current status here? Is this a HP bugg? Where can I find a patch if there is anything post 5.4...

Thanks

[NMCI Group]

I am also getting this now after upgrading to SIM 5.3 with the latest version of WEBES. All was working fine on SIM 5.2.2 with WEBES 5.4.

[Cameron Todd]

Hi, I had a new EVA storage system and management server delivered about 9 months ago and the HP Service Engineer came and did the installation services package as had been purchased, but I too have had the WEBES 'End to End detection failed" emails delivered to me every 6 hours day and night for nearly the whole time we have had this system.

The HP Engineer came back out twice after we reported that the fault had reappeared and he tried reinstalling the various software components each time, however, this did not last long and the messages soon started again for no apparent reason. (given the system was new and not yet in use for development by even our internal staff, there could not have been any changes done manually on our system to have triggered this)

The versions of what I think are the relevant software components are as follows - WCCProxy v2.2, OSEM 1.4.5 and WEBES v5.2 - but it is obvious from the above discussion that upgrading the versions is not a guaranteed fix.

Is anyone in HP engineering working on this ongoing problem, as I don't think contacting the local HP service support will result in any good result since they don't seem to know what is wrong or have the capability of fixing it.

[Cameron Todd]

Note that this is not just an internal reporting issue - Test alerts generated do not get to HP.. We also had an HSV200 shelf failure and no-one (HP nor us) got any notification of the situation, until someone visited the lights-out server room and spotted the lightshow.

[Tom Dooley]

We´ve got the same Problem and do serveral Updates of SIM and Webes, but i can not say that the SW have worked anytime.

At the Moment we will run HP SIM 5.3 and WEBES 5.4, erverything ist installed and configured, but it does not work.

[Patrik Priess]

I have the exact same issues with the webes. i just upgraded to version 5.5... hope that helps.

Anyone else found a soloution?

[Patrik Priess]

Oh well, even after the upgrade to WEBES version 5.5 we still get the

"Webes HeartBeat test failed to log event. Webes may not be in running state

CallStack:



Recommended Action:

Restart Webes Director or Contact HP services"


Still no one fixed this?

[Simon Ho (UK)]

I started getting the exact same error just over a week ago with WEBES 5.4. Since then I've completely uninstalled SIM 5.3 and all related components, then reinstalled SIM 5.3, which automatically upgraded WEBES to v5.5.

But the same E2E error is still sent out almost every time the scheduled jobs run.

This thread was opened 2 years ago. Can no-one at HP provide a proper solution to this issue?

[Simon Ho (UK)]

I've now noticed errors in the Windows System event log:

The DESTA_Service service terminated unexpectedly. It has done this 2 time(s).

Checking the Services shows that the DESTA_Service isn't running. This would explain why the E2E errors appear! The WEBES User Guide led me to the relevant logfile:

C:\Program Files\HP\svctools\specific\Webes\logs\WEBES.0.log

It seems that every time I start the DESTA_Service, it reports:

HPSIMEndpoint.getHPSIMConnection failed to create new hpsim connection

...and then later on:

ERROR JDBCExceptionReporter:78 - Unable to get information from SQL Server: localhost.

I'm going to try uninstalling WEBES 5.5 and then reinstalling it...

[Patrik Priess]

Hi Simon

Did it help with the re-installation?

[Simon Ho (UK)]

I'm still fighting with it - the WEBES 5.5 re-install failed! :(

Trying to work out why. I'm wondering if perhaps it's because the associated WEBESDB instance in SQL Server 2005 Express needs to be uninstalled as well?

[Simon Ho (UK)]

I recently had the same E2E error start to appear on another SIM server. On raising a case with HP Support, they pointed out this text in the notification e-mails:

"Webes HeartBeat test failed to log event"

They said WEBES log notification needed to be enabled, so I did this. (It's under WEBES Notification Settings in the System Event Analyzer.) Subsequent scheduled healthchecks ran without raising E2E errors.

I had previously enabled WEBES log notification when I'd installed all the SIM s/w, and there had been no E2E errors prior to the latest RSSWM automatic update.

HP agreed that the latest automatic update had updated WEBES and left the WEBES log notification disabled afterwards.

I suspect this is not the only cause of WEBES Heartbeat E2E errors, but it may help some of you.