Hi! There is a message: “Exception calling” WriteEntry “with” 3 “argument (s):” Log entry string is too long. A string written to the event log cannot exceed 32766 characters. “”
Show you how to fix this situation? Or how can I redirect log to a text file?

Serge,
Yikes! Sorry to hear about the issue you are having and thanks for all the info you provided. Right now I am buried at work, but I will need to come back and revist your reply…
— Mark

Alex,
sounds like you are hitting a windows limit on eventlog entry size.
One way I think I will approach this is to re-write the eventlog functions to split out messages longer than the limit and create mulitple entries. This may take me some time as I am quite swamped at work right now.
The other thing you ask is redirecting to a log file. This should be fairly simple.
This (basically) specifies where you want your logs to be written and sticks a timestamp in front of it.
i haven’t tested these changes, so let me know if you run into issues..
Just replace the last part of the script with this instead..

################################
$LogDate=Get-Date -Format “yyyyMMddhhmm”
$SuccessLog = “C:\” +$logDate + “-Success.log”
$WarningLog = “C:\” +$logDate + “-Warning.log”
$ErrorLog = “C:\” +$logDate + “-Error.log”

if ($SuccessAudit -ne $Null)
{
#Write-Event $EventSource $SuccessEventID “Information” $SuccessAudit “Application”
Out-File -InputObject $SuccessAudit -FilePath $SuccessLog -Append
}

if ($WarningAudit -ne $Null)
{
#Write-Event $EventSource $WarningEventID “Warning” $WarningAudit “Application”
Out-File -InputObject $WarningAudit -FilePath $WarningLog -Append
}

if ($ErrorAudit -ne $Null)
{
#Write-Event $EventSource $ErrorEventID “Error” $ErrorAudit “Application”
Out-File -InputObject $ErrorAudit -FilePath $ErrorLog -Append
}
########################################

— Mark

Mark,
I was very pleased to find this script and see others have had success in its implementation. I have scheduled this script to run on our hub dfsr servers and I see the check-dfsr events in the eventlog. I have left the backlogerrorlevel at the default value of 10. The problem I am having is it is only reporting 9500 events and indicating all of the replication group connections are in sync with 0 backlog even when there are really backlogs greater than 100 (verified by running the dfsrdiag backlog manually). Do you have any ideas of what could cause the script to report incorrectly?

Any ideas would really be appreciated,
Thank you,
Sharon

Sharon,
Do your replication groups or replicated folder names have spaces in them?
There was a change made that put quotes around the replication groups and folder names. Please see the previous comments to make sure you have this.

I probably need to do some more error checking to make sure no false-positives are generated.

– Mark

For anyone that wants emails sent out I have updated the script to include HTML emails with formatting. (Added by Moderator from previous post)
Moderator please remove all other comments from me.. This should work now:

$SuccessAuditHTML = “HTML”
$SuccessAuditHTML += “BODY”

$WarningAuditHTML = “HTML”
$WarningAuditHTML += “BODY”

$ErrorAuditHTML = “HTML”
$ErrorAuditHTML += “BODY”

foreach ($Group in $RGroups)
{
## Cycle through all Replication groups found
$DFSRGFoldersWMIQuery = “SELECT * FROM DfsrReplicatedFolderConfig WHERE ReplicationGroupGUID=’” + $Group.ReplicationGroupGUID + “‘”
$RGFolders = Get-WmiObject -Namespace “root\MicrosoftDFS” -Query $DFSRGFoldersWMIQuery

## Grab all connections associated with a Replication Group
$DFSRConnectionWMIQuery = “SELECT * FROM DfsrConnectionConfig WHERE ReplicationGroupGUID=’” + $Group.ReplicationGroupGUID + “‘”
$RGConnections = Get-WmiObject -Namespace “root\MicrosoftDFS” -Query $DFSRConnectionWMIQuery
foreach ($Connection in $RGConnections)
{

$ConnectionName = $Connection.PartnerName.Trim()
$IsInBound = $Connection.Inbound
$IsEnabled = $Connection.Enabled

## Do not attempt to look at connections that are Disabled
if ($IsEnabled -eq $True)
{
## If the connection is not ping-able, do not attempt to query it for Backlog info
$Reply = $ping.send(“$ConnectionName”)
if ($reply.Status -eq “Success”)
{

## Cycle through the Replication Folders that are part of the replication group and run DFSRDIAG tool to determine the backlog on the connection partners.
foreach ($Folder in $RGFolders)
{
$RGName = $Group.ReplicationGroupName
$RFName = $Folder.ReplicatedFolderName

## Determine if current connect is an inbound connection or not, set send/receive members accordingly
if ($IsInBound -eq $True)
{
$SendingMember = $ConnectionName
$ReceivingMember = $ComputerName
}
else
{
$SendingMember = $ComputerName
$ReceivingMember = $ConnectionName
}
$Out = $RFName + ” – S:”+$SendingMember + ” R:” + $ReceivingMember
Write-Host $Out
## Execute the dfsrdiag command and get results back in the $Backlog variable
$BLCommand = “dfsrdiag Backlog /RGName:’” + $RGName + “‘ /RFName:’” + $RFName + “‘ /SendingMember:” + $SendingMember + ” /ReceivingMember:” + $ReceivingMember
$Backlog = Invoke-Expression -Command $BLCommand

$BackLogFilecount = 0
foreach ($item in $Backlog)
{
if ($item -ilike “*Backlog File count*”)
{
$BacklogFileCount = [int]$Item.Split(“:”)[1].Trim()
}

}

if ($BacklogFileCount -eq 0)
{
#Update Success Audit
$SuccessAudit += $RFName + ” : 0 files backlogged from “+ $SendingMember + ” to ” + $ReceivingMember +”.`n`r”
$SuccessAuditHTML += $RFName + ” : 0 files backlogged from “+ $SendingMember + ” to ” + $ReceivingMember + “BR”
}
elseif ($BacklogFilecount -lt $BacklogErrorLevel)
{
#Update Warning Audit
$WarningAudit += $RFName + ” ” + $BacklogFileCount + ” backlogged files from ” + $SendingMember + ” to ” + $ReceivingMember + “.`n`r”
$WarningAuditHTML += $RFName + ” ” + $BacklogFileCount + ” backlogged files from ” + $SendingMember + ” to ” + $ReceivingMember + “BR”
}
else
{
#Update Error Audit
$ErrorAudit += $RFName + ” ” + $BacklogFilecount + ” backlogged files from ” + $SendingMember + ” to ” + $ReceivingMember + “.`n`r”
$ErrorAuditHTML += $RFName + ” ” + $BacklogFileCount + ” backlogged files from ” + $SendingMember + ” to ” + $ReceivingMember + “BR”
}
#Write-Host + $Folder.ReplicatedFolderName “- ” $BackLogFilecount -foregroundcolor $FGColor
}
}
else
{
Write-Host $ConnectionName “is not pingable”
$NoPingMessage = “Server “”" + $ConnectionName + “”" could not be reached.`nPlease verify it is on the network and pingable.”
Write-Event $EventSource $NoPingEventID “Warning” $NoPingMessage “Application”
}
}
}
$SuccessAuditHTML += “BR”
$WarningAuditHTML += “BR”
$ErrorAuditHTML += “BR”

}
## Write my events to the local Application log.

$SuccessAuditHTML += “/BODY”
$SuccessAuditHTML += “/HTML”

$WarningAuditHTML += “/BODY”
$WarningAuditHTML += “/HTML”

$ErrorAuditHTML += “/BODY”
$ErrorAuditHTML += “/HTML”

Write-Host $SuccessAuditHTML

if ($SuccessAudit -ne $Null)
{
Write-Event $EventSource $SuccessEventID “Information” $SuccessAudit “Application”
}

if ($WarningAudit -ne $Null)
{
Write-Event $EventSource $WarningEventID “Warning” $WarningAudit “Application”
}

if ($ErrorAudit -ne $Null)
{
Write-Event $EventSource $ErrorEventID “Error” $ErrorAudit “Application”
}

## This is to create an email content
$Mail = New-Object System.Net.Mail.MailMessage($Sender,$Recipient)
$Mail.IsBodyHTML = $True

## Setup SMTP Mail Server info
$MailClient = New-Object System.Net.Mail.SmtpClient
$MailClient.Host = $Mailserver

if ($SuccessAudit -ne $NULL)
{
$MailTxt = “Information ”
$Mail.Subject = $MailTxt + “: DFS-R Report on ” + (Get-Date)
$Mail.Body = $SuccessAuditHTML

# Send the message
$MailClient.Send($Mail)
}

if ($WarningAudit -ne $NULL)
{
$MailTxt = “Warning ”
$Mail.Subject = $MailTxt + “: DFS-R Report on ” + (Get-Date)
$Mail.Body = $WarningAuditHTML

# Send the message
$MailClient.Send($Mail)
}

if ($ErrorAudit -ne $NULL)
{
$MailTxt = “Error ”
$Mail.Subject = $MailTxt + “: DFS-R Report on ” + (Get-Date)
$Mail.Body = $ErrorAuditHTML

# Send the message
$MailClient.Send($Mail)
}

You will need to add the HTML Tags “” to HTML, BODY, and BR within the script.

Sorry for the multiple comments

Steve,
Wow! Thanks for the update. I am sure that will help a bunch of folks out. I appreciate the effort on this.

— Mark

@Steve

What do you mean by this because my emails have no formatting:

You will need to add the HTML Tags “” to HTML, BODY, and BR within the script.

Shane :@Steve
What do you mean by this because my emails have no formatting:
You will need to add the HTML Tags “” to HTML, BODY, and BR within the script.

N/M I hadn’t had my coffee for the morning yet =)

Fantastic script, it was exactly what I needed. Thanks!

Glad it worked out for you! Let me know if you have suggestions on how to improve it.
– Mark

I love the additions of having email notification sent out and that’s scheduled once per day so thank you for that piece!!

I’ve also updated your script to run on my desktop and query the remote hub server so i can easily run it on the fly and without having to be logged in locally on the hub.

Excellent script! It proves to be very useful. Do you think there is a way to monitor the whole mesh?
eg: you have three servers a,b,c currently this script runs on server ‘a’ it will perfectly monitor the backlog from a-b,a-c (inbound and outbound). It would be nice if there was a way that it also monitored b-c (inbound and outbound). The wmi objects only show the connections to the local server”a’ and not to the whole mesh. It’s just an idea.

Many thanks in advance!

@Mark A. Weaver
The problem that i stumbled on was that WMI doesn’t reveal the other partners. While the DFS Management.msc will show this under [DFS Management|Replication| tab connections]. Do you know a quick solution to query this info? I’m happy to share my updated script once it’s finished..

@Mark A. Weaver
Thanks! Actually this was about the same I was thinking. I’ll start digging first in AD trying to find the configuration there..

Dear Mark,

Great script and works perfect, but question is it posible to run this script also on a other suport server instead of the Hub Server.

Johan

@Shane

Can you please post your version of the script i would like to run te script also on a remote server.

Greets Johan

I have written a VBScript that enumerates all the members, connections etc, from the System\DFSR-GlobalSettings\\Topology OU.

Using adsiedit, everything is GUID based, but there are attributes that reveal the hostname of the endpoints. These are actually the receiving servers, and they have msDFSR-Connection objects associated which my script enumerates the actual sending hostname and whether the link is enabled or not. It then simply shells out with the dfsrdiag backlog command and reports accordingly.

The topology I have implemented is multi-tiered with two “root” servers, multiple regional “hubs” and over 50 servers globally deployed in total and over 300Gb replicated. I have included a “self protection” check that if there is a massive backlog into the root servers for some reason the inbound replication link into the root servers is automatically disabled and email alerting is sent to my team. This stops a global replication/reconciliation cycle being triggered.

so i ran this script, the original at the top, and its picking up my SYSVOL replication only and not my replication group i created manually. How do i get this to stop looking at my SYSVOL replication?

I am running win2k8 R2 with DFS-R replication group.

@Mark A. Weaver

nope, i don’t see it, command worked but the list/table is empty.

@Mark A. Weaver

Here is the output and what happens.

PS C:\Windows\system32> ######################################################################
PS C:\Windows\system32> ######################################################################
PS C:\Windows\system32> ## Main
PS C:\Windows\system32> ## Errors written:
PS C:\Windows\system32> ## Log File: Application
PS C:\Windows\system32> ## Source: Check-DFSR Script
PS C:\Windows\system32> ## ID: 9500 – Lists fully replicated replication folders
PS C:\Windows\system32> ## ID: 9501 – Lists replication folders with less than the $BacklogErrorLevel files waiting
PS C:\Windows\system32> ## ID: 9502 – Lists replication folders with more than the $BacklogErrorLevel files waiting
PS C:\Windows\system32> ## ID: 9503 – If a connection is not pingable, this event is written.
PS C:\Windows\system32>
PS C:\Windows\system32> $BacklogErrorLevel = 10
PS C:\Windows\system32>
PS C:\Windows\system32> $ComputerName = $env:ComputerName
PS C:\Windows\system32> ## Query DFSR groups from the local MicrosftDFS WMI namespace.
PS C:\Windows\system32> $DFSRGroupWMIQuery = “SELECT * FROM DfsrReplicationGroupConfig”
PS C:\Windows\system32> $RGroups = Get-WmiObject -Namespace “root\MicrosoftDFS” -Query $DFSRGroupWMIQuery
PS C:\Windows\system32>
PS C:\Windows\system32>
PS C:\Windows\system32> ## Setup my variables
PS C:\Windows\system32> $ping = New-Object System.Net.NetworkInformation.Ping
PS C:\Windows\system32> $SuccessAudit = $Null
PS C:\Windows\system32> $WarningAudit = $Null
PS C:\Windows\system32> $ErrorAudit = $Null
PS C:\Windows\system32> $EventSource = “Check-DFSR Script”
PS C:\Windows\system32> $SuccessEventID = 9500
PS C:\Windows\system32> $WarningEventID = 9501
PS C:\Windows\system32> $ErrorEventID = 9502
PS C:\Windows\system32> $NoPingEventID = 9503
PS C:\Windows\system32>
PS C:\Windows\system32> foreach ($Group in $RGroups)
>> {
>> ## Cycle through all Replication groups found
>> $DFSRGFoldersWMIQuery = “SELECT * FROM DfsrReplicatedFolderConfig WHERE ReplicationGroupGUID=’” + $Group.Replicat
ionGroupGUID + “‘”
>> $RGFolders = Get-WmiObject -Namespace “root\MicrosoftDFS” -Query $DFSRGFoldersWMIQuery
>>
>> ## Grab all connections associated with a Replication Group
>> $DFSRConnectionWMIQuery = “SELECT * FROM DfsrConnectionConfig WHERE ReplicationGroupGUID=’” + $Group.ReplicationG
roupGUID + “‘”
>> $RGConnections = Get-WmiObject -Namespace “root\MicrosoftDFS” -Query $DFSRConnectionWMIQuery
>> foreach ($Connection in $RGConnections)
>> {
>>
>> $ConnectionName = $Connection.PartnerName.Trim()
>> $IsInBound = $Connection.Inbound
>> $IsEnabled = $Connection.Enabled
>>
>> ## Do not attempt to look at connections that are Disabled
>> if ($IsEnabled -eq $True)
>> {
>> ## If the connection is not ping-able, do not attempt to query it for Backlog info
>> $Reply = $ping.send(“$ConnectionName”)
>> if ($reply.Status -eq “Success”)
>> {
>>
>>
>> ## Cycle through the Replication Folders that are part of the replication group and run DFSRDIAG tool
to determine the backlog on the connection partners.
>> foreach ($Folder in $RGFolders)
>> {
>> $RGName = $Group.ReplicationGroupName
>> $RFName = $Folder.ReplicatedFolderName
>>
>> ## Determine if current connect is an inbound connection or not, set send/receive members accordi
ngly
>> if ($IsInBound -eq $True)
>> {
>> $SendingMember = $ConnectionName
>> $ReceivingMember = $ComputerName
>> }
>> else
>> {
>> $SendingMember = $ComputerName
>> $ReceivingMember = $ConnectionName
>> }
>> $Out = $RGName + “:” + $RFName + ” – S:”+$SendingMember + ” R:” + $ReceivingMember
>> Write-Host $Out
>> ## Execute the dfsrdiag command and get results back in the $Backlog variable
>> $BLCommand = “dfsrdiag Backlog /RGName:’” + $RGName + “‘ /RFName:’” + $RFName + “‘ /SendingMe
mber:” + $SendingMember + ” /ReceivingMember:” + $ReceivingMember
>> $Backlog = Invoke-Expression -Command $BLCommand
>>
>> $BackLogFilecount = 0
>> foreach ($item in $Backlog)
>> {
>> if ($item -ilike “*Backlog File count*”)
>> {
>> $BacklogFileCount = [int]$Item.Split(“:”)[1].Trim()
>> }
>>
>> }
>>
>>
>> if ($BacklogFileCount -eq 0)
>> {
>> #Update Success Audit
>> $SuccessAudit += $RGName + “:” + $RFName + ” is in sync with 0 files in the backlog from
“+ $SendingMember + ” to ” + $ReceivingMember +”.`n”
>>
>> }
>> elseif ($BacklogFilecount -lt $BacklogErrorLevel)
>> {
>> #Update Warning Audit
>> $WarningAudit += $RGName + “:” + $RFName + ” has ” + $BacklogFileCount + ” files in the b
acklog from ” + $SendingMember + ” to ” + $ReceivingMember + “.`n”
>> }
>> else
>> {
>> #Update Error Audit
>> $ErrorAudit += $RGName + “:” + $RFName + ” has ” + $BacklogFilecount + ” files in the bac
klog from ” + $SendingMember + ” to ” + $ReceivingMember + “.`n”
>> }
>> #Write-Host + $Folder.ReplicatedFolderName “- ” $BackLogFilecount -foregroundcolor $FGColor
>> }
>> }
>> else
>> {
>> Write-Host $ConnectionName “is not pingable”
>> $NoPingMessage = “Server “”" + $ConnectionName + “”" could not be reached.`nPlease verify it is on th
e network and pingable.”
>> Write-Event $EventSource $NoPingEventID “Warning” $NoPingMessage “Application”
>> }
>> }
>>
>> }
>>
>> }
>> ## Write my events to the local Application log.
>>
Domain System Volume:SYSVOL Share – S:MYDC05 R:MYDC01
The term ‘dfsrdiag’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<<< Backlog /RGName:'Domain System Volume' /RFName:'SYSVOL Share' /SendingMember:MYDC05 /ReceivingMember:M
VDC01
+ CategoryInfo : ObjectNotFound: (dfsrdiag:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Domain System Volume:SYSVOL Share – S:MYDC04 R:MYDC01
The term 'dfsrdiag' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<<< Backlog /RGName:'Domain System Volume' /RFName:'SYSVOL Share' /SendingMember:MYDC04 /ReceivingMember:M
VDC01
+ CategoryInfo : ObjectNotFound: (dfsrdiag:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Domain System Volume:SYSVOL Share – S:MYDC02 R:MYDC01
The term 'dfsrdiag' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<<< Backlog /RGName:'Domain System Volume' /RFName:'SYSVOL Share' /SendingMember:MYDC02 /ReceivingMember:M
VDC01
+ CategoryInfo : ObjectNotFound: (dfsrdiag:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Domain System Volume:SYSVOL Share – S:MYDC03 R:MYDC01
The term 'dfsrdiag' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<<< Backlog /RGName:'Domain System Volume' /RFName:'SYSVOL Share' /SendingMember:MYDC03 /ReceivingMember:M
VDC01
+ CategoryInfo : ObjectNotFound: (dfsrdiag:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Domain System Volume:SYSVOL Share – S:MYDC01 R:MYDC02
The term 'dfsrdiag' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<<< Backlog /RGName:'Domain System Volume' /RFName:'SYSVOL Share' /SendingMember:MYDC01 /ReceivingMember:MY
DC02
+ CategoryInfo : ObjectNotFound: (dfsrdiag:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Domain System Volume:SYSVOL Share – S:MYDC01 R:MYDC03
The term 'dfsrdiag' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<<< Backlog /RGName:'Domain System Volume' /RFName:'SYSVOL Share' /SendingMember:MYDC01 /ReceivingMember:J
VDC02
+ CategoryInfo : ObjectNotFound: (dfsrdiag:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Domain System Volume:SYSVOL Share – S:MYDC01 R:MYDC04
The term 'dfsrdiag' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<<< Backlog /RGName:'Domain System Volume' /RFName:'SYSVOL Share' /SendingMember:MYDC01 /ReceivingMember:E
VDC01
+ CategoryInfo : ObjectNotFound: (dfsrdiag:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Domain System Volume:SYSVOL Share – S:MYDC01 R:MYDC05
The term 'dfsrdiag' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ dfsrdiag <<< if ($SuccessAudit -ne $Null)
>> {
>> Write-Event $EventSource $SuccessEventID “Information” $SuccessAudit “Application”
>> }
>>
PS C:\Windows\system32> if ($WarningAudit -ne $Null)
>> {
>> Write-Event $EventSource $WarningEventID “Warning” $WarningAudit “Application”
>> }
>>
PS C:\Windows\system32> if ($ErrorAudit -ne $Null)
>> {
>> Write-Event $EventSource $ErrorEventID “Error” $ErrorAudit “Application”
>>
>>

that did it Mark, thanks a million! the problem is my lack of full understanding of DFS-R , we have win2k8 R2 domain based DFS and i thought we should run all dfs commands from a DC. however the members were file servers so this makes sense now. its working great now, and thanks for sharing this will help tremendously!

How do most use this script, do they setup in the task scheduler or something different?

There is a problem with this script. It can positively report that the backlog is zero on replication pairs where there is an issue with DFS replication. For instance the DFS service is down on the sender. If you were to run the DFSRDIAG Backlog command from the PowerShell you would get a different error rather than an actual backlog number. This script reports that as a backlog of zero.