Insight Remote Support
1754419 Members
3048 Online
108813 Solutions
New Discussion юеВ

Webes HealthCheck End-To-End Detection Failed

 
Tuscani_1
Frequent Advisor

Webes HealthCheck End-To-End Detection Failed

Any idea how to resolve these? I am running SIM 6.1 on Server 2008 R2

--

Webes Health Check reported a problem at Thu, 7 Oct 2010 21:05:02 -0500

Hostname:
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:
50 REPLIES 50
Frank Alden Smith
Trusted Contributor

Re: Webes HealthCheck End-To-End Detection Failed

Tuscani,

Check to see if the DESTA service is running on the CMS. Restart it even if the service appears to be running.

Take care,
frank
All knowing is doing.
Tuscani_1
Frequent Advisor

Re: Webes HealthCheck End-To-End Detection Failed

Yeah.. tried that.. no help.
GeraldR
Advisor

Re: Webes HealthCheck End-To-End Detection Failed

we have the same problem...

exactly every 8 hours we do get an mail from hpsim "Webes HealthCheck End-To-End Detection Failed":

Webes Health Check reported a problem at ...

Hostname: xxx.y.z
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.




any ideas?

tnx! gerald
BPE
Esteemed Contributor

Re: Webes HealthCheck End-To-End Detection Failed

If you get the E2E failure every 8 hour.
What tells you desta status?
If the desta service is still running it could be that you are running on a VM and the configuration is not done correctly.

End 2 End means that the scheduled test
similar to the "wccproxy test" command was not able to send a test event to HP.

The reason can be
- Desta_service was not running
- If desta can not connect to the underlying postgreSQL database it will stop after some time.
- the remote support client could not connect to HP. e.g. internet connection problem / proxy change
- The remote support is configured to transport disable for the system running WEBES
- The system with WEBES is not in the support eligible list.(No HP System)
Tuscani_1
Frequent Advisor

Re: Webes HealthCheck End-To-End Detection Failed

I get two differest errors:

1.

An installation of HPSIM on been detected; however WEBES was unable to communicate with it.
This may be because HPSIM is not running or not functional.

WEBES will attempt to proceed with startup, but it will function in a degraded mode until this problem is resolved.

Resolution:

Step 1: Go to Start->Control Panel->Administrative Tools->Services, select DESTA_Service, then stop it.
Step 2: In the same window select HP System Insight Manager and either start or restart the service.
Step 3: Open the HP System Insight Manager interface (i.e. https://localhost:50000 ) and login.
Step 4: After verifying that HP System Insight Manager is running correctly, restart the DESTA_Service

2.

Webes Health Check reported a problem at Sat, 9 Oct 2010 05:05:01 -0500

Hostname:
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.
BPE
Esteemed Contributor

Re: Webes HealthCheck End-To-End Detection Failed

In this case it could be that the certificate exchange between WEBES and SIM did not work correct. I would follow the advice and open a HW case (WEBES is a part of Remote Support and a part of HW Support) HP support could help you easy out of this situation. If the communication between HPSIM and WEBES don't work your system is never eligible for the communication with HP and the end 2 End will fail.
Frank Alden Smith
Trusted Contributor

Re: Webes HealthCheck End-To-End Detection Failed

Tuscani and GeraldR,

I have been in contact with the HP engineer who is working on this issue. He requests that you:

Run "desta sysinfo" on the command line (on your CMS) and attach the generated Zip file to your ITRC reply.

I will send these files to him and keep you all posted.

Take care,
frank
All knowing is doing.
Tuscani_1
Frequent Advisor

Re: Webes HealthCheck End-To-End Detection Failed

Sure.. however, tool is stuck zipping data.

--

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>desta sysinfo
SvcToolsCollectorVersion = April 29, 2010
*****************************************
Checking and archiving old
collections if they exist..
*****************************************
*****************************************
Load environment variables from registry
using SetRegBat.exe
*****************************************
*****************************************
Collecting Info about this
Managed system.
*****************************************
*****************************************
Checking for currently
installed versions..
*****************************************
*****************************************
Gathering WCCProxy Information..
*****************************************
*****************************************
Gathering DESTA Information..
*****************************************
*****************************************
Gathering SEA Information..
*****************************************
*****************************************
OSEM Not installed skipping..
*****************************************
*****************************************
Gathering ISEE Information..
*****************************************
*****************************************
Gathering log files..
*****************************************
*******************************************
Gathering HealthCheck Job Information..
*******************************************
*****************************************
Clearing temporary files..
*****************************************
*****************************************
Zipping collected data..
Dennisb_2
Occasional Advisor

Re: Webes HealthCheck End-To-End Detection Failed

I have the same error. My system is running on VMWARE ESX or ESXi which the support document says it is supported but the HP engineer told me its not supported I got confused.

Any resolution for this?