Async Client configuration tool connection failed

(0) Share

Report

Posted on by Adil_aat

Async client configuration tool connection failed. Upon further digging I came to know that two of the certificates are expired. Async connection was working well before certificate expiry. I renewed the certificate from IIS and updated thumb in the both webconfig files. But still its showing connection failed.

Do I need to do any further steps to renew the licence.

Kindly please advice.

3386.Async.png

I have the same question (0)

All responses (17)

Answers (2)

Adil_aat 35 on at

Like (0)

Report

I just tried to verify the metadata by using link https://server:8594/AsyncServer/UploadService.svc

and I got following page.

Was this reply helpful? Yes No
Shaimaa Abo Gabal on at

Like (0)

Report

Hi Abdul Adil,

You need to check the event viewer info and you can share it so that we can help you out on this . Also Make sure that computer name you are giving as full qualified name that includes domain name.

and please review this thread it can help you .

https://community.dynamics.com/ax/f/microsoft-dynamics-ax-forum/200711/async-client-installation-can-t-connect-to-async-server/575271

Was this reply helpful? Yes No
Adil_aat 35 on at

Like (0)

Report

Kindly find below event viewer reports

Microsoft.Dynamics.Retail.Pos.Customer.WinFormsTouch.frmNewCustomer, Text: New customer: 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.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)

at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)

at System.Net.TlsStream.CallProcessAuthentication(Object state)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)

at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.ConnectStream.WriteHeaders(Boolean async)

--- End of inner exception stack trace ---

at System.Net.HttpWebRequest.GetResponse()

at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout).

Second:

Real-time service connectivity failure.

Could not establish trust relationship for the SSL/TLS secure channel with authority 'g1db01.artcomm.com:8592'.

Server stack trace:

at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)

at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)

at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)

at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)

at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)

at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)

at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)

at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)

at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)

at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Microsoft.Dynamics.Retail.TransactionServices.ClientProxy.ITransactionService.InvokeMethod(RequestInfo requestInfo, String methodName, Object[] parameters)

at LSRetailPosis.TransactionServices.InvokeMethod(Nullable`1 timeout, String methodName, Object[] parameters, Int32[] parametersLength, Func`1 getClient)

Was this reply helpful? Yes No
Shaimaa Abo Gabal on at

Like (2)

Report

Be sure you copy/paste the Thumbprint correctly , some times there were hidden unicode characters which may be the reason why you are getting the error when browsing the retail server. You will not see it in notepad. Just place your cursor where the string starts and press Backspace until cursor actually moves. Or use more advanced text editor and you will be able to spot it.

Also reimport certificate on the client machine under Local Machine and the Async client user was added to the MSG database users group.

Was this reply helpful? Yes No
Suggested answer

A.Prasanna 8,223 on at

Like (0)

Report

Issue with the certificates or the thumbprints . Once you create certificates you need to add them in to Trusted Authorities , both client and the Server where Async Server Installed . also you need to add DNS /Host Records Accordingly .

First fix Async Server Issue , once you fix that you can see Service meta data when browsing, Service URL ,

then try to connect Async Client . Make sure to allow necessary Communication Ports open before trying to connect Async Client .

Hope this helps,

Amith Prasanna

Was this reply helpful? Yes No
Adil_aat 35 on at

Like (0)

Report

Hi Shaimaa

Thank you for your great reply.

I already used Notepad++ and removed the special unicode character from the thumb also tried to reimport the certificate 3 or 4 time in Async client.

May I know do I need to buy SSL Certificate or just need to create certificate from IIS ?

Was this reply helpful? Yes No
Adil_aat 35 on at

Like (0)

Report

Hi Amith,

Thank you for your reply.

The certificate is already added to trusted authorities in both server and client and didn't add DNS/Host records. Let me add DNS/Host record.

Please advice me how to add DNS/Host records.

Ports are already opened. It was working fine until 28th April 2020, Certificate expired on 28th April 2020.

Thank you

Was this reply helpful? Yes No
Suggested answer

A.Prasanna 8,223 on at

Like (1)

Report

Hi Abdul ,

Have you bind your renewed certificate with Async Server web Service .

refer this to crosscheck our changes : blog.johanpersson.nu/ (just ignore ADCS related setups )

Thanks ,

Amith Prasanna

Was this reply helpful? Yes No
Adil_aat 35 on at

Like (0)

Report

yes bind both async server and real time server with new certificate.

Was this reply helpful? Yes No
Suggested answer

A.Prasanna 8,223 on at

Like (1)

Report

Do one thing , just open your certificate and check what is under Issuer Name and it should match with

Server Name in your Async Server Url (https://<server>:8594/AsyncServer/UploadService.svc) , further more it's says Key Set Does not exists. so it's something to do with Certificates . remove old certificates which are already expired.

If you still hard to get what is happening Try to Use Fiddler to find out issues in your async service .

Amith Prasanna

Was this reply helpful? Yes No