Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: The Wmiprvse.exe process may terminate unexpectedly on a primary Host Integration Server 2000 server or on a primary Host Integration Server 2004 server


View products that this article applies to.

Symptoms

The Wmiprvse.exe process may terminate unexpectedly on a primary Microsoft Host Integration Server 2000 server or on a Host Integration Server 2004 server that is configured as the primary configuration server for the Host Integration Server subdomain. When the Wmiprvse.exe process terminates, the following Error event may be logged in the Application log:

Event ID: 1000
Event Source: Application Error
Description: Faulting application wmiprvse.exe, version Version, faulting module mngbase.dll, version Version, fault address Address.

Notes
  • When the Wmiprvse.exe process terminates, Host Integration Server features that use the Host Integration Server Windows Management Instrumentation (WMI) providers do not function correctly. For example, the SNA LU6.2 Resync TP service cannot run WMI queries when the Wmiprvse.exe process terminates. When WMI queries do not run, the SNA LU6.2 Resync TP service cannot perform the exchange log sequence that is required to establish 2-Phase Commit (2PC) transactions.
  • This issue also occurs in a Microsoft Host Integration Server 2006 environment.

↑ Back to the top


Resolution

Host Integration Server 2000

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Mngagent.exe5.0.0.2099131,34425-Oct-200622:19x86SP3
Mngbase.dll5.0.0.2099151,82425-Oct-200622:19x86SP3
Mngcli.exe5.0.0.2099131,34425-Oct-200622:19x86SP3
Mngext.dll5.0.0.209928,94425-Oct-200622:19x86SP3
Mngsna.dll5.0.0.2099114,96025-Oct-200622:19x86SP3
Snaadmin.dll5.0.0.2099409,87225-Oct-200622:19x86SP3
Snacfg.dll5.0.0.2099291,08825-Oct-200622:19x86SP3
Snacfg.exe5.0.0.2099250,12825-Oct-200622:19x86SP3
Snaevent.dll5.0.0.2099483,60025-Oct-200622:18x86SP3
Snaole.dll5.0.0.2099643,34425-Oct-200622:19x86SP3
Snaolewmi.dll5.0.0.2099651,53625-Oct-200622:19x86SP3
Snarpc.dll5.0.0.2099151,82425-Oct-200622:19x86SP3
Wmisna.dll5.0.0.2099483,60025-Oct-200622:19x86SP3
Wmisna.mofNot Applicable92,31726-Jan-200621:32Not ApplicableSP3
Wmisnastatus.dll5.0.0.209994,48025-Oct-200622:19x86SP3
Wmisnastatus.mofNot Applicable26,14826-Jan-200621:32Not ApplicableSP3
Wmisnastatus_xp.mofNot Applicable26,09220-Oct-200523:49Not ApplicableSP3
Wmisna_xp.mofNot Applicable92,16506-May-200518:05Not ApplicableSP3
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

Host Integration Server 2004

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Mngbase.dll6.0.2047.096,25625-Oct-200622:18x86SP1
Wmisna.dll6.0.2047.0281,08825-Oct-200622:19x86SP1
Wmisna.mofNot Applicable90,32725-Oct-200622:05Not ApplicableSP1
Wmisnastatus.dll6.0.2047.067,58425-Oct-200622:19x86SP1
Wmisnastatus.mofNot Applicable24,61725-Oct-200622:04Not ApplicableSP1
Wmisnastatus_xp.mofNot Applicable24,65525-Oct-200622:04Not ApplicableSP1
Wmisna_xp.mofNot Applicable90,31925-Oct-200622:05Not ApplicableSP1
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

Host Integration Server 2006

To resolve this problem, obtain the latest service pack for Host Integration Server 2006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
979497� How to obtain the latest Host Integration Server 2006 service pack

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

These common Host Integration Server features and functions use the Host Integration Server WMI providers:
  • The SNA LU6.2 Resync TP service
  • Host Integration Server clients that are configured to use an Active Directory organizational unit to locate servers
  • Microsoft Host Integration Server 2004 Management Pack for Microsoft Operations Manager 2005
  • Custom applications that use the Host Integration Server WMI providers for Host Integration Server administration and management purposes
  • Host Integration Server services such as SnaPrint and TN3270, and SNA applications that run locally on Host Integration Server systems when the Support Active Directory Clients check box is selected
  • Host Integration Server Administration and Management components

Stack output

If Dr. Watson (Drwtsn32.exe) is the default debugger, and if it is configured to create a User.dmp file, the stack output data that appears in the User.dmp file may resemble one of the following stack output listings.

Stack output 1

eax=00d73008 ebx=07b8cff8 ecx=081ee8d0 edx=7c82ed54 esi=00000000 edi=00000189eip=60982608 esp=081ee94c ebp=081ee94c iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010202
mngbase!GetMyProcEnv+0x8: 60982608 8b4010           mov     eax,[eax+0x10]    ds:0023:00d73018=????????
0:009>kb
ChildEBP RetAddr  Args to Child              
081ee94c 609825ab ffffffff 081ee964 6098c81c mngbase!GetMyProcEnv+0x8 
081ee960 6098a11d 0000000d 00000000 7c830a90 mngbase!FindManageType+0xb
081eeb90 6770c24a 0000000d 0009465c 081eec00 mngbase!CManage::FindUniqueChild+0x9d 
081eebe8 6771bde2 00000000 081eec00 00000004 snaadmin!CSnaItem::CreateManage+0x4a 
081eec04 6770d691 007e3750 00094644 081eec2c snaadmin!CAppcSessionItem::Terminate+0x22 
081eec14 6770e628 00000189 00b0000c 00b00008 snaadmin!CSnaItem::GetItem+0x31 
081eec2c 612065e8 00000189 00094644 081eece4 snaadmin!CSnaItem::EnumServ2+0x8 
081eec64 6120657b 07b8cff8 081e0004 00000000 snacfg!Enumerate+0x48 
081eec88 6770e729 00b0000c 081e0004 00000000 snacfg!SnaEnumerateRecords+0x4b 
081eecfc 68d19f7a 00126f2c 081eed28 00000000 snaadmin!CSnaItem::GetServiceGroup+0x69 
081eed24 73f4cfe2 00126f2c 73f35a63 081eeda0 snaolewmi!CSnaDomain::GetServiceGroup+0x2a 
081eeda0 73f3684f 00000008 00000000 081eeec0 mfc42!_AfxDispatchCall+0x12 
081eee34 73f36f46 007f4390 00000001 73ec2504 mfc42!COleDispatchImpl::Invoke+0x47f 
081eeef4 73f37205 0000002d 00000001 00000009 mfc42!COleDispatchDriver::InvokeHelperV+0x2e6 
081eef14 65389eb5 081eefa0 0000002d 00000001 mfc42!COleDispatchDriver::InvokeHelper+0x25 
081eef40 65392d08 653e0300 653e51a8 081eefdc WmiSna!ISnaDomain::GetServiceGroup+0x25 
081eef54 65393356 081eefa0 081eefd0 00000000 WmiSna!CSnaOleProvider::GetSnaCollection+0x18 
081eefe8 6939b30f 007cf6e8 00000000 007cf6e8 WmiSna!CSnaOleProvider::EnumerateInstances+0x1c6 
081eeffc 693a0556 007cf6e8 00000000 00000000 framedyn!Provider::CreateInstanceEnum+0x21 
081ef4e8 01018ba7 00816ed8 001219a4 00000000 framedyn!CWbemProviderGlue::CreateInstanceEnumAsync+0x1bc

Stack output 2

0:006> kv

eax=01402f18 ebx=6179607c ecx=00000017 edx=7c82ed54 esi=61781adc edi=00866ed0
eip=61788c25 esp=009ae790 ebp=60092e20 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206

mngbase!FindManageType+0x6: 61788c25 8b4010   mov     eax,[eax+0x10]    ds:0023:01402f28=????????
ChildEBP RetAddr  Args to Child              
009ae790 6178653e 0000000a 00863a68 077ffea8 mngbase!FindManageType+0x6 (FPO: [1,0,1]) (CONV: stdcall) 
009ae98c 67b2c453 0000000a 00126ea4 00000000 mngbase!CManage::FindUniqueChild+0x8a (FPO: [Uses EBP] [5,121,4]) (CONV: thiscall) 
009ae9c4 67b35d28 00000000 00000000 00000000 snaadmin!CSnaItem::CreateManage+0x54 (FPO: [Non-Fpo]) (CONV: thiscall) 
009ae9d4 67b2d7f2 00000001 009aea4c 009aea14 snaadmin!CLu3270Item::StartManage+0xf (FPO: [0,0,0]) (CONV: thiscall) 
009ae9e4 67b2d91a 000001c7 0104000c 009aea4c snaadmin!CSnaItem::GetItem+0x50 (FPO: [Non-Fpo]) (CONV: stdcall) 
009aea14 67b297e2 000e1cdc 0104000c 00000000 snaadmin!CSnaItem::NewGroup+0x89 (FPO: [Non-Fpo]) (CONV: stdcall) 
009aea2c 624c8ed8 00000000 00864e90 009aeaa4 snaadmin!CUserItem::GetLu3270Group+0x16 (FPO: [0,0,1]) (CONV: thiscall) 
009aea48 73f4cfe2 73f35a63 009aeab0 009aeaa4 snaolewmi!CSnaUser::GetAssignLu3270+0x15 (FPO: [Non-Fpo]) (CONV: thiscall) 
009aeab0 73f3684f 00000004 00000000 009aebac mfc42!_AfxDispatchCall+0x12 (CONV: stdcall) 
009aeb44 73f36f46 00864ea0 00000001 73ec2504 mfc42!COleDispatchImpl::Invoke+0x47f (FPO: [Non-Fpo]) (CONV: stdcall) 
009aebe0 73f37205 00000009 00000001 00000009 mfc42!COleDispatchDriver::InvokeHelperV+0x2e6 (FPO: [Non-Fpo]) (CONV: thiscall) 009aec00 6210cd32 009aef88 00000009 00000001 mfc42!COleDispatchDriver::InvokeHelper+0x25 (FPO: [Non-Fpo]) (CONV: cdecl) 
009aec24 62122c6b 62121f20 009aef88 693a7ba5 WmiSna!ISnaWorkstation::GetAssignLuLua+0x16 (FPO: [Non-Fpo]) (CONV: thiscall) 009aec28 62121f20 009aef88 693a7ba5 00000000 WmiSna!CSna3270LusForUserAtWorkstation::GetLuCollection+0x9 (FPO: [1,0,0]) (CONV: thiscall) 
009aeea8 62122711 009aef88 009aef34 009aef48 WmiSna!CSnaBaseQueryLusForUserAtWorkstation::GetLusOnServiceForUser+0x2a (FPO: [Non-Fpo]) (CONV: thiscall) 
009aeef8 6212180b 009aef88 009aef34 009aef48 WmiSna!CSnaLusForUserAtWorkstation::GetLusForUser+0x100 (FPO: [Non-Fpo]) (CONV: thiscall) 
009aefbc 6939b5ec 00865d18 009af004 00000000 WmiSna!CSnaBaseQueryLusForUserAtWorkstation::ExecQuery+0x34f (FPO: [Non-Fpo]) (CONV: thiscall) 
009aefdc 693a0136 00865d18 009af004 00000000 framedyn!Provider::ExecuteQuery+0x5d (FPO: [Non-Fpo]) (CONV: thiscall) 
009af4d0 010193ec 0079fb70 07682f3c 00109b24 framedyn!CWbemProviderGlue::ExecQueryAsync+0x235 (FPO: [Non-Fpo]) (CONV: stdcall) 009af520 01019591 00000000 07682f3c 00109b24 wmiprvse!CInterceptor_IWbemSyncProvider::Helper_ExecQueryAsync+0x44d (FPO: [Non-Fpo]) (CONV: thiscall)

↑ Back to the top


Keywords: kbpubtypekc, kbfix, kbbug, kbhotfixserver, kbqfe, kbautohotfix, KB916137

↑ Back to the top

Article Info
Article ID : 916137
Revision : 2
Created on : 2/5/2010
Published on : 2/5/2010
Exists online : False
Views : 444