![the server responded with a status of 413 request entity too large moodle scorm package the server responded with a status of 413 request entity too large moodle scorm package](https://i.stack.imgur.com/yfIKF.png)
- #The server responded with a status of 413 request entity too large moodle scorm package drivers#
- #The server responded with a status of 413 request entity too large moodle scorm package update#
- #The server responded with a status of 413 request entity too large moodle scorm package software#
- #The server responded with a status of 413 request entity too large moodle scorm package code#
- #The server responded with a status of 413 request entity too large moodle scorm package windows#
#The server responded with a status of 413 request entity too large moodle scorm package drivers#
Đ9:26:51:896Ē464 ea28 PT WARNING: Sync of Drivers failed (Software succeeded): 0x80240439ĭeclined Manually using the WSUS console. Đ9:26:51:896Ē464 ea28 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 4548) stopped does use network is at background priority Đ9:26:51:894Ē464 ea28 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
![the server responded with a status of 413 request entity too large moodle scorm package the server responded with a status of 413 request entity too large moodle scorm package](https://bobcares.com/wp-content/uploads/413_request_entity_too_large_error.jpg)
Đ9:26:51:894Ē464 ea28 WS WARNING: The response from the HTTP server was not recognized.
#The server responded with a status of 413 request entity too large moodle scorm package code#
Đ9:26:51:894Ē464 ea28 WS WARNING: There was an error communicating with the endpoint at ' Đ9:26:51:894Ē464 ea28 WS WARNING: The server returned HTTP status code '413 (0x19D)' with text 'Request Entity Too Large'. Đ9:26:51:861Ē464 ea28 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started operation # 4548 does use network is at background priority Đ9:26:51:839Ē464 ea28Ěgent SyncUpdates adding 0 visited app categories
![the server responded with a status of 413 request entity too large moodle scorm package the server responded with a status of 413 request entity too large moodle scorm package](https://www.hostinger.com/tutorials/wp-content/uploads/sites/2/2019/01/htaccess-upload-max-filesize.png)
Đ9:26:51:839Ē464 ea28Ěgent Reading cached app categories using lifetime 604800 seconds Đ9:26:51:839Ē464 ea28 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 4547) stopped does use network is at background priority Đ9:26:51:817Ē464 ea28 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started operation # 4547 does use network is at background priority Đ9:26:50:582Ē464 ea28Ěgent SyncUpdates adding 0 visited app categories Đ9:26:50:582Ē464 ea28Ěgent Reading cached app categories using lifetime 604800 seconds Đ9:26:50:573Ē464 ea28 IdleTmr WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 4546) stopped does use network is at background priority Đ9:26:50:559Ē464 ea28 IdleTmr WU operation (CAgentProtocolTalker::GetCookie_WithRecovery) started operation # 4546 does use network is at background priority Đ9:26:50:545Ē464 ea28 PT Server URL = Đ9:26:50:559Ē464 ea28 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 4545) stopped does use network is at background priority Đ9:26:50:544Ē464 ea28ĞP Got WSUS SimpleTargeting URL: " Đ9:26:50:545Ē464 ea28 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started operation # 4545 does use network is at background priority Đ9:26:50:544Ē464 ea28 PT + ServiceId =, Server URL = Đ9:26:50:544Ē464 ea28 PT WARNING: Cached cookie has expired or new PID is available Has anyone ever seen this? Any tips would be greatly appreciated! I can't find any information on WSUS and HTTP 413 errors.
#The server responded with a status of 413 request entity too large moodle scorm package software#
It's only when I use SCCM client and run a software updates scan.
#The server responded with a status of 413 request entity too large moodle scorm package windows#
If I scan against Windows Update, I can see updates are available and I don't see these errors. I believe the clients may be having difficulty scanning against the WSUS server. I started digging because certain clients were not receiving updates. WARNING: There was an error communicating with the endpoint at ' WARNING: The server returned HTTP status code '413 (0x19D)' with text 'Request Entity Too Large'. They look like this: WARNING: Nws Failure: errorCode=0x803d0000
#The server responded with a status of 413 request entity too large moodle scorm package update#
Recently, I've been seeing a lot of 413 errors in the Windows Update log during the scan. I have SCCM fully updated, and it's been handling updates for quite some time without issues.