DFS-R: Debug Logging Monitor

  • ID:  Microsoft.Windows.FileServer.DFSR.DebugLoggingFailureMonitor
  • Description:  This object monitors the DFS Replication debug log, and creates a Warning alert if it detects that DFS Replication was unable to write to the log.
  • Target:  DFS Replication Service
  • Enabled:  Yes

Operational States

Name State Description
FirstEventRaised Warning  
SecondEventRaised Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
FirstEventRaised (Warning) DFS-R: Failed to Write to the Debug Log Medium Warning Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This object monitors the DFS Replication debug log, and creates a Warning alert if it detects that DFS Replication was unable to write to the log. It does so by looking for the presence of DFS Replication Event 1302.

Causes

An unhealthy state of this monitor indicates that debug logging is disabled because DFS Replication was unable to write to the debug log. This usually occurs when DFS Replication cannot access the path of the debug log folder. This can occur for the following reasons:

  • The volume hosting the debug log folder is offline or on a network share.

  • The volume hosting the debug log folder is out of disk space.

  • The debug log folder has exceeded a quota set on the folder or volume hosting the folder.

  • Incorrect permissions are set on the debug log folder.

Resolutions

Locate the debug log files

To find the path configured for debug logs, type the following command on the affected computer:

wmic /namespace:\\root\microsoftdfs path DfsrMachineConfig get DebugLogFilePath

Verify that the path exists and that it is local to the affected computer. It must not be a UNC address or network path.

If the path does not exist, you can either create the path or change the default debug log location. To change the debug log location, type the following command, where <new_target_path> is the new path for the debug logs:

wmic /namespace:\\root\microsoftdfs path DfsrMachineConfig set DebugLogFilePath="<new_target_path>''

Increase available disk space

If the volume hosting the staging folder or debug log files is low on disk space, increase the available disk space on the volume, increase the size of the volume, or change the path of the staging folder to a volume with more available disk space.

To manually check the amount of available disk space, open a command prompt window and type the following command, where <servername> is the name of the server hosting the affected folder and <domain\user> is your user name:

WMIC /node: "<servername>" /user: <domain\user> volume list status.

After freeing up space, restart the DFS Replication service.

Adjust quotas

If a quota (NTFS disk quota or File Server Resource Manager quota) is limiting the affected folder or volume, consider increasing the quota size.

  • To adjust folders created with File Server Resource Manager, see Quota Management (http://go.microsoft.com/fwlink/?LinkId=187098).

  • To adjust NTFS disk quotas, use the Fsutil quota command, as discussed in FSutil quota (http://go.microsoft.com/fwlink/?LinkId=187104).

Correct the debug log folder permissions

If the DFS Replication service doesn’t have Full Control permissions to the debug log folder, logging will fail. To resolve this issue, grant the local System account Full Controlpermissions to the debug log folder.

Verification

This monitor automatically resets to a healthy state when the issue is resolved.

External References
This monitor does not contain any external references.

See Also for Windows Server File & iSCSI Services Management Pack


Downloads for Windows Server File & iSCSI Services Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED