Article ID: 244678 - Last Review: March 1, 2007 - Revision: 2.2 Debugging the QoS Service ProviderThis article was previously published under Q244678 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SUMMARY
You can generate diagnostic information by using the logging feature available for the Quality of Service (QoS) service provider.
MORE INFORMATIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk. You can use the logging feature to monitor a program's usage of the QoS Application Programming Interface (API) set as well as the QoS service provider itself. Two log files are created during logging: Qossp.aid and Rapilib.aid. These files are stored in the %SystemRoot%\System32\Logfiles folder. To enable logging, you must modify the registry. To enable QoS service provider logging, add the following value to the registry:
Value Name: EnableDebugAid Key: HKLM\System\CurrentControlSet\Services\Rsvp\Parameters Value Type: REG_DWORD Valid Range: 0 - 1 Created by installation: No Description: This key enables logging for the QoS service provider. A value of 0 generates a diagnostic log (Qossp.aid) containing information about how a program is using the generic QoS API. A value of 1 generates a diagnostic log (Rapilib.aid) that displays how well the QoS service provider itself is working. | Article Translations
|
Back to the top
