Webes HeartBeat test failed (again)

[Steven Clementi]

I have the same error as in thise thread...

" http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1102115 "

My Webes is already at the latest and this "just" started happening a few days ago. It was fine before Friday. (This is a brand new installation for a DR site so there are currently no EVA's being managed by the server.)

Are there any logs I can look at to see if something is not configured right?

Steven

[ITRC Test-CH]

WEBES version 4.5 and later has a built in health check where the E2E (end to end) test belongs to. This one may "struggle", which causes a lot of notifications.

To stop this, you can turn it off with the command C:\desta whc e2e off .

Regards,
Werner

[Steven Clementi]

"To stop this, you can turn it off with the command C:\desta whc e2e off ."

I've already explored this option and...

Turning it off is not an option. It was working, now it is not. I need to figured out what changed and correct it.

Any other suggestions?


Steven

[Steven Clementi]

HP Support has informed me of an issue with 4.5.1 and that if I can not manually reset the ozone database successfully, I should back out the install and try WEBES 4.5

WEBES 4.5.1 was removed after several attempts at resetting the ozone db and re-installed. So far, things look ok and there are no heartbeat errors.

This is one fix for the problem (that not always works according to HP Support). WEBES 5 is supposed to address/fix the issue.

Steven

[Steven Clementi]

See previous post for conclusion and solution.

Steven

[James Cordill]

I'm getting the same error with webes 5!
What now?

[Jerry Huizinga]

Hello Webes users,

We are using Webes 5.1 and still we receive E2E failures.
Most of my customers also complain about these events.

Isn't time to put a working version on the net ?

Jerry.

[Michael.Bradshaw]

I have Webes 5.1 with Patch 2, I installed 5.1 P2 3 weeks ago, an upgrade from 4.5.1, and now I get the E2E error several times a day. REALLY annoying. Makes me not believe my SAN is being monitored.

Any real fix out there? I tried all this:
Here are the steps to reset WEBES when you get an E2E error
1 Stop DESTA and WCCProxy

- From the command prompt type desta stop to stop the desta service, it might take some time for it to completly stop

- type wccproxy stop to stop the wccproxy service

2 Run C:\program files\hewlett-packard\svctools\common\share\WebesJavaKill.exe

3 Check the Windows Application event file size:

- On the desktop, right click on My Computer or My Appliance, and select Manage.

- Click on Event Viewer, and the right click on Application and select Properties.

- Make sure MAX LOG SIZE is set to at least 8192KB and no more then 16960KB.

- Also make sure "Overwrite events as needed is selected"

- Save and clear the Windows Application event file

4 Delete the following files in C:\program files\hewlett-packard\svctools\specific\desta\data

- destadb.*

- ed.*

- wbemdb.*

5 Restart DESTA (net start desta_service) NOTE:WCCproxy automatically starts

6 Wait a few minutes an run a WSEA TEST

[Paul Kurtz]

I am seeing this message on 5.4 is there a fix?