[Info-vax] Another "automatic update"

[Jan-Erik Söderholm]

Den 2019-03-27 kl. 13:05, skrev David Turner:
> On 3/27/2019 12:08 AM, Dave Froble wrote:
>> Got a bit busy today.  Quite interesting, and disgusting.
>>
>> A networking task that has been working very well for months, if not 
>> years, got an error and aborted.  Actually, did it twice.
>>
>> This happened right after an automatic update of WEENDOZE server 2012, 
>> and of course, it's not a consistent error, just intermittent.  Oh, joy!
>>
>> Turns out it's an error from WEENDOZE TCP/IP, where it attempts to 
>> connect to another connection request while the listener is currently 
>> attached to another connection.
>>
>> Ok, nothing in the application program can affect this.  Best I can 
>> determine is it's probably something introduced by the automatic update.
>>
>> So, now, where were all those arguments for just rolling in updates 
>> without some serious testing?  So we have this brave new world of 
>> constant automatic updates.  Be afraid.  Be very afraid.
>>
> Well there's a surprise...  ;0)
> 
>> To be fair, since it's intermittent, testing just might not have caught it.
>>
>> Moved the task over to a WEENDOZE 7 system and it's been working without 
>> any problems.  But, that's putting off the issue, not solving it.
>>
> 

 From the thin information provided here (no Windows update ID or what the
actual error returned was), it can just as well have been some error from
the programmer that came to light when some bugfix or such was done. Maybe
you were just lucky before. Let us know when you have better information
to share, that would be interesting.