Self Diagnostic Fails the Self Check - HTTPS Activation Not Working

Problem reported by Jeremy Farrance - 10/14/2015 at 7:25 AM

Resolved

Since last night at about 10:15pm Central (10/13/15), and still happening now (11 hours later) the SmarterMail Check-Up (self-diagnostic page at /About/Checkup.aspx) is reporting the following errors.

Under Internet Connectivity

Failed

https to activation page

and

Product Checks
Failed	Activation ECHO A0
	Notes: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) 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.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) 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.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at SmarterTools.Common.ActivationService.ActivationV2.Echo(String s) at SMWeb.About.Checkup.VerifyActivationEcho(StringBuilder sb, Int32 server)

Product Checks

Failed

Activation ECHO A0

Notes: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) 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.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) 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.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at SmarterTools.Common.ActivationService.ActivationV2.Echo(String s) at SMWeb.About.Checkup.VerifyActivationEcho(StringBuilder sb, Int32 server)

4 Replies

Reply to Thread

ScottF Replied

10/14/2015 at 10:49 AM

I'm seeing it too. What is "ECHO A0"?

Also here:

http://mail.smartertools.com/About/Checkup.aspx

Employee Replied

10/14/2015 at 11:56 AM

Employee Post

Greetings,

This is currently a known issue on our end that should be corrected this evening during a scheduled maintenance window. The failure is stating that it's unable to establish a secure connection to our A0 activation server, however we do have multiple servers in place to handle this type of incident.

This error will not prevent the product from activating and will not cause your installation to stop functioning in any way. If you do encounter any issues activation, please let us know by submitting a ticket to our sales department within the portal, or e-mailing sales@smartertools.com directly and we will get you taken care of.

Employee Replied

10/14/2015 at 1:56 PM

Employee Post

This issue should now be resolved on our end. No further errors should be present in the activation section of the diagnostics page.

David . Replied

10/14/2015 at 8:33 PM

The activation information should not be public. The information exposes sensitive information.

It is very easy to look for sites that offer this information.

-----------------------------------------------------------------------

Info    SmarterTrack Version: 11.3.5752
Info    Hosting Process: w3wp
Info    Pipeline Mode: Integrated
Passed    Microsoft.Net Framework Version: 4.0.30319

Info    NT Username to use for permissions: IIS APPPOOL\SmarterTrack
Passed    /App_Data/Logs/
Passed    /App_Data/Attachments/ read test
Passed    /App_Data/Attachments/
Passed    /App_Data/Config/ read test
Passed    /App_Data/Config/
Passed    /App_Data/Temp/ read test
Passed    /App_Data/Temp/
Passed    C:\Windows\Temp

Back to Community Threads

Please leave this box unchecked

4 Replies

Reply to Thread

Tags

Related Knowledge Base Articles