HP F200 VSS Provider/Microsoft Windows LTU and Media Kit manual Diagnostics, Application Event Log

Models: F200 VSS Provider/Microsoft Windows LTU and Media Kit F400 VSS Provider/Microsoft Window LTU and Media Kit E200 VSS Provider/Microsoft Windows LTU and Media Kit S800 VSS Provider/Microsoft Windows LTU and Media Kit T800 VSS Provider/Microsoft Windows LTU and Media E-LTU T400 VSS Provider/Microsoft Windows LTU and Media Kit T800 VSS Provider/Microsoft Windows LTU and Media Kit T400 VSS Provider/Microsoft Windows LTU and Media E-LTU S400 VSS Provider/Microsoft Windows LTU and Media Kit

1 23
Download 23 pages 33.35 Kb
Page 20
Image 20

5 Diagnostics

Volume Shadow Copy Service Trace

If the failure of the VSS request has been determined to be outside the scope of VSS Provider for Microsoft Windows, gather the following information for Microsoft support:

Windows Application Event Log

Windows System Event Log

Volume Shadow Copy Service Trace

For VSS Provider for Microsoft Windows debug purposes, turn on VSS logging by setting up the registry data value on the VSS registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Debug\Tracing]

To eliminate the risk of modifying the registry database, VSS Provider for Microsoft Windows provides the vsstrace.reg registry file for assistance with turning on VSS logging.

The file vsstrace.reg is located under the VSS Provider for Microsoft Windows installation directory. Since VSS logging is volume based, the log file cannot be on the volume as part of the shadow copy set.

The default location for the trace file is set to c:\vsstrace.txt. Modify it to fit into your system if necessary.

Use Windows Explorer to locate the vsstrace.reg file. Double-click this file to make it active.

The trace log will be appended. In order to receive meaningful information, clear out the contents before a new run begins.

To turn off the VSS tracing, remove the following registry key from the registry database:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Debug\Tracing]

NOTE: You can use the ProvCfg.exe utility with the Log subcommand to specify the appropriate log level. See “Installation, Upgrade, and Deinstallation” (page 10) “Using the ProvCfg Command to Set Up or Modify a System Connection” (page 15) for complete details.

Contents of the vsstrace.reg File

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Debug\Tracing] "TraceFile"="c:\vsstrace.txt"

"TraceLevel"=dword:ffffffff

"TraceEnterExit"=dword:00000001

"TraceToFile"=dword:00000001

"TraceToDebugger"=dword:00000000

"TraceFileLineInfo"=dword:00000001

"TraceForceFlush"=dword:00000000

Application Event Log

This section describes how to view event logs associated with VSS Provider for Microsoft Windows, and how to interpret the VSS Provider messages that get posted through the Application Event Log in numerical order (Table 3 (page 21)).

20 Diagnostics

Page 20
Image 20
HP F200 VSS Provider/Microsoft Windows LTU and Media Kit manual Diagnostics, Volume Shadow Copy Service Trace