I tried upgrading my site from WSUS 3 sp1 to sp2 and it failed during the upgrade which then uninstalls your previous version of WSUS. So I reinstalled wsus 3 sp1 and I have also reinstalled SCCM, done a site repair, uninstalled wsus again and uninstalled IIS, reinstalled them and reconfigured SCCM and on almost all 600 clients I am now getting this error in the WUAHandler.log file so I can no longer patch machines:
Its a WSUS Update Source type ({59D545A7-168D-4163-8DB6-F08517042BFC}), adding it.
Cannot insert more than 1 WSUS update source with different unique ids WUAHandler 10/29/2009 11:06:51 AM 2576 (0x0A10)
Failed to Add Update Source for WUAgent of type (2) and id ({59D545A7-168D-4163-8DB6-F08517042BFC}). Error = 0x8004069
I have looked all over the web and have not found a way to get rid of this issue. If I do a Report in SCCM, Troubleshooting it shows me two different WSUS Guids. I searched the registry and one of the Guids is under a SMS Site key and the other is under my fsp identification key. I removed fsp role, restarted IIS and tried again and still clients are not reporting back for patching. I have no errors under Site Status and if I add new clients patching seems to work to them. I can also fix this issue if I delete the ccm repository and repair wmi but I can't go around and do that on 600 machines.
I have also tried to reinstall the client on a machine (did not remove it and reinstall which I will try next) and tried a repair of the client but same result. It almost seems that the clients still have the old WSUS guid and not the new one?
Before I decide to blow away everything and start from scratch does anyone have any ideas?
Thanks,
Steve
Steve Holm
Its a WSUS Update Source type ({59D545A7-168D-4163-8DB6-F08517042BFC}), adding it.
Cannot insert more than 1 WSUS update source with different unique ids WUAHandler 10/29/2009 11:06:51 AM 2576 (0x0A10)
Failed to Add Update Source for WUAgent of type (2) and id ({59D545A7-168D-4163-8DB6-F08517042BFC}). Error = 0x8004069
I have looked all over the web and have not found a way to get rid of this issue. If I do a Report in SCCM, Troubleshooting it shows me two different WSUS Guids. I searched the registry and one of the Guids is under a SMS Site key and the other is under my fsp identification key. I removed fsp role, restarted IIS and tried again and still clients are not reporting back for patching. I have no errors under Site Status and if I add new clients patching seems to work to them. I can also fix this issue if I delete the ccm repository and repair wmi but I can't go around and do that on 600 machines.
I have also tried to reinstall the client on a machine (did not remove it and reinstall which I will try next) and tried a repair of the client but same result. It almost seems that the clients still have the old WSUS guid and not the new one?
Before I decide to blow away everything and start from scratch does anyone have any ideas?
Thanks,
Steve
Steve Holm