In the first article of a two-part series, the authors present a high-level overview of the ETW technology and core OS instrumentation.
Alex Bendetov, Insung Park
MSDN Magazine September 2009
View Complete Post
In Part 2, the authors cover core OS Event Tracing for Windows (ETW) events as well as present simple scripts to demonstrate a few basic accounting techniques on some of the OS events introduced.
MSDN Magazine October 2009
Windows Management Instrumentation (WMI) is based on an industry-wide standard for notifications used to manage objects and devices across a network. By receiving WMI events, an application can be notified of changes to data in WMI itself. This allows the developer to notify the consuming application that certain system configuration data has changed, without the application having to poll WMI continuously for this data. The author presents an explanation of the different types of events in WMI, then goes on to develop an event provider.
J. Andrew Schafer
MSDN Magazine September 2001
It's difficult to troubleshoot any application without a trail of clues to follow, and cloud apps are no different. We look at how logging and tracing are enabled for Windows Azure, and how you can use Windows PowerShell to manage diagnostics for a running service.
MSDN Magazine June 2010
MSDN Magazine May 2007
Building on his article published in the June issue, which demonstrated several ways to get process and DLL-related information from APIs such as PSAPI, NTDLL, and TOOLHELP32, the author presents some unusual ways to get system-oriented info that you can easily integrate in your own toolkit. There are three tools included as samples: LoadLibrarySpy, which monitors an application and detects which DLLs are really loaded; WindowDump, which retrieves the content and a detailed description of any window; and FileUsage, which redirects console-mode applications to tell you which process is using any opened file.
MSDN Magazine August 2002
DirectShow is an API that enables Windows applications to control a wide variety of audio/video input devices including (but not limited to) DV camcorders, Web cams, DVD drives, and TV tuner cards. It provides out-of-the-box support for a variety of formats, from WAV and AVI to Windows Media. DirectShow is also extensible, enabling third parties to support their own specialized devices, formats, or processing components. This article introduces the basic concepts behind DirectShow and gives a step-by-step tutorial showing how to create your own video effect filter.
Michael Blome and Mike Wasson
MSDN Magazine July 2002
DLL conflict problems can be tough to solve, but a large number of tools are available to help. There are also many Windows APIs that you can use to build custom debugging tools. Three such tools are discussed here and provided as samples. DllSpy lists all the DLLs loaded in the system and the processes that are using them. ProcessSpy enumerates the running processes and exposes the DLLs they are using, and ProcessXP displays the list of concurrent running sessions for Windows XP.
MSDN Magazine June 2002
This article provides an overview of Windows Management Instrumentation, a technology that exposes a wide variety of system and device information through a standard API. With WMI, management information is exposed by following the object oriented structure outlined in the Common Information Model (CIM), which relies on inheritance for reuse and standardization of object classes that represent system devices. This article briefly describes querying WMI for information using a query language much like SQL called Windows Management Instrumentation Query Language (WQL), existing system classes, handling system events, and security in WMI.
MSDN Magazine May 2000
The new Windows Management Instrumentation (WMI) technology for Windows 2000, Windows NT 4.0, and Windows 98 provides powerful scripting technology that can be used to administrate Windows-based systems. With WMI, you can create scripts to simplify management of devices, user accounts, services, networking, and other aspects of your system. This piece will introduce you to WMI and the WMI Scripting Object Model, taking a look at the available objects, methods, and properties. Along the way, you'll see how these elements can be used to create system management scripts.
MSDN Magazine April 2000
This error started on 29 April and I cannot get rid of it...ÃÂ My search works fine, both site and people.ÃÂ AD profile import works fine.ÃÂ Full and incremantal crawls work as scheduled.ÃÂ Just that this error keeps showing up every five minutes in one of two WFE's.ÃÂ The other WFE does notÃÂ receive this error
I have verified all Security Configuration/Service Accounts, verified all Services on Server/Search accounts, Stopped/Restarted all search, and verified SSP accounts.ÃÂ The last thing I did was verify there was an indexer attached to the SSP...
I set the diagnostic logging to verbose and the only thing that stood out around the time of the error was
System.Data.SqlClient.SqlException: Invalid object name 'AR_CacheCounters'.
SqlError: 'Invalid object name 'AR_CacheCounters'.'ÃÂ ÃÂ ÃÂ Source: '.Net SqlClient Data Provider' Number: 208 State: 1 Class: 16 Procedure: 'proc_ar_GetCacheInvalidationCountersWithCount' LineNumber: 3 Server: 'SERVER'