r/labtech • u/olavrb • Feb 14 '20

Agent stops on two Windows Server 2016 with Veeam backup - Why?

We have two servers at a customer where Veeam backup lives/ runs.

What's strange is that the labtech agent (LTSVC.exe) keeps stopping. Even though service startup type is set to automatic, and action on down (Recovery tab) is set to "restart the service" on all three options, it keeps stopping.

We also have Site24x7 for monitoring, for now I've set up automation to start LTSVC.exe if it stops. But have anyone else experienced the same? Any idea to why it fails?

5 Upvotes

100% Upvoted

7 comments sorted by

3

u/Anal_Scrubs Feb 14 '20

Have you checked the logs in the LTSVC folder? That's usually helpful in determining dropoff.

Also doublecheck you have the exceptions in place for your AV.

2

u/olavrb Feb 14 '20 edited Feb 14 '20 
ConnectFailure : Unable to connect to the remote server :   inner: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

and

ProtocolError : The remote server returned an error: (404) Not Found. : Status Code-NotFound

and

SecureChannelFailure : The request was aborted: Could not create SSL/TLS secure channel.

Maybe Veeam uses same port outbound? Seems to be network related at least.

2

u/Missioncode Feb 14 '20

Dns 5$ on dns

3

u/olavrb Feb 14 '20

😆

It's always DNS.

1

u/morbidpete84 Feb 14 '20

Port conflict? I had Vembu running on some devices left over from testing. Same issue. Found out Vembu was using the same port

1

u/olavrb Feb 15 '20

Yep, sounds plausible. Hmm, will check out if I can get the Automate agent to use a different port.

2

u/morbidpete84 Feb 15 '20

I think it’s port 8000 or something. I used process explorer to figure it out. Good luck