Hi All,
I encountered a very strange situation for a customer.
We have a live VM running on azure. Which has 4vCPU's.
On this VM we have 6 BC 17.0 instances.
We have split up the services for the functionality so 3 of them are SOAP API services.
Every time the server reboots after .net updates our 3th party receives the SOAP Message is closed.
Normally this is fixed again by rebooting the server but lately the issue starts at random moments aswel.
The difference is now that in the error I see the following line: Microsoft.Dynamics.Nav.Service.SOAP.SoapThrottlerDispatchMessageInspector.AfterReceiveRequest
Environment Name:
Environment Type:
User:
Type: System.ObjectDisposedException
Message: Message is closed.
StackTrace:
at System.ServiceModel.Channels.BufferedMessage.get_Properties()
at Microsoft.Dynamics.Nav.Service.SOAP.SoapThrottlerDispatchMessageInspector.AfterReceiveRequest(Message& request, IClientChannel channel, InstanceContext instanceContext)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.AfterReceiveRequestCore(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
Source: System.ServiceModel
HResult: -2146232798
StackTrace:
at System.ServiceModel.Channels.BufferedMessage.get_Properties()
at Microsoft.Dynamics.Nav.Service.SOAP.SoapThrottlerDispatchMessageInspector.AfterReceiveRequest(Message& request, IClientChannel channel, InstanceContext instanceContext)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.AfterReceiveRequestCore(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
Anyone has an idea what this could be?
0
Answers
I've not found why the error has come back yet.