Repair The Reporting Web Service Is Not Working Tutorial

Home > Web Service > The Reporting Web Service Is Not Working

The Reporting Web Service Is Not Working


Event Type: Error Event Source: Windows Server Update Services Event Category: Web Services Event ID: 12002 Date: 15/05/2007 Time: 11:32:33 AM User: N/A Computer: ECSOAKSMX01 Description: The Reporting Web Service is PLEASE CHECK CAREFULLY YOUR LOCAL SECIRITY SETTINGS AND ADD NETWORK SERVICE WHERE ITS NEED. From the WSUS 3.0 Deployment Guide (p71-72): - You cannot set up the entire WSUS Web site to require SSL. See error 12002, "The Reporting Web Service is not working." Another manual reboot of the server did not fix the issue.

About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Your advice save me! You can also use the Event Viewer to check the Application, Security, and System event logs to see if there are any events that indicate a problem. I restarted the app, kicked off a SUP sync…and sure enough after a couple minutes it stopped again.

The Client Web Service Is Not Working. Wsus 12022

What passwords / accounts did you chage ? Event Type: Error Event Source: Windows Server Update Services Event Category: Web Services Event ID: 12032 Date: 15/05/2007 Time: 11:32:33 AM User: N/A Computer: ECSOAKSMX01 Description: The Server Synchronization Web Service Quote Login/register to remove this advertisement. The request failed with HTTP status 503: Service Unavailable Remove configuration failed on WSUS Server Setting new configuration state to 3 (WSUS_CONFIG_FAILED) I'm still not buying it…I swear it was configured.

Until this week. These articles are provided as-is and should be used at your own discretion. i think admin should help in this regard 0 Back to top of the page up there ^ MultiQuote Reply #10 ishu Member Group: Regular Members Posts: 26 Joined: 02-May-07 Wsus The Reporting Web Service Is Not Working 12002 By default you can find it on your C drive by executing the following command cd "c:\Program Files\Update Services\Tools" Execute one of the following commands If updates are configured for port

Please independently confirm anything you read on this blog before doing whatever you decide to do. Check that the PortNumber is set to 80 (Decimal) or 50 (Hex). This post has been edited by Ryzz: 16 May 2007, 18:09 0 Back to top of the page up there ^ MultiQuote Reply #6 lixiao201t Newbie Group: Validating Posts: 1 This may appear if you installed Exchange Server 2007 automatically and Exchange enabled SSL (which it generally does to support Outlook Web Access).

I cant figure out what im doing wrong either, the weird thing for me is that its been doing it since i installed it, i have never got it running. The Client Web Service Is Not Working 12022 I would have thought the reboot would have taken care of that but maybe something lingered after the OS restart. The anly main differences from these 2 machines is that , they were successfully upgraded.. Also refer this: I hope this helps, Shree 0 LVL 47 Overall: Level 47 Windows Server 2003 26 Microsoft IIS Web Server 8 Anti-Virus Apps 6 Message Active

The Simpleauth Web Service Is Not Working.

There's so much to learn and remember in our jobs that it's impossible to keep up. this page x 20 EventID.Net From a newsgroup post: "Make sure the value for PortNumber under the key HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup is set to the correct port (the one your WSUS site is on)". The Client Web Service Is Not Working. Wsus 12022 Please follow and like us: 1 Comment on WSUS Failure Max Cady // December 16, 2014 at 1:39 PM // Reply Great! Wsus Server Synchronization Web Service Is Not Working Switching it back to unassigned (all ip) solved the problem.

Check that UsingSSL is set to 0 (if you are not using SSL). To dstewartjr: I've gone through the WSUS config checklist, without making any changes. Reply ↓ Leave a Reply Cancel reply Your email address will not be published. However, my WSUS Administration console fails (see attached JPEG named "WSUS-Console-Error.JPG"). The Api Remoting Web Service Is Not Working.

I have Server 2012 running WSUS for a long time without incident. Further update: The following steps appear to have solved the problem: 1. I am suspecting a DNS issue here; did you flush your DNS? 0 Poblano OP samyboughanem Nov 14, 2014 at 8:03 UTC The Error 12002 is a Microsoft First place to start is the WindowsUpdate.log of a client system to determine exactly what is failing. 0 Pimiento OP tomsvehla Nov 19, 2014 at 4:15 UTC Thanks

You can try to change the communication port to 3580. Iis/web Services Extensions Secondly, I use my blog as a notebook. After successfully upgrading a primary site server from Server 2008 R2 to Server 2012 R2, I was working through the last verification checks for functionality when I noticed the SUP was

x 19 Serj All this events12002, 12042, 12032, 12052 etc may appear if you have more then one IP but WSUS web site is asigned to only one of them.

Not using SSL on this setup.  I then rebooted the server again to see what would happen. For more information, see Help and Support Center at 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. Event Id 12022 I have uninstalled and reinstalled incase it was a problem there.

All my other machine I had some sort of issue, so I unistalled WSUS2 and install WSUS 3 clean.. See ASP.NET Ajax CDN Terms of Use – ]]> WSUS Support Forums: WSUS 3.0 - All Web Services I've checked the following basics: permissions are fine. this content Ran IISRESET as suggested and clients started reporting in again.

Yes No Tell us more Flash Newsletter | Contact Us | Privacy Statement | Terms of Use | Trademarks | © 2016 Microsoft © 2016 Microsoft

Notify me of new posts by email. This section explains how to troubleshoot these services in general. See This gets rid of teh errors with respect to services not functioning. 2. WSUS 2.0's default port is 80,but 3.0's is 3580.

I think the problem rest with "port". Then it struck me.  Some consultants had played "security expert" in this AD.  I'd already found tonnes of issues in this AD deployment from not understanding DNS to installing Windows 2003 Next step I did the obvious and tried to connect via the console, only to get the lovely error "Cannot connect to WSUSServerName, the server may be using another port or Thursday, March 19, 2015 9:19 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site.

Copyright © 2016 | WordPress Theme by MH Themes Lab Geek Lab Geek Experiences and tips from a desktop engineer ConfigMgr 2012 WSUS Synchronization Errors ConfigMgr 2012 WSUS Synchronization Errors April Server 2008 R2 Reply ↓ Rick September 19, 2016 at 3:32 pm This results in removing all SSL requirements for the WSUS server's IIS web site.