ATA Gateway Services not starting

[Paulo Silva]

After install my Ata Gateway I receive an error message:

The ammount of Ram and Core processor already is ok following the description of Microsoft but the service doesn't start.

Follow my error log file below:

2018-03-12 20:19:48.6278 3188 5   00000000-0000-0000-0000-000000000000 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Domain controllers are not configured
   at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
   at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)
2018-03-12 20:19:55.6199 1280 5   00000000-0000-0000-0000-000000000000 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Domain controllers are not configured
   at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
   at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)
2018-03-12 20:20:02.6015 692 5   00000000-0000-0000-0000-000000000000 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Domain controllers are not configured
   at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
   at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)
2018-03-12 20:20:09.4686 3840 5   00000000-0000-0000-0000-000000000000 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Domain controllers are not configured
   at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
   at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
   at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)

Anyone know what could be ? It's a fresh installation.

[#2]

You need to configure this Gateway instance via the configuration page in the console UI.

Once configured, it will sync within a few seconds and start OK.

Only Light Weight Gateways are "auto configured".

Eli.

[#3]

Hi Eli,

I already did it.

After add my domain in ATA center I receive a message that the service stopped.

And same going to the Gateway server and trying to start manually the service I receive the error 1067.

[#4]

The Center service is running OK?

The Console UI is working?

In the Failing Gateway logs, if you delete the current logs and start the service again,

Is the only error still 

"Domain controllers are not configured"

?

[#5]

The Center service is running OK? Yes

The Console UI is working? Yes

In the Failing Gateway logs, if you delete the current logs and start the service again,

Is the only error still 

"Domain controllers are not configured"

?

The same error back in the logs.

I already deleted the domain and add again and the same error appear and the service doesn't start.

[#6]

Notice that in the GW configuration , you should add the DC FQDN, not the domain.

See detailed instructions at

https://docs.microsoft.com/en-us/advanced-threat-analytics/install-ata-step5

So if your domain is domain.com, you should add DC1.domain.com, and not just domain.com.

[#7]

Hi Eli,

Sorry for my explanation.

What we configured was the FQDN as you said and not the domain.

But the service begin starting and fews seconds after stop.

Now i'll try to uninstall my Gateway and Center and begin all the installation process again.

[#8]

Try to uninstall the GW only, don't think there is a need to install the center again.

But do download a fresh copy of the GW package from the Center.

[#9]

I also already did it two times and no success.

Now i'm really gonna do all the installation again and see what happens.

[#10]

If it still fails, please share a screenshot of the GW configuration in the console.

(You can share it in a private message if you prefer)

[#11]

Eli,

I sent for you a private message with my gateway configuration.

Thanks

[#12]

What was the solution as I am experiencing the exact problem.

[#13]

In the above case a  rebuild of the WMI Repository solved the problem.

[#14]

Having this problem again in another environment...

I receiving again this error 1067 and I already saw:

- Network connections ok;

- Net framework installation ok;

- WMI library ok;

- enought hardware to run gateway lightweight;

Anyone know what could be ?

I already add another 10 DC's in my Ata center in the same environment, but there's one that is showing this error 1067.

In this case is the deployment of 1.9 version.

Below follow my error.log

2018-04-26 16:49:40.9293 4792 13 Error [DirectoryServicesClient+<CreateLdapConnectionAsync>d__32] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to connect to domain controller [DomainControllerDnsName=XXXXXAD04.XXXXXXXX.corp ErrorCode=82] ---> System.DirectoryServices.Protocols.LdapException: A local error occurred.
 at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 --- End of inner exception stack trace ---
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.TryCreateLdapConnectionAsync(?)
2018-04-26 16:49:40.9772 4792 5 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to communicate with configured domain controllers
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
 at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)
2018-04-26 16:49:54.3286 3096 12 Error [DirectoryServicesClient+<CreateLdapConnectionAsync>d__32] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to connect to domain controller [DomainControllerDnsName=XXXXXAD04.XXXXXXXX.corp ErrorCode=82] ---> System.DirectoryServices.Protocols.LdapException: A local error occurred.
 at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 --- End of inner exception stack trace ---
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.CreateLdapConnectionAsync(?)
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.TryCreateLdapConnectionAsync(?)
2018-04-26 16:49:54.3443 3096 5 Error [DirectoryServicesClient+<OnInitializeAsync>d__14] Microsoft.Tri.Infrastructure.Utils.ExtendedException: Failed to communicate with configured domain controllers
 at async Microsoft.Tri.Gateway.Resolution.DirectoryServices.DirectoryServicesClient.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.ModuleManager.OnInitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Module.InitializeAsync(?)
 at async Microsoft.Tri.Infrastructure.Framework.Service.OnStartAsync(?)
 at Microsoft.Tri.Infrastructure.Framework.Service.OnStart(String[] args)

[#15]

The GW is failing to connect to the *AD04 DC.

Error Code 82 suggest:

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.

Eli.

[#16]

DNS ok and the time in the Ata Gateway is ok too.

Do you have ideia if this problem could be caused by another thing ?

Thanks

[#17]

Try to restart the GW machine, I wonder if it will change anything.

---

@Paulo Silva wrote:

DNS ok and the time in the Ata Gateway is ok too.

Do you have ideia if this problem could be caused by another thing ?

Thanks

---

[#18]

It doesn't work.

I already add 3 other DC's to my Ata Center but this one don't work.

[#19]

Are you able to connect from these machines to the destination machines that ATA fails for using ldp.exe via kerberos? or are you getting the same error there?

[#20]

@Paulo Silva 

In my case, the problem was the user account of the directory services. For some reason it was disabled. I enabled it and changed the password. Then I wrote the new password in the Data sources section in ATA Center.
The service started successfully and it is possible to see the gateway in the ATA Center.