![]() We almost reached your situation but one of my collegue was smart enough to catch this one at the right time. Event Id 1004 Detection Of Product How To Convince Windows.Event Id 1004 Detection Of Product Free Of That.Event Id 1004 Detection Of Product Install Nor Repair.When MSI could not find the C:\WINDOWS\Installer\9c9a4.msi, it is supposed to stop repairing WSUS and not remove it. C:\WINDOWS\Installer\9c9a4.msi and rename it. "DisplayName"="Microsoft Windows Server Update Services 3.0" "LocalPackage"="C:\\WINDOWS\\Installer\\9c9a4.msi" The WSUS installer file information is saved at: To avoid WSUS being removed by “hiding” the WSUS MSI file. When Windows Installer trying to “repair” WSUS, it calls WSUS MSI file.There is work around posted by Sherry Kissinger. So right now you have a WSUS server which doesn’t work and the only solution is to reinstall the software. Try the installation again using a valid copy of the installation package ‘WUSSetup.msi’. An installation package for the product Microsoft Windows Server Update Services 3.0 SP1 cannot be found. Product: Microsoft Windows Server Update Services 3.0 SP1 - Error 1706. This event triggers the WSUS to do a selfrepair, which it actuallly doesn’t support! The call to the WSUS interface (WSUSApiFeature) fails.ĭetection of product ‘’ failed. Then randomly after backup the WSUS Assembly files (used by ConfigMgr to communicate with WSUS) are checked for in the wrong location. It seems to be related to backup, however the Config Mgr. By investigating the Eventlog you are able to monitor the process as it happens. I am not yet 100% sure why this is happening but it’s related to WSUS trying to repair itself. I have seen several times, that my WSUS server is suddently gone when the SUP role is installed locally on the Config Mgr site server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |