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


Hi,

 

I have Sync form Windows update, and Do not create WSUS reporting events.

But I dont think this relates to windows update. I think it's some component or thing in SCCM that doesn't get loaded correctly.

Share this post


Link to post
Share on other sites

Hello, I've he same problem. I unistalled\installed wsus and sup, but still persist. Any idea about? It's a bug?

I thinks is related to sccm component too... but no way to solve it

Roberto

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
I tried today to set classifications through powershell but I get this.. :/


Set-CMSoftwareUpdatePointComponent -SiteCode XXX -AddUpdateClassification "Definition Updates"


Set-CMSoftwareUpdatePointComponent : No object corresponds to the specified parameters.

At line:1 char:1

+ Set-CMSoftwareUpdatePointComponent -SiteCode XXX -AddUpdateClassification "Defin ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (Microsoft.Confi...omponentCommand:SetSoftwareUpdatePointComponentCommand) [set-CMSoftwareUpdatePointComponent], ItemNotFoun

dException

+ FullyQualifiedErrorId : ItemNotFound,Microsoft.ConfigurationManagement.Cmdlets.HS.Commands.SetSoftwareUpdatePointComponentCommand

Share this post


Link to post
Share on other sites

Did you integrate your SCCM/WSUS server with System Center Updates Publisher?

 

I also saw you are running a 2008 (R2) version of WSUS. Did you verifiy you got both updates for it? (min WSUS 3.0 SP2 + KB2720211 + KB2734608)

 

Link to both updates:

http://support.microsoft.com/kb/2720211

http://support.microsoft.com/kb/2734608

 

You also might want to look in the event viewer of Windows itself, WSUS might be spitting out some errors over there.

Share this post


Link to post
Share on other sites

Yes, I have both updates installed.

 

I think it might be a corrupted db that gives the problem. When I remove the SUP, and then reinstall it, the wizard remembers my choises.

I suspect it has something to do with it. So, if I somehow could totally reset the sccm db regarding SUP settings, it might work.

 

In WCM.log theres this line:

Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Category Id="Product:01030579-66d2-446e-8c65-538df07e0e44"><![CDATA[Windows 8.1 Language Packs]]></Category>~~ <Category Id="Product:0a07aea1-9d09-4c1e-8dc7-7469228d8195"><![CDATA[Windows RT]]></Category>~~ <Category Id="Product:14a011c7-d17b-4b71-a2a4-051807f4f4c6"><![CDATA[Windows 8.1 Language Interface Packs]]></Category>~~ <Category Id="Product:18e5ea77-e3d1-43b6-a0a8-fa3dbcd42e93"><![CDATA[Windows 8.1 Dynamic Update]]></Category>~~   ETC................. 

I don't recall seeing this in another running system I manage, so im thinking perhaps something is wrong in the db and the total output of the xml is written in the log.

Share this post


Link to post
Share on other sites

I did an wsutil /reset and then a checkhealth and the eventlog tells everything is working fine

 

I also tried to change some product in another environement and got the same kind of XML data as described in my last post. So perhaps thats just working as intended.

Share this post


Link to post
Share on other sites

Im not sure what to do now, since I've used up all my ideas.

 

Last link that I found for you:

http://social.technet.microsoft.com/Forums/en-US/29135ae5-5f0c-49d9-b7ad-f4d5e9664a33/sccm-2012-sp1-sup-on-windows-server-2012?forum=configmanagerdeployment

 

Poeple saying this is what helped them:

 

 

Pretty strange behavior but here's what I did to fix it:

1.) Uninstall SUP role

2.) Uninstall WSUS

4.) Delete SUSDB from SQL Server

5.) Restart Server

6.) Install WSUS (Chose to install DB nit WID)

7.) Configured Updates to be stored locally

8.) Ran Post Deployment Configuration from Server manager

9.) Started WSUS Admin Console and ran Wizard (also chose to connect for the catalog sync) up to the Point where you select the products (like Kent suggested). Here I canceled the wizzard without chosing any products

10.) Install SUP role in SCCM and configure the right Settings (WSUS on Server 2012 Defaults to its own admin Website and ports 8530 and 8531) and select the products I needed

11.) Checked wcm.log where everything seemed all right now.

12.) started synchronization in the sccm console

At least for me this is working now.

Cheers

Sebastian Bammer

 

 

Kind Regards,

Kevin

Share this post


Link to post
Share on other sites

Thanks Kevin for all your ideas.

 

I might have for the root cause for the problem.

 

As seen in this picture alle the Update Categories marked with yellow has AllowSubscription = 0

and line number 11 starts with 16777253.

 

post-18769-0-30773400-1403263858_thumb.png

 

And seen in this picture, line 1 is referring to 16777253 and none of the update classifications. So perhaps some ugly thing has happened in the database.

post-18769-0-41651900-1403263857_thumb.png

 

 

Think it's time for Supprt Ticket..

Share this post


Link to post
Share on other sites

I talked with Microsoft, and while the technician tried to recreate through virtual lab, I did the same, and found out if I altered the DB in my virtual lab I could recreate the problem, and also get it back.

So I asked the technician if I could just do the same, and his answer was yes, just try.

 

And now my system is working again, both of the problems I had.

Share this post


Link to post
Share on other sites

I know this is an old post but if you read this and remember can you write up more details on how you fixed this please.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×