Problema:
Log Name: Application
Source: Application Error
Date: 3/10/2010 4:24:35 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: VS5.opsmgr.net
Description:
Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794
Faulting module name: ole32.dll, version: 6.1.7600.16385, time stamp: 0x4a5be01a
Exception code: 0xc0000005
Fault offset: 0x0000000000039389
Faulting process id: 0x180
Faulting application start time: 0x01cabfafa91cc252
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\ole32.dll
Report Id: b45b5a1d-2c93-11df-ac21-001b213a78be
Quando questo accade su un DB server, non è bello.
Il software di monitoring che adoperiamo (Zenoss) fa uso della classe WMI Win32_service per interrogare il DB server.
Questo causa il summenzionato memory leak.
Soluzione:
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=981314&kbln=en-us
Nessun commento:
Posta un commento