Webes HealthCheck End-To-End Detection Failed

[Dennisb_2]

Hi guys, I decided to disable the e2e since SIM has healthy status and it can see the VM entitlement. What is the implication when e2e is disabled? should I still get an alert if the other systems failed (not e2e related)?
Cheers!

[Frank Alden Smith]

Dennisb,

E2Es are an indication that WEBES is either not analyzing events, or is one hour or more behind in analyzing events. Disabling E2Es prevents you from knowing a problem is occurring, then when a real failure occurs while WEBES is broken -- HP will NOT be notified!

Take care,
frank

[Tuscani_1]

Frank, are you saying the HP tech I worked with should not have disabled the E2E errors? I think would agree.. it's like he applied a bandaid without fixing the underlying issue.

[Frank Alden Smith]

Tuscani,

The workaround that the technician gave you is NOT recommended, for the reasons I stated earlier. That is why an HP engineer was trying to diagnose your e2e issue by reviewing the log files you so kindly collected.

You and Dennisb can be of enormous help in resolving this problem, by sending the log files to me if the problem reappears. I will pass them along to the WEBES engineers who are working on this issue.

Take care,
frank

[Tuscani_1]

Thanks.. I suspected as much. I am going to reenable and will wait to hear back from you.

[Frank Alden Smith]

Tuscani & Dennisb,

The WEBES engineer needs more log files to determine the cause of the e2e issue; so the next time you get an e2e failure notification please:

1) Run 'desta sysinfo' on the command line (on your CMS)

2) Mail the Zip file to me frank.smith@hp.com.

I will let you know when a solution is found.

Take care,
frank

[Tuscani_1]

Will do

[Dennisb_2]

Thanks Frank. I will send the logs today. I'm just following Tuscani's workaround since my case from HP was already closed.
Cheers!

[dennis kloster]

I am getting the same exact error message every 8 hours. Did anyone get this issue fixed?

[GeraldR]

hi frank!

did sent you my desta sysinfo files in the last days...
...may i ask, if you got them and if you were able to pass them over to the specialist?

tnx! gerald

[ChallengerSchool]

We recently migrated from the simple, straightforward "it's worked for years" LeftHand service console to the monolithic HP Insight Remote Support to monitor a few P4500 storage shelves. We don't have any HP servers, just the SAN. The software is running on a VM. We are getting the Webes HealthCheck message every 8 hours. After opening a case with HP, sending the desta sysinfo information, and waiting a week, we received the following extremely helpful reply:

"please upgrade to the latest ver of the tool and see if thata resolves the
issue"

We are on the latest version. A few days later, more in-depth technical analysis from Level 2 Support:

"sounds like it is having comuncation issues"

Huh? I'm glad this error appears to be just a minor annoyance.

Has anyone solved this issue? Is it safe to disable the E2E notifications?

[Mike Haarsma]

We are getting the same issue... Every 8 hours. I have tried everything recommended in this forum and nothing solves the issue.

Version: Web-Based Enterprise Services Common Components for Windows V6.1 (Build 136), member of Web-Based Enterprise Services Suite for Windows V6.1 (Build 136)
Error Code: E2E

Description:

Webes failed to analyze a HeartBeat Event and log a problem report. Webes may not be in a running state.

CallStack:



Recommended Action:

Stop and restart Desta_service. If this problem persists then run "desta sysinfo" on the command line and give the generated Zip file to HP Customer Support.

[Grooper]

Same here.

HP Support case opened.
I wonder what'll be this time...?

I've been with this "tool" since it was released and not a single installation was without problems.

Thomas

[Roland R Schmid]

Hi!

I've recently installed the HP Insight Remote Support (IRS) and I am also getting this e2e error.

Unfortunately I cannot serr where I can change any of the settings you have mentioned here.

It must be different to SIM

[Grooper]

@Roland:
IRS comes in two flavours:

IRS standard without SIM Integration
IRS advanced with SIM Integration

BTW:
No help from Support so far.
Just "send logfile xxx" and " check your proxy and firewall"

Thomas

[Roland R Schmid]

Yeah I'm running

IRS standard without SIM Integration

[ChallengerSchool]

Support was no help here either. The last message received was

"i will try to contact the SIM team in regard to this"

followed by a notice four weeks later --

Closure of your request
STATUS: REQUEST IS CLOSED

Ridiculous.

[Roland R Schmid]

Well I'm getting a HP Engineer over to do my SAN firmware upgrade - They offered so I'm not going to turn down the service! ;)

I'll get the guy to check it out at that time and see if he can make heads or tails out of it.

Will only be in the first week of July as being End of Financial Year in Australia I don't want to potentially break anything until that period has passed. ;)

Will keep you posted!

[shocko]

I have the same issue. Did you ever get it resolved?

[Stefanovic]

Hey,

we are receiving the same notifications on a new IRSS standard 5.7 setup with WEBES 6.3.

Any suggestions on how to resolve this ?

Are the steps described in http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=3927992&prodTypeId=18964&objectID=c02936712  valid for 5.7 ?

These steps are an official statement of HP to disable the e2e ?

kind regards,

Steven

[shocko]

I have a call open with support so I'll update here if I get a resolution ;)

[shocko]

I got a resolution from HP Support. It turns out that when my Application Evtn log (i.e. the windows event log) grew to over 16MB, the E2E failed. It seems like the E2E process reads through the event log and has an issue when it's over 16MB. SOlution was to clear it down and restart the desta services.

[WJ Perry]

Well that's DANDY! Our log sizes are set by global policy, and currently 26 MB

Does anyone know if a newer version is available with a fix that also supports SIM version C.06.03.00.00?

[shocko]

I think I had put a script in place to clear it down after a certain size. Might be an easy enought solution unless you have to keep your logs

[pmancillas]

I am having the same problem. I just installed SIM 7.1 and IRSA 5.80 on a VM guest and I started getting the E2E error. I found out that the CMS server was not listed on the Remote Support Configuration and Services - Entitlement page in SIM. I did the "Edit System Properties" for the server and changed the "System Subtype" to "HP Proliant" and then the server showed up on the Entitlement page. I restarted the DESTA service and now I don't get the E2E errors anymore. So the fix is that the CMS has to be added to the RSCS page so that the end-to-end communication will work successfully.