Error when running Get-DfsrBacklog on Server 2012 R2


i trying take advantage of new powershell cmdlets dfsr in server 2012 r2. running powershell version 4.0 administrator (elevated). running following command on destination server returns error listed below.

get-dfsrbacklog -sourcecomputername sourceserver -destinationcomputername destinationserver

get-dfsrbacklog : not retrieve backlog information. replication group: "*" replicated folder: "*" source
computer: sourceserver destination computer: destinationserver confirm running in elevated windows powershell
session , member of local administrators group on destination computer. destination computer must
accessible on network, , have dfsr service running. cmdlet not support wmi calls the
following or earlier operating systems: windows server 2012. details: ws-management service cannot process the
request.the computed response packet size (5022319) exceeds maximum envelope size allowed (512000).
@ line:1 char:1
+ get-dfsrbacklog -sourcecomputername sourceserver -destinationcomputername destinationserver ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + categoryinfo          : protocolerror: (sourceserver:string) [get-dfsrbacklog], dfsrexception
    + fullyqualifiederrorid : get-dfsrbacklog.cimexception,microsoft.distributedfilesystemreplication.commands.getdfsr
   backlogcommand

the detail of error "the ws-management service cannot process request.the computed response packet size (5022319) exceeds maximum envelope size allowed (512000)." seems key, not sure do. have tried specifying group name folder name thinking may buffer issue, same result no matter how detail specify (same packet sizes , everything).

how increase maximum envelope size of ws-management service, or how otherwise solve error?

i figured out , wanted post in case else came across error. administrative command prompt, ran below command increase max envelope size 20.

winrm set winrm/config @{maxenvelopesizekb="10240"}





Windows Server  >  Windows PowerShell



Comments

  1. This almost worked for me. had to do this:
    winrm set winrm/config @{MaxEnvelopeSizekb="5000000"}

    ReplyDelete

Post a Comment

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

send messages to users