Đ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. #GPODDER ERROR 413 HTTP SOFTWARE#It's only when I use SCCM client and run a software updates scan. 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 #GPODDER ERROR 413 HTTP 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |