Debugging the QoS Service Provider

• Microsoft Windows 2000 Server
• Microsoft Windows 2000 Advanced Server
• Microsoft Windows 2000 Datacenter Server

SUMMARY

You can generate diagnostic information by using the logging feature available for the Quality of Service (QoS) service provider.

MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

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.

Additional query words:

Keywords : kbenv kbtool
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbinfo