Hello everyone, I've just installed the Windows Azure Tools 1.3. Now I'm not able to run a project that worked absolutely fine with the previous SDK. Immediately after starting my WebRole, the applications login form appears and dfloadbalancer.exe crashes.
Here's the stacktrace:
bei System.Net.Sockets.Socket.Shutdown(SocketShutdown how)
bei Microsoft.ServiceHosting.Tools.DevelopmentFabric.LoadBalancer.PacketForwarder.ProcessReceive(IAsyncResult result)
bei System.Net.LazyAsyncResult.Complete(IntPtr userToken)
bei System.Threading.ExecutionContext.runTryCode(Object userData)
bei System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Net.ContextAwareResult.Complete(IntPtr userToken)
bei System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
bei System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
bei System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
Any idea why this happens and how to get around this problem?
I had a very similar issue (with Azure SDK 1.4 installed) to this and the cause turned out to be a malformed connection string. Also, I saw many more of these errors when we were experiencing network connectivity issues and were deveoping against an Azure
database in the cloud. It may be worth reviewing any connection strings, and network connectivity of the app to ensure that all of that is ok - especially as the namespace System.Net.Sockets.Socket is mentioned.