Insight Remote Support
1833162 Members
3361 Online
110051 Solutions
New Discussion

WEBES 5.1 getting "End to End detection failed"

 
clayborn williams
Occasional Advisor

WEBES 5.1 getting "End to End detection failed"

I am getting the following error and when I restart the webes director a day later I will get the error again. Is there a patch available or fix for this?

Webes Health Check reported a problem at Thu, 21 Aug 2008 05:01:00 -0400

Hostname: rtpdseva001
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.
5 REPLIES 5

Re: WEBES 5.1 getting "End to End detection failed"

Upgrade to WEBES 5.2 and then install patch 2.
------------------------------------
Patch Release 2 for WEBES V5.2 is now available. This is a Windows only patch to the Windows only WEBES V5.2 release.

This patch release for WEBES V5.2 provides solutions for a number of errors users may see. Included in this release:

- A fix for end to end failure caused when WEBES waits for HP SIM to be ready for incoming connections
- A fix to the problem where WEBES could be running while MSSQL was not
- Resolution to the issue where idle SEA Analyzer shuts down and doesnâ t restart when new events arrive
- Sidbuilder fix to work with RSP client
- EVA EIP 06 analysis rule enhancements

This patch kit must be installed on systems that already have WEBES V5.2 installed
clayborn williams
Occasional Advisor

Re: WEBES 5.1 getting "End to End detection failed"

thanks
clayborn williams
Occasional Advisor

Re: WEBES 5.1 getting "End to End detection failed"

the solution has been found.
Deepak Mathew
New Member

Re: WEBES 5.1 getting "End to End detection failed"

I was getting this same error and did the install. It was fine for sometime, but today I got that same error and it is on V5.2 Patch2. Any ideas?
Norm Nakawaki
New Member

Re: WEBES 5.1 getting "End to End detection failed"

I applied the patch last month and everything was fine until last week. This error also started appearing again. I restarted the services and it hasn't appeared this week.