Company about
Home > Wsus Self > Self Update Is Not Working Event Id 13042

Self Update Is Not Working Event Id 13042


I read and have experienced first-hand the problems when placing WSUS and SharePoint services on the same machine; could the fact that I have SpiceWorks on the same machine as WSUS I moved sharepoint services to another server. Share this:LinkedInFacebookLike this:Like Loading... 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. check over here

And checked my wsus health status. This got mine working. i still get Error messages, but clients can download and install updates here is screenshots from IIS 7 what to do next? 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)". check these guys out

Wsus Self Update

Another possibility that I've seen from time to time is that the v-dir isn't pointing to the correct location. The source is "Windows Server Update Services" and the id is 13042. The Server Synchronization Web Service is not working.

I was not using https. An example of English, please! Apparently usecustomwebsite does some changes other than the registry which seems to have fixed my problem. Wsus Selfupdate Folder Make sure that there is an entry for http on Port 80 with * as the IP address.

in the event viewer of the Win Server 2008 (64), on which the WSUS version 3.1.6001.65 is installed. Selfupdate Virtual Directory So, if Spiceworks is installed, and listening on port 80, you have a problem. x 51 Markus Mix In my case I found the sollution here: EV100327 (Event Viewer Errors 13042 13002 12002 12042 12052). over here I fixed this error by going to Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager.

While you could change the physical path for the default web site to the directory you want for your new web site, another way is to do the following. Wsus Selfupdate 403 Forbidden Guess what!? I've resolved this by modifying the apache conf so that the spiceworks apache server services the /selfupdate resource (%ProgramFiles%\\Spiceworks\\httpd\\httpd.conf) by adding the following to the very end: # WSUS SelfUpdate Alias Social Media Icons Proudly powered by WordPress

Selfupdate Virtual Directory

Student Information System PA College of Art & Design needed a new information database system for their student records, admissions, and recruiting. x 43 Anonymous Check that you don't have a Group Policy which prevents remote logon to the the "guests" group. Wsus Self Update Now we needed to get them into the SeraCare domain. Wsus Test Selfupdate The WSUS Administration site was set up on 8350, as per usual and all settings (security and registry) looked correct.

If so, how was the challenge overcome in your experience? check my blog So, if Spiceworks is installed, and listening on port 80, you have a problem. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your account. (LogOut/Change) You are 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 Remove The Ssl (https) Site Binding For The Default Web Site

Make sure you allow anonymous users access on the Directory Security tab as well as allow directory browsing. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We These articles are provided as-is and should be used at your own discretion. this content It's really an error without issue if WSUS is installed on port 8530, because nothing requires the secondary installation of /selfupdate on the DWS anymore (legacy pre-WSUS AU clients could only selfupdate

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. Installselfupdateonport80.vbs Download Once we changed the port on the default website and started it, this problem disappeared. Monday, January 30, 2012 5:27 PM Reply | Quote 0 Sign in to vote What must be installed on the Default Web Site WSS, if installed to use port 80.

Thanks! 0 Back to top of the page up there ^ MultiQuote Reply #2 WombatBob Member Group: Regular Members Posts: 8 Joined: 20-Apr-09 Posted 21 Apr 2009, 10:15 Have you

See the link to WSUS: SelfUpdate Tree is not working for the full article. Our WSUS server is currently running on ports 8530(http) and 8531(https). Login. Installselfupdateonport80.vbs Missing For more information, see Help and Support Center at

Comments: EventID.Net EV100621 (Windows Update Services Multiple Errors in Event Viewer) provides a solution for this type of problem (the steps the reconfigure WSUS). x 37 Anonymous ME920659 has information that may prove helpful for this problem. I looked a lot for solution everywhere , including this forum but could not find a solution. have a peek at these guys In combination with other HMS errors, there are additional possibilities to consider. 1 This discussion has been inactive for over a year.

Both the v-dir and the v-root must support anonymous access. CONTINUE READING Join & Write a Comment Already a member? Perhaps you have added a new site that you want to host and have given it Port 80, changing the default web site to another port, like 8080.  This would would Related Comments Pramod Kumar says: July 21, 2011 at 10:26 PM I have getting error: "self update is not working" , tried to find resolution, read your article on web.

Right-click Default Website --> Permissions.