event id 770 registry problem

[Richard Selke]

the event viewer on a dl385 5 displays and event id 770.

The host remote alerter detected an error while attempting to retrieve date from key = CompaqHost\OsPerf\Component\LogicalDisk in the registry.

The box is a proliant dl385 g4.

can ya help with the fix????

[Prashant (I am Back)]

Hi,

Refer to last post
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=566420

To remediate:
Go to Control Panel - open HP Management Agents.
Move the NIC Information from Inactive Agents to Active Agents. (In my instance, I had 2)
Stop and restart SNMP and HP Insight Services.

The error will disappear.

In my case, the following messages appeared:
The Compaq Common Cluster Agent has successfully initialized.
The Compaq Cluster Management NT Extension Agent has successfully initialized.

Regards,
Prashant S.

[Richard Selke]

was already done no help

[Prashant (I am Back)]

Hi,

What is registry size?
Is event occur at any particular intervals?
Did we tried reloding mangement agent on the same server?

Regards,
Prashant S.

[Wilfrid David]

I have the same problem since the version 7.41 of HP Agents.

Event Type: Warning
Event Source: Foundation Agents
Event Category: Alerter
Event ID: 770
Date: 17/01/2006
Time: 13:08:50
User: N/A
Computer: xxxxxx
Description:
The Host Remote Alerter detected an error while attempting to retrieve data from key = CompaqHost\OsPerf\Component\LogicalDisk in the registry. The data contains the error code.
Data:
0000: ea 00 00 00 ê...

This message appears about every hours.

What's the problem ?
I have already uninstalled and reinstalled.

Thank you for your help.

[Tim McCabe]

I have the exact same issue on a DL385 running WIN2003 SP1 with the 7.41 agents.
My server has ASR'ed twice. This is a brand new build on the server with nothing else running.

Event Type: Warning
Event Source: Foundation Agents
Event Category: Alerter
Event ID: 770
Date: 1/17/2006
Time: 3:07:03 PM
User: N/A
Computer: SERVER1
Description:
The Host Remote Alerter detected an error while attempting to retrieve data from key = CompaqHost\OsPerf\Component\LogicalDisk in the registry. The data contains the error code.
Data:
0000: ea 00 00 00 ê...

[Marco Badoux]

Hi,
I have a DL380 with the same error. I have update the drivers with Version Control Agents so every driver is up to date.

I get the following error in Eventviewer:
Source: Foundation Agents
Category: Alerter
Evend Id: 770

The Host Remote Alerter detected an error while attempting to retrieve data from key = CompaqHost\OsPerf\Component\LogicalDisk in the registry. The data contains the error.

This message appears every hour in my eventviewer.

Has some one an idea how to solve this problem?

Greetings
Marco

[Graham Drew]

We have it too - but only on clustered servers.

It "seems" to be associated with the cluster disks that are missing, i.e. mounted on the other member of the cluster.

?

Graham (not Lindsay)

[Tim McCabe]

My server is not a cluster and is brand new. My errors occur about every 10 - 15 minutes. Since this is a new server I have been copying mass amounts of data to it. Every time I put it under load, it ASR's.

[Stan Hurton]

We have this on non-clustered servers as well.

[agents]

Move the 'performance monitor' entry from active to inactive list in the agent control panel window to stop the error message in event viewer.

[Tim McCabe]

This sounds like a potential "Work Around" not a fix. Will this prevent the ASR?

[Ben Vallance]

We also have the same problem on several servers we recently upgraded support software on. Both clustered and non clustered.

We are running PSP 7.40b with updated agents to 7.41.0.0
----------------------------------------------
Event ID: 770

Description:
The Host Remote Alerter detected an error while attempting to retrieve data from key = CompaqHost\OsPerf\Component\LogicalDisk in the registry. The data contains the error code.
Data:
0000: ea 00 00 00 à ª...
----------------------------------------------

We have logged a case with HP and they tell us there is no fix for it.........
We are not experiencing ASR and HP have informed us this will not have an impact on the performance of the server

We are testing the workaround of setting the performance monitor agent to inactive and look forward to yet another bug fix to the 7.4 agents

[Tim McCabe]

Here is a little more info. I have 3 DL385â s with the 7.41 agents on them. Two of them are the 2.6Ghz model and have the same problem. The 2.4Ghz model seems unaffected.

Here are your agent options:
Prior to 7.4: bad HBA drivers
7.4: High CPU
7.41: Foundation Agent errors and ASR

HP can we get a workable set of agents?????

[Tim McCabe]

I have uninstalled the 7.41 "HP Insight Management Agents" via add/remove programs on one of my servers and rebooted. I then applied the 7.40 PSP's and rebooted. This appears to have eliminated the 7.41 foundation error but I am now at risk for the high CPU issue.
I have verified the 7.41 foundation error along with the ASR on multiple servers now.

[Bernhard Schmid]

Same for me. DL 380 G4, Cluster, fresh install of Win 2003 Enterprise Server, SP1. Additionally the SNMP-service crashes regularly :-(

[Richard Selke]

First thanks for the input. I feel the same as far as the frustration on this issue. My server having this issue is not clustered. I have used the work around. in my case not fatal but still annoying.

hp should take notice.

should have a patch somwhere??

anyway keep pluggin along

Rick

[Ben Vallance]

Has everyone with this problem logged a call with HP and left it open? When we logged a call about it the guy said there was no fix and could he close the call!!

Unless everyone logs calls this problem is likely to be ignored or set to a low priority.

Setting the performance monitor agent to inactive proved successful at stopping the events appearing, but that is hardly getting at the root of the problem.

If the performance monitor agent is provided it should work without filling the event log with hundreds of errors. We have no option but turning it off.

[Tim McCabe]

Yes, I have opened a case. After having the case open for nearly a week now, I have asked my case to be escallated. At least they admitted to me that they know it is an agent issue. They feel that it may be particular to certain firmware revisions.

If you have the problem, please open a case. The more data the better. If you have any detailed data besides DL385 G1 such as processor speed or that all of your firmware is current via Insight manager repository, that might be helpful as well. And likewise if you have the 7.41 agents installed on another server and you are NOT having a problem, please note the details of that server as well.

Thanks!

[Tim McCabe]

I have received an HP advisory regarding this issue: c00568181
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00568181

While this advisory does not resolve my particular issue, it may help some of you, so I thought I would pass it on.

[Ben Vallance]

bump to be above the duplicated thread.

[Tim McCabe]

HP still has not been able to resolve my issue. I have been able to duplicate this on several different hardware platforms.
My gut feeling is that the ultimate fix will come out with the new 7.5 PSP's but there is no release date for them.

[Torbjorn Mohn]

I just discovered that I could fix the problem on all 4 of my servers by setting up the Management Agents (Control Panel/HP Management Agents) again and restarting the service. I removed the Performance monitor, saved, then open it again, added the Performance monitor again and saved.

I assume that the problem may have to do with the fact that I updated the agent to ver 7.41 "on the fly", without rebooting the server?

Anyway, everything is working OK now on all 4 servers without the error.

[marcos ortega]

i try this but it doesn't work, i still have the error.

[Nicolas Melay]

Same problem here with agents 7.41 on a DL385 and a bunch of ML350 G4s.
I have just disabled the Performance Monitor agent on the DL385, .

I found an intersting detail on the registry key though, and I'd like share it.

Run the registry editor and open the HKLM\SYSTEM\CompaqHost\OsPerf\Component\LogicalDisk key.
There you can try and modify the LocalDiskxxx values.
Leave regedit open, wait for a few minutes, and try to modify the values again.
You'll get an error saying the value is unreadable.
Press F5 and you can read and modify it again.

So here's my take on it.
The Performance Monitor agent gathers information from Windows and writes it to these registry values. But it does it the wrong way, deleting and re-creating the value on each update.
On its side, the Host Remote Alerter agent gathers these stats from the registry, first enumerating the LocalDiskxxx entries and then reading each separate value.
Every now and then, a "race condition" occurs, the value has been deleted by the Performance Monitor agent before the Host Remote Alerter agent managed to read it, and failure to do so is reported in the event log.

Other agents may be affected by the same problem (see the other id 770 thread).

Now if I'm correct here, HP will hopefully come up with a fix very soon.