Skip to content

Featured Replies

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.

  • Author

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.

  • Author

Found possible solution,

WSUSPool kept stopping, increased the memory for now, will test.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.