Joe13 Posted October 24, 2017 Report post Posted October 24, 2017 Good day everyone, I'm experiencing a weird one with WSUS. I'm using SCCM 1706, WSUS and SQL 2016 everything on one server. Everything works until I go to a client PC to find the following in WUAHandler log file OnSearchComplete - Failed to end search job. Error = 0x80244022. WUAHandler 2017/10/24 8:06:25 AM 3284 (0x0CD4) Scan failed with error = 0x80244022. WUAHandler 2017/10/24 8:06:25 AM 3284 (0x0CD4) I go back to my SCCM server only to find that WSUS cannot connect to the database. Restart the server and everything works fine. When WSUS fails the updates stop pushing - is this how it should work? I mean the package is already in SCCM and deployed to my collections? I can post more log files. Thank you. Quote Share this post Link to post Share on other sites More sharing options...
Joe13 Posted October 24, 2017 Report post Posted October 24, 2017 Another note, WSUS is using SQL database. Should the updates fail if WSUS isn't available? The updates were downloaded and deployed to the collections already... Really need some assistance. Quote Share this post Link to post Share on other sites More sharing options...
Joe13 Posted October 24, 2017 Report post Posted October 24, 2017 Found possible solution, WSUSPool kept stopping, increased the memory for now, will test. Quote Share this post Link to post Share on other sites More sharing options...