Company about
Home > Wsus Self > Self-update Is Not Working Event 13042

Self-update Is Not Working Event 13042

Contents

Incorrect ACLs on this folder tree can also produce a similar sort of issue. http://www.eventid.n...d...ces&phase=1 Yes, WombatBob, I have tried all of the suggested steps to no avail. Log Name: Application Source: Windows Server Update Services Date: 10/3/2013 4:53:26 AM Event ID: 12012 Task Category: 9 Level: Error Description: The API Remoting Web Service is not working. If the entry points to another port or isn't there, you probably have to make some other adjustments in IIS.  Here is what I think you may find. check over here

I was forced to unistall everything and start from scratch. All of these posts are more or less reflections of things I have worked on or have experienced. x 53 Craig Tolley I found that the permissions on the Default Website in IIS had been changed. i still get Error messages, but clients can download and install updates here is screenshots from IIS 7 what to do next? https://support.microsoft.com/en-us/kb/2000598

Wsus Self Update

Both the v-dir and the v-root must support anonymous access. iSCSI for SBS – PartII Another Tip for SBS 2011 Hyper-v -- Migration and Answer FileConsiderations Create a free website or blog at WordPress.com. %d bloggers like this: WSUS Support Forums: Actually Windows Sharepoint Services 3.0 and WSUS 3.0 *can* coexist, and hundreds of implementations of that scenario exist today.The necessary requirement is that you properly configure Windows Sharepoint Services to NOT Thanks!

Reply ↓ Horstworst January 26, 2016 at 7:17 am Thanks, this fixed the errors for me! 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 Any one have any ideas? Wsus Test Selfupdate If you want any more info about wsus for provide better assistance, Please ask.

Guess what!? Selfupdate Virtual Directory The Server Synchronization Web Service is not working. You should also check that the selfupdate subdirectory has this unchecked if you are using http and not https. http://www.expta.com/2008/06/fix-for-self-update-is-not-working-in.html The Client Web Service is not working.

Click the Directory Security tab -> click Edit under Secure Communications and uncheck Require Secured Communications. Remove The Ssl (https) Site Binding For The Default Web Site If you got the file not found or similar error, then here is what you should do. When those resources are unavailable (because a Sharepoint - 80 v-root exists), the noted errors are recorded in the Application Event Log.Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA Principal/CTO, Onsite Technology Solutions, the clients can get update and can connect to server...

Selfupdate Virtual Directory

An example of English, please! https://community.spiceworks.com/topic/143171-wsus-3-0-and-existing-web-sites-self-update-not-working They simply provide the best products, in my opinion, and I like to work with the best. Wsus Self Update The DSS Authentication Web Service is not working. Self Update Is Not Working Windows 2008 R2 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).

See example of private comment Links: WSUS: SelfUpdate Tree is not working Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... check my blog Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Go to the Selfupdate virtual directory Properties, click "Edit" under IP address and domain name restrictions. Wsus Selfupdate Folder

After 10 minutes, the error was corrected automatically and the event log said all websites were working now. 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 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. this content Shame Microsoft!!!!

x 45 Peter Van Gils I saw these errors on a DC that had just been upgraded to Win2003 SP2. Wsus Selfupdate 403 Forbidden 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 Notify me of new posts via email.

These articles are provided as-is and should be used at your own discretion.

Email check failed, please try again Sorry, your blog cannot share posts by email. I have to say though that the above is an easy test and eliminates some things but I really doubt it will solve your problem but worth a go none the Posted by Jeff Guillet at 9:13 AM Labels: troubleshooting, WSUS Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Countdown to MVP Global Summit (Redmond, WA) 2016-11-07 Installselfupdateonport80.vbs Download 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 38 Maximus5684 I was receiving Event IDs 13042, 12002, 12012, 12032, 12022, 12042, and 12052. There is special folder that needs to copied from the existing WSUS site into the default site. If WSS is installed on an alternate v-root and configured to use port 80, then the Default Web Site is not running. have a peek at these guys I was playing around with wsusutil.exe and found a command option called "usecustomwebsite".

x 43 Anonymous Check that you don't have a Group Policy which prevents remote logon to the the "guests" group. getting same Error: self update is not working Event ID -13040 Error: Server is failing to download some updates Event ID -10032 My wsus 3.0 sp1 are working on custom web By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Right-click Default Website --> Permissions.

I don't think it has anything to do with other programs installed or using the same port but I haven't tracked the cause down yet. 0 Mace OP