12002 The Reporting Web Service is not working.
-
Friday, November 16, 2012 4:47 PM
Hi :)
I have WSUS on Windows Server 2012 std. with Internal Database. Today I've installed 7 updates from patch tuesday and after restart I've got
error 12002 The Reporting Web Service is not working
I can see now that updatet clients can not report their status anymore :(
What's up ? Any suggestion ?
Best regards
Nenad
All Replies
-
Monday, November 19, 2012 1:57 AMModerator
Hi,
I would start by verifying that the /ReportingWebService resource is properly configured in IIS.
Correct configurations can be found in the WSUS Technical Reference Guide: IIS Settings for WSUS 3.0 SP2 Web Services.
Also,Under ReportingWebService
Made sure all were set to disabled except for Anonymous Authentication
Anonymous Authentication Enabled
ASP .NET Impersonation Disabled
Basic Authentication Disabled
Forms Authentication Disabled
Windows Authentication Disabled
Regards,
Clarence
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Marked As Answer by Clarence ZhangModerator Wednesday, November 21, 2012 2:29 AM
-
Monday, November 19, 2012 5:03 AM
Hi :)
Config is ok and virtual reporting web service have only enabled anonymous auth.
I've added right for Network Service to log on locally and reboot.After some time clients started to reporting their status again.
- Marked As Answer by Clarence ZhangModerator Wednesday, November 21, 2012 2:29 AM
-
Monday, November 19, 2012 6:39 PMI had the same issue after I rebooted servers for patch Tuesday updates this weekend. After looking at it for a little bit, I stopped and started the server in IIS. After that PC's started checking in. I would have thought the reboot would have taken care of that but maybe something lingered after the OS restart.

