Webes HealthCheck End-To-End Detection Failed

[Tuscani_1]

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:

[Frank Alden Smith]

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

[Tuscani_1]

Yeah.. tried that.. no help.

[GeraldR]

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]

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]

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]

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]

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

[Tuscani_1]

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]

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?

[BPE]

Check the entitlement list for your server!
If you do not see your VM SIM server, tell HP they should tell you how you get your VM Server to the list and the E2E error will disappear. To be sure that you have this problem you can use the wccproxy test command on your VM SIM server. The event will not be send to HP if you have the problem but you can get a local email if you have email notification enabled what seems to be the case because you saw the end 2 end error.

[GeraldR]

hi frank!

the desta sysinfo file has 9 mb, - uploads here have a max. limit of 1 mb.
any ther ideas to transfer the file?

i'll try to open a sr myself...

tnx! gerald

[Frank Alden Smith]

GeraldR,

You may e-mail it to frank.smith@hp.com so I can forward it directly to the software engineer working on this issue.

Take care,
frank

[Frank Alden Smith]

Dennisb,

Running Insight RSA A.05.50 is supported on ESXi and ESX VM. The following is from the A.05.50 Release notes:

With the A.05.50 release, the HP Insight Remote Support Advanced software is now supported on the following operating systems:
o Microsoft Windows Server 2008 R2
o VMware ESX and ESXi update releases to 3.x and 4.0
o VMware ESX and ESXi Server 4.1
o Microsoft Windows Storage Server 2008 Standard edition
o Microsoft Windows Storage Server 2008 Advanced edition

Take care,
frank

[BPE]

Hello Frank and Dennis

I did not find the forum article anymore but Brad or Brent submitted the workaround.

If you have SIM with RSA 5.50 it is possible that you do not see your SIm on a VM in the entitlement list. HP support should know this workaround.

I only remember that you need to add some text in the SIM system page ->tools -> set system properties "Operation system description" field e.g."VMware ESX Server" and you will see after the data exchange between SIM and WEBES your vm SIM Server in the entitlement list.
In this case if all the icons are green you should no longer get the E2E Error.

[Frank Alden Smith]

Dennisb,

The edits required to the system properties of the CMS, referred to by bpe, are as follows:

For a CMS running on virtual server, you need to change the following system property values to ensure the CMS appears on Remote Support Systems List displayed on the Entitlement tab:

o System subtype 1: Select 'HP ProLiant'.
o Product Model: Type in ProLiant (Exactly as shown with the letters 'P' and 'L' capitalized)
o Operating System Description. This must be a valid Microsoft Windows operating system supported on the CMS.

Take care,
frank

[Tuscani_1]

desta sysinfo finally finished.. however, the zip file is 40MB.. you can download from here:

https://www.onlinefilefolder.com/1szJo0AXreClaL

[Frank Alden Smith]

Tuscani,

Thanks, I got the file and will send it to the software engineer. Hope to let you know something soon.

Take care,
frank

[Tuscani_1]

Thanks.. also.. my CMS is not a VM, it is a 460c G6

:)

[BPE]

1. Do you see your BL460c G6 in the entitlement list under options -> Remote Support ->entitlement?
2. Did you install the Proliant Support Pack on this server?

[Dennisb_2]

Hi Frank,Thanks. I'll check that out and will post later for the result.

[Tuscani_1]

bpe, the 8.40 PSP is installed. However, I am upgrading to 8.60 now. The server is in the entitlement list and all icons are green.

[Tuscani_1]

Just got off the phone with HP Support. here is what we did:

1. Set Country Code\Site Name\PrimaryContact info on all servers

2. Verified entitlement and SEA

3. Disabled the E2E notifications

Start > Run > CMD

desta whc e2e off

[Frank Alden Smith]

Tuscani,

I got an e-mail from the HP engineer about your log files, in which he said:

o The DESTA service was having some problems in analysis (might be in hung state), and WEBES sent E2E notices starting Mon, 4 Oct 2010 21:05:03 -0500 and ending 9 Oct 2010 05:05:01 -0500 one E2E every 8 hours.
o The zipped data contains only WEBES.114.log starting 9th October, when things started back to normal. I couldn't determine the cause of the failure between Oct 4th to 9th as no WEBES log files available. There weren't any E2E after 9th October.

I assume the problem continued or else you would not have disabled e2e notifications. Is that correct?

Take care,
frank

[Tuscani_1]

Correct.. I was getting the error everyday. The last few days it has been stable.. however, I am going to disable the healthcheck anyway now that I know WEBES and Remote Support is healthy.