Jump to content


stgrdk

WSUS Classification problems

Recommended Posts

Hi Windows-Noob ppl,

 

I have this problem and I don't know how to solve it.

 

When I go in to configure site component: Software Update Point and go to Classification,

the dropdown plus icon is missing, and I can't select All Classification and press Apply, Apply is greyed out (as in no changes made)

 

I have this warning in wsyncmgr.log:

WARNING: Request filter does not contain any known classifications. Sync will do nothing.

 

There are no other errors in either WCM.log, WSUSCtrl.log

 

Anyone seen this before?

post-18769-0-85738100-1402645206_thumb.png

Share this post


Link to post
Share on other sites

This is the wsyncmgr.log I get

 

 

Thread terminated by service request. SMS_WSUS_SYNC_MANAGER 17/06/2014 15:26:08 4448 (0x1160)
SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 3856 (0xF10). SMS_WSUS_SYNC_MANAGER 17/06/2014 15:26:59 1224 (0x04C8)
Log level 2 SMS_WSUS_SYNC_MANAGER 17/06/2014 15:26:59 3856 (0x0F10)
Wakeup by SCF change SMS_WSUS_SYNC_MANAGER 17/06/2014 15:27:13 3856 (0x0F10)
Wakeup by SCF change SMS_WSUS_SYNC_MANAGER 17/06/2014 15:50:39 3856 (0x0F10)
Wakeup by SCF change SMS_WSUS_SYNC_MANAGER 17/06/2014 15:50:49 3856 (0x0F10)
SMS_EXECUTIVE signalled SMS_WSUS_SYNC_MANAGER to stop. SMS_WSUS_SYNC_MANAGER 17/06/2014 16:19:52 1224 (0x04C8)
Thread terminated by service request. SMS_WSUS_SYNC_MANAGER 17/06/2014 16:19:53 3856 (0x0F10)
SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 2140 (0x85C). SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 4088 (0x0FF8)
Log level 2 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
Found local sync request file SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
Starting Sync SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
Performing sync on local request SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
Read SUPs from SCF for SRVSCCM.domain.local SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
Found active SUP SRVSCCM.domain.local from SCF File. SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SRVSCCM.domain.local SITE=SCM PID=1768 TID=2140 GMTDATE=mar giu 17 14:31:20.228 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:31:20 2140 (0x085C)
Synchronizing WSUS server SRVSCCM.domain.local SMS_WSUS_SYNC_MANAGER 17/06/2014 16:32:24 2140 (0x085C)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SRVSCCM.domain.local SITE=SCM PID=1768 TID=2140 GMTDATE=mar giu 17 14:32:24.341 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:32:24 2140 (0x085C)
Synchronizing WSUS server SRVSCCM.domain.local ... SMS_WSUS_SYNC_MANAGER 17/06/2014 16:32:24 1776 (0x06F0)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 17/06/2014 16:32:24 1776 (0x06F0)
Done synchronizing WSUS Server SRVSCCM.domain.local SMS_WSUS_SYNC_MANAGER 17/06/2014 16:32:32 1776 (0x06F0)
Sleeping 2 more minutes for WSUS server sync results to become available SMS_WSUS_SYNC_MANAGER 17/06/2014 16:32:32 1776 (0x06F0)
Set content version of update source {82A2A181-DDB0-45C1-A543-BCEC20FB9E23} for site SCM to 0 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 2140 (0x085C)
Synchronizing SMS database with WSUS server SRVSCCM.domain.local SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 2140 (0x085C)
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SRVSCCM.domain.local SITE=SCM PID=1768 TID=2140 GMTDATE=mar giu 17 14:34:33.486 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 2140 (0x085C)
Synchronizing SMS database with WSUS server SRVSCCM.domain.local ... SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 1436 (0x059C)
sync: Starting SMS database synchronization SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 1436 (0x059C)
requested localization languages: en SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 1436 (0x059C)
Syncing updates arrived after 06/17/2014 15:13:32 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 1436 (0x059C)
Requested categories: SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 1436 (0x059C)
sync: SMS synchronizing categories SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 1436 (0x059C)
sync: SMS synchronizing categories, processed 0 out of 261 items (0%) SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:33 1436 (0x059C)
sync: SMS synchronizing categories, processed 261 out of 261 items (100%) SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 1436 (0x059C)
sync: SMS synchronizing categories, processed 261 out of 261 items (100%) SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 1436 (0x059C)
WARNING: Request filter does not contain any known classifications. Sync will do nothing. SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 1436 (0x059C)
WARNING: Request filter does not contain any known categories. Sync will do nothing. SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 1436 (0x059C)
Done synchronizing SMS with WSUS Server SRVSCCM.domain.local SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 1436 (0x059C)
Set content version of update source {82A2A181-DDB0-45C1-A543-BCEC20FB9E23} for site SCM to 0 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 2140 (0x085C)
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SRVSCCM.domain.local SITE=SCM PID=1768 TID=2140 GMTDATE=mar giu 17 14:34:35.518 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 2140 (0x085C)
Sync succeeded. Setting sync alert to canceled state on site SCM SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 2140 (0x085C)
No changes made to the SMS database, content version remains 0 SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 2140 (0x085C)
Sync time: 0d00h03m15s SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 2140 (0x085C)

Share this post


Link to post
Share on other sites

 

I already did, but it doesn't work for me. I checked in all classification, but still I get WARNING: Request filter does not contain any known classifications. Sync will do nothing. SMS_WSUS_SYNC_MANAGER 17/06/2014 16:34:35 1436 (0x059C)

 

Sccm ovverride wsus settings, so it can't works.

 

Is it works for you?

Share this post


Link to post
Share on other sites

No unfortunately you are right. It didn't work for me. I just thought it did, or well, it did first time I changed the WSUS options.

I saw this in the log: sync: WSUS synchronizing updates, processed 14257 out of 84442 items (16%), ETA in 02:28:40

 

But now I get the same WARNING: Request filter does not contain any known classifications. Sync will do nothing. SMS_WSUS_SYNC_MANAGER

Share this post


Link to post
Share on other sites

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...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...



×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.