Hi,
My DIS is not connecting to the Dataminer Agent.
When I use the cloud path in DIS for upload, it works, but the conventional path over the IP address is not working.
I am running Windows 11 version 24H2 with the latest DIS version 3.1.6.
I downgraded the version back to 3.1.2, and it works fine now. This might be an issue for other users as well once they update their system.
------------------------------------
Error message when trying to connect via IP address:
------------------------------------
Error message when trying to publish:
System.ServiceModel.FaultException:
Message="System.ServiceModel.FaultException: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> 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:80
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)
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException[TResult](Task`1 task)
at SLDisDMAComm.SLDisDmaCommService.ConnectToWebApi() in D:\a\DIS\DIS\ProtocolEditor\SLDisDMAComm\SLDisDmaCommService.cs:line 1203
at SLDisDMAComm.SLDisDmaCommService.ConnectToWebApi() in D:\a\DIS\DIS\ProtocolEditor\SLDisDMAComm\SLDisDmaCommService.cs:line 1224
at SLDisDMAComm.SLDisDmaCommService.Connect(String hostname, String username, String password, String accessToken) in D:\a\DIS\DIS\ProtocolEditor\SLDisDMAComm\SLDisDmaCommService.cs:line 219"
------------------------------------
Four days ago, this question was asked. It might be related:
how-to-install-older-version-of-dis-3-1-4
BR,
Hi,
The new version of DIS has some new features that make use of some web api endpoints besides the normal connection.
From the stacktrace, it seems that DIS is trying to make an api call to http://127.0.0.1 (localhost), which makes me believe that there is no http (port 80) binding configured in IIS, resulting in the refusal of the connection.
DIS determines the protocol (http or https) from information it receives from DataMiner. If it is expected that http traffic is blocked, it could be that DataMiner is not aware it should be using https, resulting in DIS attempting to use http. Can you verify if you have the https-tag configured in the maintenance.xml file?
Kind regards,
DIS is now correctly trying to connect to the webapi over https, however, it seems like the certificate that is configured in IIS is not trusted. This can have multiple root causes (self-signed, expired, name mismatch, …), so would it be possible to inspect the certificate configured in IIS?
It is probably because we have a self-signed certificate from DataMiner.
That's correct. I would recommend to install a proper certificate issues by a Domain controller or purchased from a Certificate Authority. If that is not possible you can also install the self-signed certificate in the trusted root certificate store.
Thank you for your help. Installing the certificate from the server's IIS on my PC worked.
However, connecting to my customer's agent still doesn't work because the port is not open. I will be running the older DIS system until this is resolved by the customer. It might be a good idea to keep older versions of the DIS system available whenever significant changes like this are made.
BR,
Hi,
I added the tag to the file, and now the message is showing this:
—————————————
System.ServiceModel.FaultException:
Message="System.ServiceModel.FaultException: System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. —> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
— End of inner exception stack trace —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException[TResult](Task`1 task)
at SLDisDMAComm.SLDisDmaCommService.ConnectToWebApi() in D:aDISDISProtocolEditorSLDisDMACommSLDisDmaCommService.cs:line 1203
at SLDisDMAComm.SLDisDmaCommService.ConnectToWebApi() in D:aDISDISProtocolEditorSLDisDMACommSLDisDmaCommService.cs:line 1224
at SLDisDMAComm.SLDisDmaCommService.Connect(String hostname, String username, String password, String accessToken) in D:aDISDISProtocolEditorSLDisDMACommSLDisDmaCommService.cs:line 219"