computed response packet size

Question

_{Tuesday, July 23, 2019 1:17 PM}

I have a post going in the Windows Server forum but haven't gotten much of a reply yet, was hoping I might receive some assistance here.  The issue is with server manager from RSAT on a Windows 10 1903 machine.

I'm having issues with Server Manager/RSAT.  When I try to connect to domain servers I receive: "Configuration refresh failed with the following error: The WS-Management service cannot process the request.  The computed response packet size (512103) exceeds the maximum envelope size that is allowed (512000).

I found a few other similar issues online that were resolved by increasing the WinRM max envelope size but that doesn't appear to be doing the trick for me.  I get the same maximum envelope size allowed error message at 512000 no matter what I set using "winrm set winrm/config @{MaxEnvelopeSizekb="xxxx"}

All replies (6)

_{Wednesday, July 24, 2019 6:58 AM}

Hi,

Thanks for your posting.

Did you restart the machine after using "winrm set winrm/config @{MaxEnvelopeSizekb="xxxx"}?

Best regards,

Abby

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, July 25, 2019 2:19 PM}

Yes, I did.  No change.

My change appears to get committed, a get-item -path WSMan:\localhost\MaxEnvelopeSizekb returns:

   WSManConfig: Microsoft.WSMan.Management\WSMan::localhost

Type                   Name                           SourceOfValue   Value
                                                          
System.String     MaxEnvelopeSizekb                                8192

However that has 0 effect on the error message, which still claims that the envelope max size is set at 51200.  Doubling the value to 16384, same error message.  So either Server Manager isn't using the WSMan values or it's having trouble reading them, I'm not sure which.

_{Friday, July 26, 2019 8:16 AM}

Hi,

Which specified RSAT tool did you install in Windows 10 1903?

In addition, please have a try with the methods below and see whether the issue still exists.

1. Restart the WinRM service:

net stop winrm

net start winrm

2.Perform a clean boot then restart your machine to detect if there is any third-party software interference.

https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

3.Check if the latest patch was installed.

If the issue persists after the above troubleshooting method, please reinstall RSAT on another computer that joins the same domain.

Best regards,

Abby

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, July 30, 2019 8:50 AM}

Hi,

Just want to confirm the current situation.

Please feel free to let us know if you need further assistance.

Best regards,

Abby

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, August 1, 2019 9:29 AM}

Hi,

Was your issue resolved?

If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

If you resolved it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

If no, please reply and tell us the current situation in order to provide further help.'

Best regards,

Abby 

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, March 10, 2020 5:26 PM}

When I ran:

winrm set winrm/config @{MaxEnvelopeSizekb="2048"}

on the client, it had no effect. However when I ran it on the server in question it immediately resolved the issue.