Problem after installing some windows updates (935839,929123,935840)

[Solhar]

Hello all.

This morning one of my applications stopped working.

The error message I'm getting if this one:

System.Net.Sockets.SocketException was unhandled
Message="The handle is invalid"
Source="System"
ErrorCode=6
NativeErrorCode=6
StackTrace:
at System.Net.Sockets.Socket.DoBeginAccept(LazyAsyncResult
asyncResult)
at System.Net.Sockets.Socket.BeginAccept(AsyncCallback
callback, Object state)
at
System.Net.Sockets.TcpListener.BeginAcceptSocket(AsyncCallback
callback, Object state)
at
System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object
data)
at
System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at
System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary
properties, IServerChannelSinkProvider sinkProvider,
IAuthorizeRemotingConnection authorizeCallback)
at
System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary
properties, IServerChannelSinkProvider sinkProvider)
at
System.Runtime.Remoting.Channels.Tcp.TcpChannel..ctor(IDictionary
properties, IClientChannelSinkProvider clientSinkProvider,
IServerChannelSinkProvider serverSinkProvider)
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.RegisterChannel(Boolean
SecureChannel)
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[]
commandLine)
at Tium.My.MyApplication.Main(String[] Args) in 17d14f5c-
a337-4978-8281-53493378c1071.vb:line 81
at System.AppDomain.nExecuteAssembly(Assembly assembly,
String[] args)
at System.Runtime.Hosting.ManifestRunner.Run(Boolean
checkAptModel)
at System.Runtime.Hosting.ManifestRunner.ExecuteAsAssembly()
at
System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext
activationContext, String[] activationCustomData)
at
System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext
activationContext)
at
Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssemblyDebugInZone()
at System.Threading.ThreadHelper.ThreadStart_Context(Object
state)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

I'm suspecting one or more of these windows updates to cause the
problem:
kb935839
kb929123
kb935840

Has anybody else seen this?

I have initiated a support request with MS and I'll reply to myself
with the solution to this problem.


Cheers

Harry.

 

[Peter Duniho]

[...]
I'm suspecting one or more of these windows updates to cause the
problem:
kb935839
kb929123
kb935840

Has anybody else seen this?

If you suspect the updates, then the first thing to try is uninstalling
the updates. With some updates, you can just uninstall them directly.
With others, you may have to use System Restore to go back to a checkpoint
prior to installation.

Either way, it doesn't make sense to _assume_ it's the updates. You
should have a direct way of testing that, and so that's the first thing
you should do.

Also, unless all of your network-enabled applications have stopped
working, it would surprise me if this was actually related to the
updates. At the very least, if it is related to the updates, there is
something unique about your program that is causing it to fail when no
other application does. So the other thing for you to start looking into
is what non-standard way are you using the networking API that causes your
application to fail when no other application does.

Pete

 

[oskar]

I'm suspecting one or more of these windows updates to cause the
problem:kb935839
kb929123
kb935840

Has anybody else seen this?

I have had similar problems the last few days, since the updates were
released. I'm very interested in reading about any kind of progress
that you make.

I have a server/client remoting application, where the client
successfully calls the server, but when the server tries to call the
client back it fails after about 60 seconds. On some machines that are
updated however, the application still works. So if the updates are
causing any problem, it's probably in combination with something else.
Confusing...

 

[ardp]

On 14 Juni, 14:35, Solhar wrote:

> I'm suspecting one or more of these windows updates to cause the
> problem:kb935839
> kb929123
> kb935840
>
> Has anybody else seen this?

I have to say that I have the same problem with one of my applications apply KB935839 e KB935840 this time I did not apply kb929123.

My application is written with Microsoft Visual C++ and make extensive use of Sockets and Threads.

I still did not´t know exactly what is happing but I know that the applications is having problems to open a socket in listen stat.

I know for sure that one of that patches is the cause of problem since 3 machines start to have problems right after the installations of them, and I really think that KB935839 is the bad guy but I still does not know that for sure, on monday probably I will debug the application to know what is going wrong.

If anyone else have some information about that please let us know about.