Troubleshooting ATA known issues
Applies to: Advanced Threat Analytics version 1.9
This section details possible errors in the deployments of ATA and the steps required for troubleshooting them.
ATA Gateway and Lightweight Gateway errors
| Error | Description | Resolution |
|---|---|---|
| System.DirectoryServices.Protocols.LdapException: A local error occurred | The ATA Gateway failed to authenticate against the domain controller. | 1. Confirm that the domain controller's DNS record is configured properly in the DNS server. 2. Verify that the time of the ATA Gateway is synchronized with the time of the domain controller. |
| System.IdentityModel.Tokens.SecurityTokenValidationException: Failed to validate certificate chain | The ATA Gateway failed to validate the certificate of the ATA Center. | 1. Verify that the Root CA certificate is installed in the trusted certificate authority certificate store on the ATA Gateway. 2. Validate that the certificate revocation list (CRL) is available and that certificate revocation validation can be performed. |
| Microsoft.Common.ExtendedException: Failed to parse time generated | The ATA Gateway failed to parse syslog messages that were forwarded from the SIEM. | Verify that the SIEM is configured to forward the messages in one of the formats that are supported by ATA. |
| System.ServiceModel.FaultException: An error occurred when verifying security for the message. | The ATA Gateway failed to authenticate against ATA Center. | Verify that the time of the ATA Gateway is synchronized with the time of the ATA Center. |
| System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://center.ip.addr:443/IEntityReceiver | The ATA Gateway failed to establish a connection to the ATA Center. | Ensure that the network settings are correct and that the network connection between the ATA Gateway and the ATA Center is active. |
| System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable. | The ATA Gateway failed to query the domain controller using the LDAP protocol. | 1. Verify that the user account used by ATA to connect to the Active Directory domain has read access to all the objects in the Active Directory tree. 2. Make sure that the domain controller is not hardened to prevent LDAP queries from the user account used by ATA. |
| Microsoft.Tri.Infrastructure.ContractException: Contract exception | The ATA Gateway failed to synchronize the configuration from the ATA Center. | Complete configuration of the ATA Gateway in the ATA Console. |
| System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. | Message Analyzer is installed on the ATA Gateway. | Uninstall Message Analyzer. |
| Error [Layout] System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. | The ATA Gateway does not have enough memory. | Increase the amount of memory on the domain controller. |
| Fail to start live consumer ---> Microsoft.Opn.Runtime.Monitoring.MessageSessionException: The PEFNDIS event provider is not ready | PEF (Message Analyzer) was not installed correctly. | If using Hyper-V, try to upgrade Hyper-V Integration services otherwise, contact support for a workaround. |
| Installation failed with error: 0x80070652 | There are other pending installations on your computer. | Wait for the other installations to complete and, if necessary, restart the computer. |
| System.InvalidOperationException: Instance 'Microsoft.Tri.Gateway' does not exist in the specified Category. | PIDs was enabled for process names in the ATA Gateway | See Handling Duplicate Instance Names to disable PIDs in process names |
| 'System.InvalidOperationException: Category does not exist. | Counters might be disabled in the registry | Use KB2554336 to rebuild Performance Counters |
| System.ApplicationException: Unable to start ETW session MMA-ETW-Livecapture-a4f595bd-f567-49a7-b963-20fa4e370329 | There is a host entry in the HOSTS file pointing to the machine's shortname | Remove the host entry from C:\Windows\System32\drivers\etc\HOSTS file or change it to an FQDN. |
| System.IO.IOException: Authentication failed because the remote party has closed the transport stream or could not create an SSL/TLS secure channel | TLS 1.0 is disabled on the ATA Gateway, but .Net is set to use TLS 1.2 | Enable TLS 1.2 for .Net by setting the registry keys to use the operating system defaults for SSL and TLS, as follows:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] " SchUseStrongCrypto"=dword:00000001 |
| System.TypeLoadException: Could not load type 'Microsoft.Opn.Runtime.Values.BinaryValueBufferManager' from assembly 'Microsoft.Opn.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' | ATA Gateway failed to load required parsing files. | Check to see if Microsoft Message Analyzer is currently installed. Message Analyzer is not supported to be installed with the ATA Gateway / Lightweight Gateway. Uninstall Message Analyzer and restart the Gateway service. |
| System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required | The ATA Gateway communication with the ATA Center is being disrupted by a proxy server. | Disable the proxy on the ATA Gateway machine. Note that proxy settings may be per-account. |
| System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003) | One or more of the services needed to operate ATA did not start. | Start the following services: Performance Logs and Alerts (PLA), Task Scheduler (Schedule). |
| System.Net.WebException: The remote server returned an error: (403) Forbidden | The ATA Gateway or Lightweight Gateway was forbidden from establishing an HTTP connection because the ATA Center is not trusted. | Add the NetBIOS name and FQDN of the ATA Center to the trusted websites list and clear the cache on Internet Explorer (or the name of the ATA Center as specified in the configuration if the configured is different than the NetBIOS/FQDN). |
| System.Net.Http.HttpRequestException: PostAsync failed [requestTypeName=StopNetEventSessionRequest] | The ATA Gateway or ATA Lightweight Gateway can't stop and start the ETW session that collects network traffic due to a WMI issue | Follow the instructions in WMI: Rebuilding the WMI Repository to fix the WMI issue |
| System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions | Another application is using port 514 on the ATA Gateway | Use netstat -o to establish which process is using that port. |
Deployment errors
| Error | Description | Resolution |
|---|---|---|
| .Net Framework 4.6.1 installation fails with error 0x800713ec | The pre-requisites for .Net Framework 4.6.1 are not installed on the server. | Before installing ATA, verify that the windows updates KB2919442 and KB2919355 are installed on the server. |
| System.Threading.Tasks.TaskCanceledException: A task was canceled | The deployment process timed out as it could not reach the ATA Center. | 1. Check network connectivity to the ATA Center by browsing to it using its IP address. 2. Check for proxy or firewall configuration. |
| System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required. | The deployment process timed out as it could not reach the ATA Center due to a proxy misconfiguration. | Disable the proxy configuration before deployment, then enable the proxy configuration again. Alternatively, you can configure an exception in the proxy. |
| System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host | Enable TLS 1.2 for .Net by setting the registry keys to use the operating system defaults for SSL and TLS, as follows:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 |
|
| Error [\[]DeploymentModel[\]] Failed management authentication [\[]CurrentlyLoggedOnUser=<domain>\<username>Status=FailedAuthentication Exception=[\]] | The deployment process of the ATA Gateway or ATA Lightweight Gateway could not successfully authenticate against the ATA Center | Open a browser from the machine on which the deployment process failed and see if you can reach the ATA Console. If not, start troubleshooting to see why the browser can't authenticate against the ATA Center. Things to check: Proxy configurationNetworking issuesGroup policy settings for authentication on that machine that differs from the ATA Center. |
| Error [\[]DeploymentModel[\]] Failed management authentication | Center certificate validation failed | The Center certificate may require an internet connection for validation. Make sure your Gateway service has the proper proxy configuration to enable the connection and validation. |
| While deploying the Center and selecting a certificate, a "Not supported" error is reported | This can happen if either the certificate selected does not meet the requirements or the private key of the certificate is not accessible. | Make sure you are running the deployment with elevated privileges (Run as administrator) and that the selected certificate meets the requirements. |
ATA Center errors
| Error | Description | Resolution |
|---|---|---|
| System.Security.Cryptography.CryptographicException: Access denied. | The ATA Center failed to use the issued certificate for decryption. This most likely happened due to use of a certificate with KeySpec (KeyNumber) set to Signature (AT\_SIGNATURE) which is not supported for decryption, instead of using KeyExchange (AT\_KEYEXCHANGE). | 1. Stop the ATA Center service. 2. Delete the ATA Center certificate from the center's certificate store. (Before deleting, make sure you have the certificate backed up with the private key in a PFX file.) 3. Open an elevated command prompt and run certutil -importpfx "CenterCertificate.pfx" AT\_KEYEXCHANGE 4. Start the ATA Center service. 5. Verify everything now works as expected. |
ATA Gateway and Lightweight Gateway issues
| Issue | Description | Resolution |
|---|---|---|
| No traffic received from the domain controller, but health alerts are observed | No traffic was received from a domain controller using port mirroring through an ATA Gateway | On the ATA Gateway capture NIC, disable these features in Advanced Settings: Receive Segment Coalescing (IPv4) Receive Segment Coalescing (IPv6) |
| This health alert is displayed: Some network traffic is not being analyzed | If you have an ATA Gateway or Lightweight Gateway on VMware virtual machines, you might receive this health alert. This happens because of a configuration mismatch in VMware. | Set the following settings to 0 or Disabled in the virtual machine NIC configuration: TsoEnable, LargeSendOffload, TSO Offload, Giant TSO Offload |
Multi Processor Group mode
For Windows operating systems 2008R2 and 2012, ATA Gateway is not supported in Multi Processor Group mode.
Suggested possible workarounds:
If hyperthreading is on, turn it off. This may reduce the number of logical cores enough to avoid needing to run in Multi Processor Group mode.
If your machine has less than 64 logical cores and is running on a HP host, you may be able to change the NUMA Group Size Optimization BIOS setting from the default of Clustered to Flat.
See Also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for