locked
Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm RRS feed

  • Question

  • Hello Team,

    Please I need assistance with below error installing ATA Lightweight Gateway server on VM in VMware environment.

    When the DC attempt to register, the connection do close

    The Gateway log:

    [141C:24D0][2017-08-01T18:32:50]i001: Burn v3.11.0.1701, Windows v6.3 (Build 9600: Service Pack 0), path: C:\Users\ADMINI~1.FIR\AppData\Local\Temp\3\{2AAE8D36-6B3B-4787-8E71-174A81D0294A}\.cr\Microsoft ATA Gateway Setup.exe
    [141C:24D0][2017-08-01T18:32:50]i000: Initializing string variable 'InstallationConfigurationFilePath' to value '[WixBundleOriginalSourceFolder]\GatewayInstallationConfiguration.json'
    [141C:24D0][2017-08-01T18:32:50]i000: Initializing hidden variable 'ConsoleAccountPassword'
    [141C:24D0][2017-08-01T18:32:50]i000: Initializing hidden variable 'ManagementAuthenticationToken'
    [141C:24D0][2017-08-01T18:32:50]i000: Initializing string variable 'NetFrameworkCommandLineArguments' to value '/passive /showrmui'
    [141C:24D0][2017-08-01T18:32:50]i009: Command Line: '"-burn.clean.room=C:\Users\administrator.domain\Desktop\Microsoft ATA Gateway SetupLatest\Microsoft ATA Gateway Setup.exe" -burn.filehandle.attached=336 -burn.filehandle.self=332'
    [141C:24D0][2017-08-01T18:32:50]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\administrator.domain\Desktop\Microsoft ATA Gateway SetupLatest\Microsoft ATA Gateway Setup.exe'
    [141C:24D0][2017-08-01T18:32:50]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\administrator.domain\Desktop\Microsoft ATA Gateway SetupLatest\'
    [141C:24D0][2017-08-01T18:32:52]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\ADMINI~1.FIR\AppData\Local\Temp\Microsoft Advanced Threat Analytics Gateway_20170801183252.log'
    [141C:24D0][2017-08-01T18:32:52]i000: Setting string variable 'WixBundleName' to value 'Microsoft Advanced Threat Analytics Gateway'
    [141C:24D0][2017-08-01T18:32:52]i000: Setting string variable 'WixBundleManufacturer' to value 'Microsoft Corporation'
    [141C:24D0][2017-08-01T18:32:52]i000: Loading managed bootstrapper application.
    [141C:24D0][2017-08-01T18:32:52]i000: Creating BA thread to run asynchronously.
    [141C:24D0][2017-08-01T18:32:52]i100: Detect begin, 7 packages
    [141C:24D0][2017-08-01T18:32:52]i000: 2017-08-01 17:32:52.6468 5148 1   Debug [\[]DeploymentModel[\]] DetectBegin [\[]Installed=False[\]]
    [141C:24D0][2017-08-01T18:32:52]i000: Setting string variable 'NetFrameworkRegistryValue' to value '460805'
    [141C:24D0][2017-08-01T18:32:52]i000: Setting string variable 'ServerLevelsServerCoreRegistryValue' to value '1'
    [141C:24D0][2017-08-01T18:32:52]i000: Setting string variable 'ServerLevelsServerGuiShellRegistryValue' to value '1'
    [141C:24D0][2017-08-01T18:32:52]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB3047154_RTM~31bf3856ad364e35~amd64~~6.3.2.0'
    [141C:24D0][2017-08-01T18:32:52]i000: Setting numeric variable 'KB3047154Exists' to value 0
    [141C:24D0][2017-08-01T18:32:52]i052: Condition 'NetFrameworkRegistryValue >= 394254' evaluates to true.
    [141C:24D0][2017-08-01T18:32:52]i052: Condition 'NetFrameworkRegistryValue >= 394254' evaluates to true.
    [141C:24D0][2017-08-01T18:32:52]i052: Condition 'KB3047154Exists' evaluates to false.
    [141C:24D0][2017-08-01T18:32:52]i101: Detected package: NetFrameworkPackageServer, state: Present, cached: None
    [141C:24D0][2017-08-01T18:32:52]i101: Detected package: NetFrameworkPackageServerCore, state: Present, cached: None
    [141C:24D0][2017-08-01T18:32:52]i101: Detected package: KB3047154Package, state: Absent, cached: None
    [141C:24D0][2017-08-01T18:32:52]i101: Detected package: VcRedistributable2013Package, state: Absent, cached: None
    [141C:24D0][2017-08-01T18:32:52]i101: Detected package: PefNdisDriver, state: Absent, cached: None
    [141C:24D0][2017-08-01T18:32:52]i101: Detected package: BundleActionsPackage, state: Absent, cached: None
    [141C:24D0][2017-08-01T18:32:52]i101: Detected package: MsiPackage, state: Absent, cached: None
    [141C:24D0][2017-08-01T18:32:52]i199: Detect complete, result: 0x0
    [141C:0894][2017-08-01T18:32:52]i000: 2017-08-01 17:32:52.6624 5148 5   Debug [\[]DeploymentModel[\]] [\[]DeploymentAction=Install[\]]
    [141C:0894][2017-08-01T18:32:52]i000: 2017-08-01 17:32:52.7561 5148 5   Debug [\[]DeploymentModel[\]] [\[]IsAfterRestartAndConfigured=False[\]]
    [141C:0894][2017-08-01T18:33:08]i000: 2017-08-01 17:33:08.0847 5148 5   Error [\[]TaskAwaiter[\]] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm
       at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
       at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
       at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[\[][\]]& thumbPrint)
       at System.Net.Security.SecureChannel.GenerateToken(Byte[\[][\]] input, Int32 offset, Int32 count, Byte[\[][\]]& output)
       at System.Net.Security.SecureChannel.NextMessage(Byte[\[][\]] incoming, Int32 offset, Int32 count)
       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.BeginWrite(Byte[\[][\]] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState)
       at System.Net.TlsStream.UnsafeBeginWrite(Byte[\[][\]] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState)
       at System.Net.PooledStream.UnsafeBeginWrite(Byte[\[][\]] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at async Microsoft.Tri.Infrastructure.Extensions.HttpClientExtension.GetAsync[\[][\]](?)
       at async Microsoft.Tri.Common.Management.ManagementClient.<>c__DisplayClass9_0.<GetStatusAsync>b__0(?)
       at async Microsoft.Tri.Infrastructure.Extensions.HttpClientExtension.RequestAsync[\[][\]](?)
       at async Microsoft.Tri.Common.Management.ManagementClient.GetStatusAsync(?)
    [141C:0894][2017-08-01T18:33:08]i000: 2017-08-01 17:33:08.0879 5148 5   Error [\[]DeploymentModel[\]] Failed management authentication [\[]CurrentlyLoggedOnUser=domain\administratorStatus=FailedInternal Exception=System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm
       at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
       at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
       at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[\[][\]]& thumbPrint)
       at System.Net.Security.SecureChannel.GenerateToken(Byte[\[][\]] input, Int32 offset, Int32 count, Byte[\[][\]]& output)
       at System.Net.Security.SecureChannel.NextMessage(Byte[\[][\]] incoming, Int32 offset, Int32 count)
       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.BeginWrite(Byte[\[][\]] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState)
       at System.Net.TlsStream.UnsafeBeginWrite(Byte[\[][\]] buffer, Int32 offset, Int32 size, AsyncCallback asyncCallback, Object asyncState)
       at System.Net.PooledStream.UnsafeBeginWrite(Byte[\[][\]] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Tri.Infrastructure.Extensions.HttpClientExtension.<GetAsync>d__0`1.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Tri.Common.Management.ManagementClient.<>c__DisplayClass9_0.<<GetStatusAsync>b__0>d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Tri.Infrastructure.Extensions.HttpClientExtension.<RequestAsync>d__4`1.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Tri.Common.Management.ManagementClient.<GetStatusAsync>d__9.MoveNext()[\]]


    BR, David Sunday

    Wednesday, August 2, 2017 10:13 AM

Answers

  • see

    https://docs.microsoft.com/en-us/advanced-threat-analytics/troubleshooting-ata-known-errors

    Look for the row that talks about TLS.

    make sure the GW & Center machine can both use TLS.12. it might solve the problem.

    • Marked as answer by David Sunday Friday, August 11, 2017 9:14 AM
    Wednesday, August 2, 2017 1:20 PM

All replies

  • Are you able to access the Center's console UI from this machine using iexplore.exe with the same credentials?
    Wednesday, August 2, 2017 10:52 AM
  • Yes I can.

    BR, David Sunday

    Wednesday, August 2, 2017 11:02 AM
  • Are you able to access the Center's console UI from this machine using iexplore.exe with the same credentials?
    The problem is, the Gateway server (DC) does not seems to be able to make attempt to authenticate with the Center server when trying to register the lightweight gateway.

    BR, David Sunday

    Wednesday, August 2, 2017 11:10 AM
  • see

    https://docs.microsoft.com/en-us/advanced-threat-analytics/troubleshooting-ata-known-errors

    Look for the row that talks about TLS.

    make sure the GW & Center machine can both use TLS.12. it might solve the problem.

    • Marked as answer by David Sunday Friday, August 11, 2017 9:14 AM
    Wednesday, August 2, 2017 1:20 PM
  • I will try this and revert.

    Thanks.


    BR, David Sunday

    Wednesday, August 2, 2017 4:40 PM
  • thanks a lot , you saved me my job :)
    Thursday, February 28, 2019 4:47 PM