Skip to main content
To homepage To homepage
Solved

IngestServer fails connecting to our data sources

  • March 30, 2026
  • 2 replies
  • 57 views
B
Contributor
Forum|alt.badge.img+1

Hi,

TimeXtender Data Integration 7303.1

TimeXtender Ingest Service 7313.1

  

We are connected to our Azure Datalake Gen2 storagecontainer (tested OK through TDI)

 

We are having problems with our ingestserver trying to connect to all our data sources. All of them are timing out when running and they fails with no log

 

The only log we kan find are from TimeXtender O&DQ Desktop (see att.)

We have been trough https://support.timextender.com/initial-setup-start-here-115/configure-your-firewall-700 and done the tests,  all OK

Test-NetConnection sql-instances-prod.database.windows.net -port 20000
Test-NetConnection sql-instances-prod-002.database.windows.net -port 20000

Test-NetConnection traws.timextender.com -Port 443

Test-NetConnection gateway.timextender.com -Port 443
Test-NetConnection gateway.timextender.com -Port 80

Test-NetConnection sbns-customer-prod-001.servicebus.windows.net -port 5671
Test-NetConnection sbns-customer-prod-001.servicebus.windows.net -port 5672

Test-NetConnection auth0.com -Port 443
Test-NetConnection eu.auth0.com -Port 443
Test-NetConnection cdn.auth0.com -Port 443
Test-NetConnection app.timextender.com -Port 443
Test-NetConnection app-encryption-prod-001.azurewebsites.net -Port 443

 

The fails started on friday evening, and we did an ugrade from 7303.1 to TimeXtender Ingest Service 7313.1 on saturday.

 

best regards,

Bjørn A.

  

Best answer by Thomas Lind

Hi ​@bjorn 

I see you added a ticket internally and that you got this issue resolved.

Do you want to add what was done to make this work, if others experience the same issue?

 

 

2 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • Answer
  • April 7, 2026

Hi ​@bjorn 

I see you added a ticket internally and that you got this issue resolved.

Do you want to add what was done to make this work, if others experience the same issue?

 

 

B
Contributor
Forum|alt.badge.img+1
  • bjorn
  • Author
  • Contributor
  • May 4, 2026

Hi,

We have not received details of any specific changes made to the Trend Micro Agent binaries or versioning. However, modifications were applied to Trend Micro configuration settings and filtering rules.

This strongly suggests that the root cause was related to the agent’s inspection mechanisms (e.g. traffic inspection, process monitoring, or behaviour analysis), which were incorrectly classifying legitimate application activity as malicious.

The issue was mitigated by adjusting security policies, exclusions, or inspection filters, thereby eliminating false positives and allowing the affected traffic and processes to operate as intended.


regards,

Bjørn A.

    Terms and ConditionsAccessibility statement