That is because Kaspersky don’t use a web installer that downloads only the latest files, nor regularly push out an updated installer that contains the latest virus definitions.
If you were already on port 80, then do this process in reverse.
Process Request Notification(Int Ptr man ged Http Context, Int Ptr native Request Context, Int Ptr module Data, Int32 flags) at System. From a command prompt, type the following: This will reconfigure WSUS back to port 8530.
As an absolute last resort, I turned off the VM and made a new one, this time with Server 2012.
In the end I was left with more than half my hosts still not reporting in (ever) to the server and none of them able to manually check for updates without getting a bid ol' 80072EE2.
I deleted the softwaredistribution folder, forced the client to detect and report, used the Microsoft fixit tool, all that garbage.
The Solarwinds tool told me everything was good to go, I had no DNS issues and no problems contacting IIS on the server from anywhere.
It is a well known fact that Kaspersky has always been one of the best, if not the best antivirus software.
However, one of the gripes that I have against Kaspersky is the first update normally takes a very long time to complete.
Create Exception Throw Exception: actor = Web Service/, ID=9b1e3f5a-f766-4ba9-bf7e-52c7cfbe1f68, Error Code=Internal Server Error, Mess ge=, Client=a39b9446-c45a-4060-851d-9157a2393278 I recently came across this exact issue, with identical errors in the logs as you are seeing.
Process Request Notification(Int Ptr man ged Http Context, Int Ptr native Request Context, Int Ptr module Data, Int32 flags) 2015-12-04 .018 UTC Warning w3wp.18 Soap Utilities.
First things first, make sure that KB2720211 is installed on the WSUS server. If any of your clients updated directly from Microsoft, they will have this update already and will be unable to communicate with your WSUS server (checking for updates from Microsoft on the WSUS server will give you this update if the WSUS role is installed). For some reason, reinstalling the role configured it improperly.