Microsoft KB Archive/887013

= How to enable the Volume Shadow Copy service's debug tracing features in Microsoft Windows Server 2003 =

Article ID: 887013

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
 * Microsoft Windows Server 2003 R2 Datacenter x64 Edition
 * Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
 * Microsoft Windows Server 2003 R2 Enterprise x64 Edition
 * Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003 R2 Standard x64 Edition

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



INTRODUCTION
This step-by-step article describes how to enable the Volume Shadow Copy service's debug tracing features in Microsoft Windows Server 2003.



MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To enable the Volume Shadow Copy service's debug tracing features in Windows Server 2003, follow these steps:  Click Start, click Run, type regedit, and then click OK. In Registry Editor, locate the following registry subkey:

 In the left pane, right-click VSS, point to New, and then click Key. Type Debug, and then press ENTER. In the left pane, right-click Debug, point to New, and then click Key. Type Tracing, and then press ENTER. In the left pane, right-click Tracing, point to New, and then click DWORD Value.</li> Type TraceLevel, and then press ENTER.</li> Double-click TraceLevel, and then type ffffffff in the Value data box. That is, type f eight times in the Value data box. Click OK.

Note The TraceLevel registry entry determines the type of debug tracing that will occur. A value of 0 (the default) indicates that no tracing will occur. A value of ffffffff turns on tracing for all events.</li> In the left pane, right-click Tracing, point to New, and then click DWORD Value.</li> Type TraceEnterExit, and then press ENTER.</li> Double-click TraceEnterExit, type 1 in the Value data box, and then click OK.

Note The TraceEnterExit registry entry determines whether the entry and exit information of the function is output to the trace file and to the debug output stream. A value of 0 (the default) indicates that no entry and exit information of the function is output. A value of 1 indicates that the entry and exit information of the function is output.</li> In the left pane, right-click Tracing, point to New, and then click DWORD Value.</li> Type TraceToFile, and then press ENTER.</li> Double-click TraceToFile, type 1 in the Value data box, and then click OK.

Note The TraceToFile registry entry determines whether trace information is output to the trace file. A value of 0 (the default) indicates that no trace information is output to the trace file. A value of 1 indicates that the trace information is output to the trace file. If you set the value to 1, you must also set the TraceFile registry entry. To set the TraceFile registry entry, follow these steps: <ol style="list-style-type: lower-alpha;"> In the left pane, right-click Tracing, point to New, and then click String Value.</li> Type TraceFile, and then press ENTER.</li> Double-click TraceFile, type c:\trace.txt in the Value data box, and then click OK.

Important The TraceFile registry entry cannot be stored on the disk where the shadow copy is created.</li></ol> </li> In the left pane, right-click Tracing, point to New, and then click DWORD Value.</li> Type TraceToDebugger, and then press ENTER.</li> Double-click TraceToDebugger, type 1 in the Value data box, and then click OK.

Note The TraceToDebugger registry entry determines whether trace information is output to the debug output stream. A value of 0 (the default) indicates that no trace information is output to the debug output stream. A value of 1 indicates that the trace information is output to the debug output stream.</li> In the left pane, right-click Tracing, point to New, and then click DWORD Value.</li> <li>Type TraceTimeStamp, and then press ENTER.</li> <li>Double-click TraceTimeStamp, type 1 in the Value data box, and then click OK.

Note The TraceTimeStamp registry entry determines whether the time stamp information is output to the trace file and to the debug output stream. A value of 0 (the default) indicates that no time stamp information is output. A value of 1 indicates that the time stamp information is output.</li> <li>In the left pane, right-click Tracing, point to New, and then click DWORD Value.</li> <li>Type TraceFileLineInfo, and then press ENTER.</li> <li>Double-click TraceFileLineInfo, type 1 in the Value data box, and then click OK.

Note The FileLineInfo registry entry determines whether the module file name information and the line number information are output to the trace file and to the debug output stream. A value of 0 (the default) indicates that no module file name information and no line number information are output. A value of 1 indicates that the module file name information and the line number information are output.</li> <li>In the left pane, right-click Tracing, point to New, and then click DWORD Value.</li> <li>Type TraceForceFlush, and then press ENTER.</li> <li>Double-click TraceForceFlush, type 1 in the Value data box, and then click OK.

Note The TraceForceFlush registry entry determines whether a forced flush occurs after each trace message is written to the trace file. A value of 0 (the default) indicates that no forced flush occurs. A value of 1 indicates that a forced flush occurs. When a forced flush occurs, no trace records are ever lost, but computer performance is greatly reduced.</li> <li>Quit Registry Editor.</li></ol>

For more information about the Volume Shadow Copy service, visit the following Microsoft Web site:

http://technet2.microsoft.com/windowsserver/en/library/B45C7507-B7AD-420E-A981-C273C2012A831033.mspx

For more information about the Volume Shadow Copy Service update package for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

913648 A new Volume Shadow Copy Service update is now available that fixes various Volume Shadow Copy Service problems in Windows Server 2003

For more information about Windows Server 2003 compatibility with former backup software, click the following article number to view the article in the Microsoft Knowledge Base:

327948 Windows Server 2003 compatibility with former backup software

Keywords: kbhowto KB887013

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.