question

artsnob avatar image
0 Votes"
artsnob asked AllenLiu-MSFT commented

Unsolvable “unexpected packet format” error in WSUS console

I’ve spent almost a week trying to troubleshoot this error, which prevents the WSUS console from displaying the computers. It appeared out of nowhere on a WSUS server that’s been running fine for more than six years and hasn’t been modified in any way recently. I see where this issue has occurred many times in the past to other users, but none of the known solutions make any difference at all. Of course I’ve restarted the server. The IIS server is not set for SSL. I’ve restarted WSUSPOOL in IIS and increased its memory. For that matter, I’ve tried all of the solutions suggested in the error message and all of the ones in these articles:

WSUS Error: Connection Error
FIX: An error occured trying to connect the WSUS server
AN ERROR OCCURRED TRYING TO CONNECT THE WSUS SERVER

I’ve also searched in this forum and the Spiceworks WSUS forum. Nothing. There’s simply not a solution for whatever’s causing this error anywhere in cyberspace. It’s like a “zero day” bug – the first time it’s ever occurred. Does anyone have the WSUS expertise to suggest something else I might try?


windows-server-update-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

artsnob avatar image
0 Votes"
artsnob answered

wsus-breakdown.pdf (439.7 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AJTek-Adam-J-Marshall avatar image
0 Votes"
AJTek-Adam-J-Marshall answered

The 500 error is the cause of the WSUS MMC Console error and it appears that the permissions are the root cause.

https://www.ajtek.ca/wsus/wsus-permissions-wsuscontent-registry-and-iis/

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

artsnob avatar image
0 Votes"
artsnob answered AJTek-Adam-J-Marshall edited

Hmmm … I’m a little confused – how can it be permissions if the problem packets can’t be accessed? I’ll give that permissions paper a try, but I have a premonition that it’s one more solution that this bug will defy.

Do you remember that “Add-ESDMimetype” you told me to enter in the WSUS powershell window in another thread? That’s the only change that has been made to WSUS recently. Could that have something to do with it? Since it didn’t solve the problem it was implemented for, can I undo it and see if that makes any change? What's the proper syntax?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

You can run Reset-ESDMimetype to reset it to OS Defaults or use Remove-ESDMimetype to remove it altogether.

0 Votes 0 ·
artsnob avatar image
0 Votes"
artsnob answered AllenLiu-MSFT commented

I executed the "remove it" command, and it started working again immediately. Finally!

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

That's concerning.... If you wouldn't mind, run Add-ESDMimetype -Verbose

And create a ticket on our support site with the output of that command. Then execute

Remove-ESDMimetype -Verbose

And paste that output into the ticket too.

0 Votes 0 ·
artsnob avatar image artsnob AJTek-Adam-J-Marshall ·

Done. If you haven't seen it yet:
137888-capture.jpg


0 Votes 0 ·
capture.jpg (69.2 KiB)

Glad to hear that Remove-ESDMimetype fixed the issue, so the issue is solved for this thread, you may accept your reply as answer.

0 Votes 0 ·