I am asking this if by any chance you have the solution: I would like using ALOps.ExternalDeployer with a Business Central in a Docker container (created with New-BcContainer from BCContainerHelper).
And I am stuck because apparently the container rejects the connection on port 7040...
This is the script I run against the container after it has been created:
I publish an app with the command below (it works if BC is not installed in Docker). Previous calls to APIs work because I am able to get the companyId.
When I look into the Windows logs of the container, the following error is raised by the NST:
The description for Event ID 701 from source MicrosoftDynamicsNavServer$BC cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Server instance: BC
Category: Extensions
ClientSessionId: 88c273a7-44f3-4100-b8cf-e5204925c932
ClientActivityId: 7b747555-7584-49b0-a93e-e99e50137766
ServerSessionUniqueId: f069c25f-29ac-485b-b56a-6c6d5c5765ed
ServerActivityId: 419e491e-b48f-4c70-879f-54eaee5266d3
EventTime: 10/20/2020 16:20:49
Message Proxy Service Deployment Failure -- Unexpected Exception; Error:An error occurred while sending the request.; InnerException: at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Nav.ExtensionProxySvc.Client.Core.ProxyServiceHttpClient.<>c__DisplayClass8_0.<<InvokeSendRequest>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Nav.ExtensionProxySvc.Client.Util.TaskHelper.<>c__DisplayClass1_0`1.<<InvokeAsyncOperation>b__0>d.MoveNext(); StackTrace:System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:7040
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
ProcessId: 6724
Tag: 00001XR
ThreadId: 117
CounterInformation:
CustomParameters: {
}
GatewayCorrelationId:
Hello,
I am asking this if by any chance you have the solution: I would like using ALOps.ExternalDeployer with a Business Central in a Docker container (created with
New-BcContainer
from BCContainerHelper). And I am stuck because apparently the container rejects the connection on port 7040...This is the script I run against the container after it has been created:
I publish an app with the command below (it works if BC is not installed in Docker). Previous calls to APIs work because I am able to get the companyId.
After that I call this command to get the deployment status:
The output is strange because the status is Unknown instead of Completed or Failed:
When I look into the Windows logs of the container, the following error is raised by the NST: