Skip to main content
To homepage To homepage

Hi,

We have just installed TimeXtender on a VM on-prem and tries to start the applikation and the ODX Server Configuration. Both fails with the same error:

Error occurred while determining instance version or during performing aut. upgrade:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - 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.)

Details:

SQL Server: ''
SQL Error Number: 10060

I noticed that there is now server name in the error message. Is this supposed to be empty?

The SQL server name is provided in the portal för both instances that have been created (One ODX and one MDW).

We have no problems connecting to the SQL Server from same VM as TimeXtender is installed on with SSMS and dBeaver.
We have also tested Test-NetConnection -ComputerName servername -Port 1433. This also works fine.

Any ideas?

BR
Anders

Hi,

Some additional info:

  • The TX version is 6346.1
  • Connection to app-encryption-prod-001.azurewebsites.net   Port 443 and app.timextender.com  Port 443 have also been tested. No problem there.

BR

Anders

 

Hi @anders.e.jonsson 

Can you please check if the firewall prerequisites are met as described in the following article:

For example, 

Test-NetConnection sql-instances-prod.database.windows.net -Port 1433

Hi,

 

you can also get such an error if the ODX Server config app cannot establish a connection to the cloud repository TimeXtender hosts for you in Azure. It could be that your connection to sql-instances-prod.database.windows.net is not going correctly. You can capture such errors in networking tools like TCPView to find out what is going wrong.

Thanks,

It was port 1433 that wasn’t open to reach sql-instances-prod.database.windows.net.
Problem solved 😀.
BR
Anders

Reply


Terms and ConditionsCookie settings