[Forum FAQ] WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server

Question

Symptom:
You might see an error in Software Update Point Status Message when you run software updates synchronization. (Figure 1)
WSUS Configuration Manager failed to subscribe to update categories and classifications to WSUS Server “Server Name”
Figure 1
When you check the WCM.log, WSUSCtrl.log and wsyncmgr.log. There is an error in WCM.log-“Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found
on WSUS”. (Figure 2)
WCM.log:
Figure 2
Cause:
Windows 7 language packs are available for computers that are running Windows 7 Ultimate or Windows 7 Enterprise. The Windows 7 language packs can be installed only from the Optional
Updates section in Windows Update. However, these language packs are not available on the Microsoft Windows Server Update Services (WSUS) server or through the Microsoft Download Center.
For more information, please review the link below:
Windows 7 language packs are available for computers that are running Windows 7 Ultimate or Windows 7 Enterprise
http://support.microsoft.com/kb/2534462/he
Resolution:
Go to Administration -> Overview -> Site Configuration -> Sites -> Right-click CAS -> Configure Site Components -> SUP Products tab, uncheck “Windows 7 Language
Packs”, then sync again. (Figure 3)
Figure 3
After Sync successfully, the “Windows 7 Language Packs” option disappeared. (Figure 4)
Figure 4
Alternative:
About installing Windows 7 language packs, you could use SCCM 2012 Package feature (download manually) or Windows Update.
http://windows.microsoft.com/en-HK/windows/language-packs#lptabs=win7
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Answer 1

I managed to fix my issue by coping the Client, ClientUpgrade, and Scripts from the files from SCCM install discs folder SMSSETUP to c:\program files\Microsoft Configuration Manager folder.  I noticed that some of the files in the scripts
folder was missing and I copied the other folders over because I felt that maybe my local copy of the Client installer where missing some key files as well.  Once I did that and disabled software update push, restarted the wsus computer, and re-enabled
the software update push it was able to publish the client and start installing it that way.
I thing the initial log messages where pointing me in the wrong direction for a few hours because I was thinking it was permissions as well and kept trying to figure that out but in the end I do not believe any of that was the reason I was receiving the
same error as you where.