However, I did not have the ExecuteSQL.exe utility anywhere on my WSUS server. %programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername%\MICROSOFT#SSEE -d “SUSDB” -Q “update tbConfigurationC set BitsDownloadPriorityForeground=1” The KB article details the command to run, and for my scenario (WSUS 3.0 with a Windows Internal Database that was created by a default WSUS installation) the solution described was to run the following command: Specifically, configure BITS to work in foreground mode. In my environment we were not using a Sonicwall firewall device, so Method 1 applied to my scenario. And indeed I quickly found this following KB article describing the issue I was experiencing With such a specific error description in the Event Id 364 I thought finding a solution would be straight forward. The application log showed the following Event ID 364 errorĪnd also the following Event ID 10032 error The WSUS console show the following error “The files for this update failed to download” During a recent deployment of WSUS on Windows 2012 R2, using WID database, I ran into a problem whereby after I approved updates, they would fail to download.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |