ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

cqmghost.exe error

 
Dave..B
Advisor

cqmghost.exe error

This popped up on the console of my server today. Any ideas what may have caused this? This is a DL380G3, running W2K Sp4 with the 7.00 version of the ProLiant Support Pack.


Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 3/1/2004
Time: 9:23:46 AM
User: N/A
Computer: MYSERVER
Description:
Application popup: cqmghost.exe - Application Error : The instruction at "0x7c57b59d" referenced memory at "0x00000007". The memory could not be "written".

Click on OK to terminate the program
Click on CANCEL to debug the program
2 REPLIES
Sunil Jerath
Honored Contributor

Re: cqmghost.exe error

Hello David,
Please have a look at the following Customer Advisory:

CUSTOMER ADVISORY


EM030402_CW01 REVISION: 0

ProLiant Server In A Windows NT 4.0 Or Windows 2000 Environment Running Different Versions Of Insight Manager Agents May Experience Slower Performance


--------------------------------------------------------------------------------
RELEASE DATE:
April 2003
LAST UPDATED: 04 August 2003

DESCRIPTION
A ProLiant server running Microsoft Windows NT Server 4.0 or Microsoft Windows 2000 Server may experience increasingly slower performance accompanied by a steady increase in the CPU utilization of the Insight Manager Foundation Agent (CQMGHOST.EXE). The issue is caused by the Software Versions Table in the Windows Registry growing steadily to include thousands of entries and can be verified by reviewing the number of registry entries found in the following Windows Registry Key:

HKLM/System/CompaqPermanent/Host/Component/SoftwareVersions/Table

The number of entries should be approximately 100 (or fewer).

Note: The server may be unable to load the Windows Registry if it grows too large. The following excerpt from Microsoft Knowledge Base Article 269075 further explains this situation:

Windows 2000 may be unable to load the registry if it is too large. This issue can occur when a process writes too much data to the System subkey in the registry. The System subkey is designed to contain only the information that is necessary to boot the computer.

Computers that are based on Intel architecture or ARC (RISC) architecture can only use 16 megabytes (MB) of memory at this stage of the boot process. The System registry subkey has to share the 16 MB with the loader, kernel, HAL, and boot drivers. In some instances, the size of the System subkey may be 13 MB or larger.

This Knowledge Base article is located at the following URL:

http://support.microsoft.com/default.aspx?scid=kb;en-us;269075

ProLiant servers running Microsoft Windows NT Server 4.0 or Microsoft Windows 2000 Server that meet either of the following conditions are affected:

Compaq Storage Agents Version 4.90 (or later) were initially loaded, but later were downgraded to a version below 4.90.
Insight Manager Foundation Agents Version 4.90 (or earlier) are installed and running with Compaq Storage Agents later than version 4.90.
Note: HP does not recommend or support installing different versions of the Insight Manager Agents on the same server.

SCOPE
Any ProLiant server running Microsoft Windows NT Server 4.0 or Microsoft Windows 2000 Server that meets either of the following conditions:

Compaq Storage Agents Version 4.90 (or later) were initially loaded, but later were downgraded to a version below 4.90.
Insight Manager Foundation Agents Version 4.90 (or earlier) are installed and running with Compaq Storage Agents later than version 4.90.

RESOLUTION
Upgrade ALL of the Insight Manager Agents for Windows to Version 4.90 (or later). HP does not recommend or support installing different versions of the Insight Manager Agents on the same server.
HARDWARE PLATFORMS AFFECTED: ProLiant BL e-Class (BL10e Server Blade, Server Blade Enclosure), ProLiant BL p-Class (BL20p G2 Server Blade, BL20p Server Blade, BL40p Server Blade, Diagnostic Station), ProLiant DL320, ProLiant DL320 G2, ProLiant DL360, ProLiant DL360 G2, ProLiant DL360 G3, ProLiant DL380, ProLiant DL380 G2, ProLiant DL380 G3, ProLiant DL560, ProLiant DL580, ProLiant DL580 G2, ProLiant DL590/64, ProLiant DL740, ProLiant DL760, ProLiant DL760 G2, ProLiant ML310, ProLiant ML330, ProLiant ML330 G2, ProLiant ML330e, ProLiant ML350, ProLiant ML350 G2, ProLiant ML350 G3, ProLiant ML370, ProLiant ML370 G2, ProLiant ML370 G3, ProLiant ML530, ProLiant ML530 G2, ProLiant ML570
COMPONENTS AFFECTED: Non-hardware specific
OPERATING SYSTEMS AFFECTED: Microsoft (Windows 2000 Advanced Server, Windows 2000 Server, Windows NT 4.0 Server 4.0)
SOFTWARE AFFECTED: Management Agents (All versions)
THIRD PARTY PRODUCTS AFFECTED: None
DOWNLOADABLE FILES: None
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.


©Copyright 2003, 2004 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither HP or its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett-Packard Company and the names of Hewlett-Packard products referenced herein are trademarks of Hewlett-Packard Company in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

Regard
Bernard Čokorilo
Occasional Visitor

Re: cqmghost.exe error


I am having the same problem on Windows server 2003

(Using proliant ML350 G3 1.2Gb RAM 2x70Gb hard drive.Insight agents version don't know,but not up to date,will an update help as written in previous reply).

Thank you!