Closed rrrodzilla closed 6 years ago
Can you paste the stack trace ?
Stack trace below, as mentioned, this code executes just fine when run locally:
Unhandled Exception: System.AggregateException: One or more errors occurred. ---> System.Net.WebException: The remote server returned an error: (408) Request Timeout.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func
2 endFunction, Action1 endAction, Task
1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bing.Messaging.WebSocketFactory.
The .NET ClientWebsocket implementation was not yet supported on Windows Server 2008. Upgrading your OS version should resolve the issue. Support was added in Win Server 2012.
Hi,
Really hope someone has an answer for this. Our code is in a console app, (it's pretty much the code in this sample) that transcribes a single file and receives responses and then writes the responses to a text file. Works great locally on our machines.
However, when we add that console app as a resource to a node on Azure batch and spin up multiple nodes (or even a single one) it makes the initial transcribe request and then it sits and times out with a request 408 timeout error.
The nodes are vm images of Windows Server 2008R2 and I've verified the requisite ports are open as we are able to call other services.
Please tell me there's a setting or something we need to make in order to make this work.
Best Regards,
Roland