Insight Remote Support
1761287 Members
3878 Online
108901 Solutions
New Discussion ī„‚

Re: Webes HealthCheck End-To-End Detection Failed

 
Roland R Schmid
New Member

Re: Webes HealthCheck End-To-End Detection Failed

Yeah I'm running

IRS standard without SIM Integration
ChallengerSchool
New Member

Re: Webes HealthCheck End-To-End Detection Failed

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
New Member

Re: Webes HealthCheck End-To-End Detection Failed

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
Honored Contributor

Re: Webes HealthCheck End-To-End Detection Failed

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

If my post was helpful please award me Kudos! or Points :)
Stefanovic
New Member

Re: Webes HealthCheck End-To-End Detection Failed

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
Honored Contributor

Re: Webes HealthCheck End-To-End Detection Failed

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

If my post was helpful please award me Kudos! or Points :)
shocko
Honored Contributor

Re: Webes HealthCheck End-To-End Detection Failed

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.

If my post was helpful please award me Kudos! or Points :)
WJ Perry
Occasional Advisor

Re: Webes HealthCheck End-To-End Detection Failed

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
Honored Contributor

Re: Webes HealthCheck End-To-End Detection Failed

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

If my post was helpful please award me Kudos! or Points :)
pmancillas
Visitor

Re: Webes HealthCheck End-To-End Detection Failed

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.