If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? I added Everyone rights to the "\program files\update services\selfupdate" folder as well. 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. Reply ↓ Horstworst January 26, 2016 at 7:17 am Thanks, this fixed the errors for me! check over here
x 45 Peter Van Gils I saw these errors on a DC that had just been upgraded to Win2003 SP2. Enter the product name, event source, and event ID. Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? 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 https://support.microsoft.com/en-us/kb/2000598
x 49 Alexey Alexandrov This error occurred when I upgraded WSUS from WSUS 2 to WSUS 3. All of these posts are more or less reflections of things I have worked on or have experienced. The IIS was only bound to the internal IP and localhost address (127.0.0.1) to allow internal access and avoid access from WAN. In the example in this thread, the fundamental problem is that Sharepoint was installed on port 80 in an alternate v-root, effectively rendering the Default Web Site dead -- the real
An example of English, please! I have done research and have not found anything to resolve this. I was playing around with wsusutil.exe and found a command option called "usecustomwebsite". Wsus Test Selfupdate See example of private comment Links: WSUS: SelfUpdate Tree is not working Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...
The co-existence requirements of Windows Sharepoint Services and Windows Server Update Services have been discussed incessantly over the past five years and a simple web search on "WSUS" and "Sharepoint" should The fundamental issue here is that you appear to have installed Windows Sharepoint Services on PORT 80, which is blocking the ability of the WSUS Health Monitoring service to access the You can use the links in the Support area to determine whether any additional information might be available elsewhere. http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=.NET+Framework&ProdVer=2.0.50727&EvtID=13042&EvtSrc=Windows+Server+Update+Services If WSS is installed on an alternate v-root and configured to use port 80, then the Default Web Site is not running.
Secure Remote Employee System We have a remote employee who has been using their personal system to access our network via VPN, and this needed to be upgraded for security reasons. Wsus Selfupdate Folder So, if Spiceworks is installed, and listening on port 80, you have a problem. Share Point just happens to be a common cause. 0 Cayenne OP Lawrence (SolarWinds) Feb 26, 2014 at 5:37 UTC The EventID 13042 is caused when the /selfupdate x 36 EventID.Net From a newsgroup post: "Make sure the value for PortNumber under the "HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup" key is set to the correct port (the one your WSUS site is on)".
The third possibility that I've seen, albeit very rarely these days, is that the /selfupdate v-dir is properly mapped, but the %ProgramFiles%\Update Services\selfupdate folder contents are missing or corrupted. Since WSUS installs components to the Default Web Site (always), that v-root must always be running. Selfupdate Virtual Directory x 37 Vitaliy The following fixed the problem in my case. Self Update Is Not Working Windows 2008 R2 Creating your account only takes a few minutes.
x 41 Axeontech Make sure the IP address restriction exceptions for the virtual directory are configured for the server's actual IP. check my blog The API Remoting Web Service is not working. Our WSUS server is currently running on ports 8530(http) and 8531(https). To force a check to see if it fixes your problem, run "wsusutil.exe checkhealth" from "C:\Program Files\Update Services\Tools". Remove The Ssl (https) Site Binding For The Default Web Site
You should also check that the selfupdate subdirectory has this unchecked if you are using http and not https. IT WORKS! Just an fyi for those who are still having the issue. this content x 37 Anonymous ME920659 has information that may prove helpful for this problem.
The solution wasto give WRITE access to Network Service on the folder %systemroot%\Temp. Installselfupdateonport80.vbs Missing If not, create it with the Local Path pointing to C:\Program Files\Update Services\SelfupdateClick the Directory Security tab and ensure that Anonymous Access is allowedRestart IISVerify that the problem is fixed by The fundamental issue here is that you appear to have installed Windows Sharepoint Services on PORT 80, which is blocking the ability of the WSUS Health Monitoring service to access the
Log Name: Application Source: Windows Server Update Services Date: 10/3/2013 4:53:26 AM Event ID: 12002 Task Category: 9 Level: Error Description: The Reporting Web Service is not working. 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 The DSS Authentication Web Service is not working. Wsus Selfupdate 403 Forbidden Never have been.
WSUS seems not to work when the IIS web is not bound to "all addresses". Even if you have your WSUS site running on port 8530 for example, you need to create a virtual directory within the site on port 80 called "Selfupdate" and map it Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking have a peek at these guys Please note that I am not speaking on behalf-of Microsoft or any other 3rd party vendors mentioned in any of my blog posts.
Reply ↓ Leave a Reply Cancel reply Your email address will not be published. Bottom line, the 13042 is the HMS saying "I cannot find the /selfupdate stuff." It might also be useful to verify in the Application Event Log that you are getting only