Link to home
Start Free TrialLog in
Avatar of kmkrause2
kmkrause2

asked on

Event ID 770 - HP Foundation Agents

I know this was covered before, but the solution of upgrading to PSP 7.5 didn't resolve my problem.

I have a Proliant DL380 running Windows Server 2003. Each time the server starts or the Foundation Agents service is restarted, the System event log records event 770, "The Host Remote Alerter detected an error while attempting to retrieve data from key = CompaqHost\OsPerf\Component\Processor in the registry.  The data contains the error code."

The data in the error code is always 000000ea and sometimes the error itsel includes \CompaqHost\OSPerv\Component\Logical Disk.

I've run the PSP 8.0 upgrade and still the problem persists. I've verified all the files in Windows\System32\CPQMgmt\CqMgHost and all show version 8.0. I also confirmed the registry entries for the agent services (HKLM\System\CurrentControlSet\Services) all point to the correct file and path.

The problem initially started after removing iSCSI from th Active agents list to resolve another issue. On the restart of the HP Agents, I received a single instance of event ID 1795 stating that te SNMP module is older than the other modules. After that, I began receiving the event ID 770 messages on a regular basis. Yes, I've tried placing iSCSI back to Active but that didn't resolve the issue and I've verified that the SNMP.exe file is the Windows version 5.2.3790.3959 (srv03_sp2_rtm.070216-1710).

I've run ProcessMonitor against the cqmghost.exe process and found that it will often query a registry key and return with Name Not Found messages. It then creates the key and adds the current value. This happens each time the data is collected (changed the rate from 2 minute to 3 minutes) every 3 minutes, but the event log message is only generated 3 minutes after the Foundation Agents service initially starts.

Has any other resolution to this problem been found?? I know there were others that hadn't had their problem resolved with the PSP 7.5 upgrade.

Thanks,
Ken
Avatar of sandybridge
sandybridge
Have you tried the following:

Go to Control panel => HP Management Agents => Highlight the Performance Monitor agent and move it to the inactive list.

in addition please also try this trial and error:
Control panel => HP Management Agents => choose one of the Active Agents, moving it to the Inactive Agents. Save this configuration, and then moving this agent back to the Active Agents.

You may also try to edit the registry:
HKLM\SYSTEM\CurrentControlSet\Services\CqMgHost\Parameters\SubService(REG_MULTI_SZ) is edit.
erase "CPQPREF",and restart "Foundation Agents"

Hope it works fine.
Avatar of kmkrause2
kmkrause2

ASKER

Thanks for your response. I wasn't able to find a Foundation Agents in the Active Agents list (I beleive this uses the Host Information agent) but hesitated to test on a production server ;)

I did edit the registry as you suggested and restarted the Foundation Agents. Sure enough, the error didn't reappear. But, while removing the CPQPerf from the registry will certainly stop the error messages, it doesn't resolve the problem ;( Those that I answer to won't accept a bandaid as a fix. What I need to determine is the root cause and get that taken care of.

Thanks for your reply!
ASKER CERTIFIED SOLUTION
Avatar of sandybridge
sandybridge
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of kmkrause2
kmkrause2

ASKER

No, this server was built using 7.60 and the upgrade that was applied was 8.0. Is it possible that a fix from HP in 7.50 was re-broken in the later versions ;)

It will take some convincing to retro-grade back to 7.50

Thanks for the reply.
Avatar of kmkrause2
kmkrause2

ASKER

No chance for a retrograde. Looks like I'll be placing a call to HP tech support on this. In looking at their forum posts on this subject, it looks like I'm in for a long process ;) I don't know how soon this will be resolved.  How long will this question remain open if there are no other responses?

Thanks again to all.
Avatar of sandybridge
sandybridge
You are right. At this point even HP support is working for a workaround on the same issue :(, however, they have not come up with any perfect resolution. Please share your response with us. Meanwhile, I will also try to get more details of this error.
Avatar of kmkrause2
kmkrause2

ASKER

Thanks for all your help. I'll post here what I find from HP as I know this is a particularly problematic issue for a handful of people.
Avatar of kmkrause2
kmkrause2

ASKER

Did some digging on my own while waiting for HP callback.

Tested under PSP 8.0
Using Process Monitor and looking at the cqmghost.exe process, I found that when the agent starts, it creates the regstry key HKLM\System\CompaqHost\OSPerf\Components key. When the first data collection time rolls around (default is every 2 minutes) the process tries to read data from HKLM\System\CompaqHost\OSPerf\Components\Process\CPU001. This key and value don't exist, so the error is generated. The process then creates the key and value and populates the data. The next time data collection rolls around, the key, value and data are there so no message is generated

Subsequenly, I tested using a bench server and PSP 7.6. What I found there was that the process starts, creates the registry key HKLM\System\CompaqHost\OSPerf\Component\Processor and then creats the value and data for CPU001, CPU002 etc all before the first data collection cycle comes around. This is why there is no error message, because the key, value and data exist from the first time out.

Yeah, yeah, I know, going back to 7.6 would give me working agents and no messages, but we discussed that already ;)

More to come...
Avatar of kmkrause2
kmkrause2

ASKER

I got a response back from HP support stating that this was a problem with PSP 8.0 and either downgrading to 7.91 or waiting for a new fix were my options.

Oddly enough, I had posted my test results to the HP forum post regarding this error prior to contacting HP. When HP support responded, they also mentioned that this was being discussed in that very forum and that I should check it out to find out the information that I just gave them :D

I'll let admin award the points as they see fit. Retrograding will resolve the problem and is a supported fix by HP, so just because I choose to wait for an update shouldn't take away from your assistance.

Avatar of sandybridge
sandybridge
Very well. Thanks a lot for sharing your update and possible solution.
Avatar of kmkrause2
kmkrause2

ASKER

I would consider this question closed. HP has acknowledged that the problem exists in PSP 8.0. Options for resolution are to downgrade to 7.91 or wait for a fix to the PSP. In my case, we've chosen to wait for the fix.

Thanks for all the help!
Avatar of kmkrause2
kmkrause2

ASKER

I would consider this question closed. HP has acknowledged that the problem exists in PSP 8.0. Options for resolution are to downgrade to 7.91 or wait for a fix to the PSP. In my case, we've chosen to wait for the fix.

Thanks for all the help!
Avatar of kmkrause2
kmkrause2

ASKER

I would consider this question closed. HP has acknowledged that the problem exists in PSP 8.0. Options for resolution are to downgrade to 7.91 or wait for a fix to the PSP. In my case, we've chosen to wait for the fix.

Thanks for all the help!