From: George Schneider on 20 Mar 2006 15:41 What is the the wbemess.log for? I found the following intresting entried in my log: (Mon Mar 20 11:47:08 2006.-1003472578) : Unable to activate event filter with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_HAS_STOPPED' (error 80041002). The filter is not active (Mon Mar 20 11:49:08 2006.-1003352578) : Unable to activate event filter with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_IS_OCCURRING' (error 80041002). The filter is not active (Mon Mar 20 11:49:08 2006.-1003352578) : Unable to activate event filter with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_HAS_STOPPED' (error 80041002). The filter is not active (Mon Mar 20 11:51:08 2006.-1003232578) : Unable to activate event filter with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_IS_OCCURRING' (error 80041002). The filter is not active (Mon Mar 20 11:51:08 2006.-1003232578) : Unable to activate event filter with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_HAS_STOPPED' (error 80041002). The filter is not active What does this mean? Is this something I should be concerned about?
From: v-jasont on 20 Mar 2006 21:12 Hello, Thanks for posting! The wbemess.log file contains information about what Windows Management Instrumentation (WMI) tried to do and contains any error messages. Based on my research, please follow below steps to register the OLEDB32.dll which could be causing the WMI to give the error message in the log. 1. Click Start, point to All Programs, point to Accessories, and then click Windows Explorer. 2. Click Tools, click Folder Options, click the View tab, and then click to clear the Hide protected operating system files check box. When the warning dialog appears click Yes, and then click OK. 3. In the Windows Explorer Folders pane locate the Oledb32.dll file in the following folder: Drive: \Program Files\Common Files\System\Ole DB 4. Right-click Oledb32.dll, click Properties, and then click the Version tab. Verify that the version is earlier than 2.80.1022.0. 5. Right-click Oledb32.dll, and then click Rename. Type the file name Oledb32.old, and then press ENTER. 6. On the Windows Explorer Folders pane locate a possible second instance of the Oledb32.dll file in the following folder: 7. Note Windir is the folder where Windows is installed. Drive: \ Windir \System32\Dllcache\Oledb32.dll 8. If the Oledb32.dll file exists, right-click Oledb32.dll, click Delete, and then click Yes to confirm. 9. With the Windows Server 2003 installation disk in your CD drive, click Start, click Run, and then in the Open box, type cmd , and then click OK. 10. At the command prompt type the following where CDdrive is the drive letter of your CD drive, and then press ENTER: 11. CDdrive : Type the following, and then press ENTER: cd I386 12. Type the following, and then press ENTER: expand oledb32.dl_ " Drive: \program files\Common files\system\Ole DB\oledb32.dll" 13. Type the following, and then press ENTER: expand oledb32.dl_ Drive: \ Windir \System32\Dllcache\Oledb32.dll 14. At the command prompt, move to the following folder. Drive: \Program Files\Common Files\System\Ole DB 15. Type the following, and then press ENTER: regsvr32 oledb32.dll. Click OK when you receive the following DllRegisterServer in oledb32.dll succeeded. 16. By default, Windows hides protected operating system files. To hide the protected operating system files, locate the Windows Explorer program. Click Tools, click Folder Options, click the View tab, click to select the Hide protected operating system files check box, and then click OK. 17. Restart your computer. Hope the information helps. If there is anything that is unclear, please feel free to let me know. Best Regards, Jason Tan Microsoft Online Partner Support Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- | Thread-Topic: wbemess.log | thread-index: AcZMXqlAmfCWbsUkTd2YSJo8s5aQpQ== | X-WBNR-Posting-Host: 209.244.152.162 | From: =?Utf-8?B?R2VvcmdlIFNjaG5laWRlcg==?= <georgedschneider(a)news.postalias> | Subject: wbemess.log | Date: Mon, 20 Mar 2006 12:41:27 -0800 | Lines: 20 | Message-ID: <BB8273F3-9807-48F9-9403-DB8F5501738F(a)microsoft.com> | MIME-Version: 1.0 | Content-Type: text/plain; | charset="Utf-8" | Content-Transfer-Encoding: 7bit | X-Newsreader: Microsoft CDO for Windows 2000 | Content-Class: urn:content-classes:message | Importance: normal | Priority: normal | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 | Newsgroups: microsoft.public.windows.server.general | Path: TK2MSFTNGXA03.phx.gbl | Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.windows.server.general:91780 | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 | X-Tomcat-NG: microsoft.public.windows.server.general | | What is the the wbemess.log for? I found the following intresting entried in | my log: | | (Mon Mar 20 11:47:08 2006.-1003472578) : Unable to activate event filter | with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_HAS_STOPPED' | (error 80041002). The filter is not active | (Mon Mar 20 11:49:08 2006.-1003352578) : Unable to activate event filter | with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_IS_OCCURRING' | (error 80041002). The filter is not active | (Mon Mar 20 11:49:08 2006.-1003352578) : Unable to activate event filter | with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_HAS_STOPPED' | (error 80041002). The filter is not active | (Mon Mar 20 11:51:08 2006.-1003232578) : Unable to activate event filter | with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_IS_OCCURRING' | (error 80041002). The filter is not active | (Mon Mar 20 11:51:08 2006.-1003232578) : Unable to activate event filter | with invalid class name 'HPQ_VT_STATUS_VIRUS_LIKE_ACTIVITY_HAS_STOPPED' | (error 80041002). The filter is not active | | What does this mean? Is this something I should be concerned about? |
|
Pages: 1 Prev: LSASRV; Event ID: 40968 Next: Task Scheduler service not starting |