Powered by vBulletin Version 3.6.7Copyright ©2000 - 2016, Jelsoft Enterprises Ltd. This issue has been fixed in WSUS 2.0 Service Pack 1 and in WSUS 3.0. Sponsored Links #2 (permalink) 09-24-2008 PA Bear [MS MVP] Posts: n/a Re: Windows update Services (WSUS) error 10022 Forwarded to WSUS newsgroup (microsoft.public.windows.server.update_services) via crosspost as a convenience You’ll be auto redirected in 1 second. Source
This can be beneficial to other community members reading the thread. Troubleshooting synchronization Check the error in the synchronization's Details pane If a synchronization has failed, in the WSUS administration console, go to the Synchronizations node, and in the middle pane select One major cause of synchronization failure is an expired password on the proxy server. Manage Your Profile | Site Feedback Site Feedback x Tell us about your experience... this contact form
So, I didn't want to duplicate this thread. The content you requested has been removed. A downstream server is reconfigured to get updates from a different upstream server with different products and classifications selected. Such is the impact of somebody improperly changing the system date of a WSUS server and then letting it synchronize.
The name that you enter in the WSUS console on the downstream WSUS server must match the name of the upstream WSUS server. Check the firewall settings If your network has a firewall between the WSUS server and the Internet, make sure that all the necessary ports are open and the necessary domains are When I go into the event viewer I still see an event id 10022 and 13002. Wsusutil Reset It might help.
date_services >> >> In your newsreader: >> news://msnews.microsoft.com/microsof...pdate_services >> -- >> ~PAB >> >> Fabian wrote: >>> the WSUS starts to synchronize properly, but at 60% an error appears. >>> >>> Kb2734608 Thank you for your help. Obviously the dates were wrong and a manual attempt at running a synchronization was successful. Verify that users and the network service have Read permissions to the local update storage directory If you store update files on your WSUS server, you need to ensure that the
[email protected] "PA Bear [MS MVP]" wrote: > To avoid confusion, please begin a new thread in > microsoft.public.windows.server.update_services newsgroup about your > problem, Brad. > > [email protected] wrote: > > Hi, To troubleshoot this issue, make a note of the updates for which download failed on the downstream server. Creating your account only takes a few minutes. Connect with top rated Experts 14 Experts available now in Live! Wsusutil
In my case it was "Log On As: Network Service", I changed it to "Local System", restarted the Update Services, the II Service and it fixed the problem. All rights reserved. Type the following, and then press ENTER: ping WSUSServerName where WSUSServerName is the name of the upstream WSUS server with which you are trying to synchronize. have a peek here regards, ClarencePlease 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.
See KB 910847, "Time-out error when approving multiple updates on Microsoft WSUS Server" (http://go.microsoft.com/fwlink/?LinkId=86496) for more information. It's strange that this problem occured a the same > > time. > > Bacause, I have the problem september 22th, 2008. Right-click Background Intelligent Transfer Service, click Properties, and make sure that Startup Type is Manual.
We appreciate your feedback. If the failed updates are not needed, cancel and then decline the updates that are not on the upstream server If the missing updates are actually available on the upstream server, If synchronizations are failing, you can use the information below to troubleshoot the problem. But, may be I don't understood your request.
Enter the product name, event source, and event ID. Login here! date_services >>>> >>>> In your newsreader: >>>> news://msnews.microsoft.com/microsof...pdate_services >>>> -- >>>> ~PAB >>>> >>>> Fabian wrote: >>>>> the WSUS starts to synchronize properly, but at 60% an error appears. >>>>> >>>>> Check This Out Or comes > from an new update which can't be synchronize because to large ? > Because I don't understand how this problem can be come from my server, > because