TDX Collector Service will not run

The TDX Asset Discovery Scanner Service on our server will not start automatically nor will it continue running when manually started.

Several error messages appear in the TDX Discovery Manager.

Any ideas for solutions? Thanks.

 

Tags Discovery asset-discovery assetdiscovery
Asked by Andrew Brunetto on Tue 8/13/24 9:13 AM Last edited Tue 8/13/24 9:13 AM
Sign In to leave feedback or contribute an answer

Answers (2)

This answer has been marked as the accepted answer
Andrew Brunetto Wed 8/14/24 11:06 AM

I think we're down to performing a re-install.

One of the errors we are getting is "Service has been unregistered". Also, "

Unexpected end when deserializing array.

Path ", line 2, position 0."

 

No feedback
Ok submit a Support ticket so we can relay the install file to you. - Mark Sayers Wed 8/14/24 11:16 AM
Mark Sayers Tue 8/13/24 1:15 PM

Hello Andrew,

The one error message states that the IP address it attempted to reach was not in the list of WinRM Trusted Hosts. Did you take any action to allow those IP addresses like it states there in your screen shot?

Also it seems like the discovery manager may not be permitted to reach back out to the TDX IP addresses to register the discovery manager with your environment: https://app-eus.teamdynamix.com/meta/

Sincerely,
Mark Sayers
Sr Support Consultant, CS

No feedback
That IP is within the range of trusted hosts, per the range we entered in the "Trusted Hosts" box. Also, per our security officer, the TDX IP addresses are not being blocked.
Thanks. - Andrew Brunetto Wed 8/14/24 10:10 AM
Did the discovery scanner ever work properly for you, or when did it stop connecting successfully automatically? - Mark Sayers Wed 8/14/24 10:20 AM
Also, have you tried just *not* specifying any IP range on the discovery job? It isn't a requirement for jobs where you're just running the Agent Data Provider. - Mark Sayers Wed 8/14/24 10:25 AM
BTW, thank you for the help. The scanner was working fine for us until July 19th (as far as I can tell by the logs). Then it just stopped. I've been trying to determine if anything occurred or changed on our network or the server that day, but haven't found anything yet. - Andrew Brunetto Wed 8/14/24 10:42 AM
I know there isn't a new version of the discovery scanner installer, and new versions being released wouldn't invalidate existing installs of the scanner. I can't think of any reason why the scanner would suddenly fail outside of a local influence causing it. If you needed to reinstall it we could (through a Support ticket) provide you with a new installation file to use. - Mark Sayers Wed 8/14/24 10:58 AM