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

Self Update Is Not Working 13042 Wsus

Contents

Login here! Shame Microsoft!!!! Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2012) My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin I'm experiencing a similar problem but I'm not sure Join the community of 500,000 technology professionals and ask your questions. check over here

x 37 Anonymous ME920659 has information that may prove helpful for this problem. WSUS 3.0 w/ Spiceworks 7.300108 Oops, forgot to post, here was my settings on 2008R2 64Bit: (pardon the notes, I'll forget why I did what I did later...) Apache# WSUS SelfUpdate Click on bindings in the action pane. The WSUS Administration site was set up on 8350, as per usual and all settings (security and registry) looked correct.

Wsus Self Update

All rights reserved. The Client Web Service is not working. Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended If so, how was the challenge overcome in your experience?

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 x 41 Axeontech Make sure the IP address restriction exceptions for the virtual directory are configured for the server's actual IP. x 43 Christian Jones In my case, it was anonymous permissions in IIS on the selfupdate virtual directory. Remove The Ssl (https) Site Binding For The Default Web Site I fixed this by enabling the iusr_serverx account in AD that was being used for anonymous authentication by this is IIS. (For added security, change the password then you have to

I moved sharepoint services to another server. 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. If it can't find it (Default Website not installed), or can't access it (SSL enabled, Anonymous Authentication denied), you get the "Self-update is not working error" (Event ID 13042). The Cloud and More - Office 365 Using Office 365, and Miscrosoft Server and Office Products Stay updated via RSS June 2011 M T W T F S S « May

An example of English, please! Wsus Selfupdate 403 Forbidden I looked a lot for solution everywhere , including this forum but could not find a solution. So then back to the problem at hand, what else can I look at or check for the cause? 0 Cayenne OP Lawrence (SolarWinds) Feb 28, 2014 at They simply provide the best products, in my opinion, and I like to work with the best.

Selfupdate Virtual Directory

Covered by US Patent. To verify, open command prompt as administrator.  Go to c:\Program Files\Update Services\Tools and run this command: wsusutil checkhealth Then open the event viewer, application logs and see if you now get Wsus Self Update I hold multiple certifications including MCITP:Enterprise Administrator and MCITP:Enterprise Messaging Administrator, MCSE:Messaging and CISSP.I am the author of The EXPTA {blog}, as well as a published author, contributing writer, and technical Wsus Selfupdate Folder Go to the Selfupdate virtual directory Properties, click "Edit" under IP address and domain name restrictions.

You should also check that the selfupdate subdirectory has this unchecked if you are using http and not https. check my blog 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 Symptoms: - Clients have proper self-update client and can see http://10.xx.xx.xx:8530/selfupdate/wuident.cab - Clients are all reporting status to WSUS Server using HTTP port 8530. - Testing has solely been done on All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback this content It's more of something conflicting on that port.

Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Installselfupdateonport80.vbs Download Our WSUS server is currently running on ports 8530(http) and 8531(https). 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

Now go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup.

Promoted by Recorded Future Are you wondering if you actually need threat intelligence? Incorrect ACLs on this folder tree can also produce a similar sort of issue. 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 Installselfupdateonport80.vbs Missing The WSUS Health Monitoring Service checks for the /selfupdate resource on both sites when both sites are in use, but always on the Default Web Site.

The port should be 80, or whatever you use as the default http port. 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). http://johnfladung.net/wsus-self/self-update-is-not-working-on-wsus-server.html I get that message every now and then, even after what I suggested, and clients update fine.

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. A further note that might be worth mentioning is that neither certificate services nor Microsoft Server active-sync are working. 0 LVL 4 Overall: Level 4 Message Active 4 days ago Install1: To st… Microsoft IIS Web Server Rename and move Database and log to new volume in Exchange 2013/2016 Video by: Alan This video discusses moving either the default database or Click the Directory Security tab -> click Edit under Secure Communications and uncheck Require Secured Communications.

Add in IUSR_servername and give it Read & Execute, List Folder Contents and Read permissions. If the server's IP is not listed under the exceptions, self update will fail. 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 In IIS Manager, go to Default website > Selfupdate > Right-click Properties > Directory Security tab > IP addres and Domain restriction EDIT > and check "by default all computers will

See the link to WSUS: SelfUpdate Tree is not working for the full article. http://www.eventid.n...d...ces&phase=1 Yes, WombatBob, I have tried all of the suggested steps to no avail. Join Now Happy Friday!   Now to my dilemma. We explain the basics for creating useful threat intelligence.

x 46 Eric Barb WSUS requires that a "SelfUpdate" virtual directory exist on the website that is hosted on port 80. I've chosen for the time, that I'm ignoring that message since I will probably move WSUS elsewhere later this year. 0 Jalapeno OP Quest John Feb 25, 2014