Wsus 3.0 sp2 update failed

Administration Stack Trace: at Microsoft. CreateUpdateServer Object[] args at Microsoft. ConnectToServer at Microsoft. Click to expand Hi there, for me the solution of it was reinstall the WSUS, not it working but I have another problem, now I can't deploy anything, it is "in progress" for ever. I will open another for talk about it. Thanks all, Alan. Latest posts A. Configuration Manager.

NEW Wsyncmgr. Please help! Top Bottom. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. By continuing to use this site, you are consenting to our use of cookies.

Accept Learn more…. So please check if any files in that folder. Check if you have Cisco Monitor Service csmon. Please check if you can find errors like "failed to create Group" in the event viewer. Try the following: a. Repair or reinstall. NET Framework. Reboot the server and try again.

This is an entirely irrelevant discussion. Not possible at all. It may be fairly large on my successful installation it is over 2MB. Specifically we're interested in the entries related to the failed installation. I have been working on installing WSUS 3. If anybody can reproduce the behavior on a virgin installation of Windows Server from media or Microsoft-published ISO, I'm certainly interested in seeing those installation logfiles.

Can do. This thread matched perfectly to the issue I am having. Assuming it is not Error 0x The system cannot find the file specified. But this will not block setup Error 0x The operation completed successfully. Net install since not running on win2k Product Version: 3.

Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: MSI c []: Decrementing counter to disable shutdown. I really don't know if I got enough of the end of this file but I would be happy to tranfer the whole thing 2. Ok - the answer for me was pretty simple. It did not and therefore when the WSUS installer tried to create the SQL log file using the path given, it could not because the path did not exist. Hence, a failed install Spent more a weeks time in identifying the root cause.

I also had a. NET Framework 3. Upon opening Programs and Features I saw. NET Framework 4. NET version and tried again. It worked! Office Office Exchange Server.

Not an IT pro? Green Tech. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Show only Search instead for. Did you mean:. Sign In. End of synchronization for WSUS 3. Paul Reed. Published May 20 AM Click on your WSUS server name. In the center, you will see a section called Overview.

Within that area, you will see Connection. See Server Version. Version history.