Can't connect to remote SQL

[Anonymous]

I tried to install the ADMS Professional 2015 on a new server and need to connect to a remote SQL server and i receive the known error : Failed to connect to SQL server- server=server\AUTODESKVAULT;user id=sa;password=******;

I tried a lot of things with the help of my DBA and we can't find the solution for this one.

Remote connection is enable on the SQL.

The user running the sql have access to the new server and the remote Share configured on the server where i install adms 2015.

We can log as SA and the default password on the remote SQL.

All firewall has been configured with the correct exceptions, even disable completly on both servers.

TCP/IP is enable and a custom port has been assign in SQL configuration manager. Alias configured in Cliconfig.exe (32 and 64 bit) for the new port.

Tried to redownload adms 2015.

Tried this, didn't worked.

Tried this, didn't worked.

I had this problem before and most of the time it's the SA password that is not correct.

Thanks for your help.

[Neil_Cross]

On the server running the SQL instance for Vault, what Log on account is being used against the service?

[Anonymous]

Hi Neil, it's an account used for SQL services, we gave this user domain admin rights.

[Neil_Cross]

Is the server you're connecting to (the SQL server) running the same version of ADMS Professional as the one you're trying to connect from? Same version, service pack level etc?

I noticed in the first post you did, you removed the text 'localhost' from the error message, is this significant in any way? Obviously localhost would be trying to connect to the server you're working on.

[Anonymous]

No the remote server only have SQL installed.

I changed the localhost because i copy and paste from an other thread, i see it afterward that the SQL was local.

But in my case, the SQL is remote and it's only the main SQL for the company, no ADMS installed.

[Neil_Cross]

This is very difficult to troubleshoot over a forum because there are a lot of things which could cause this.

Are you 100% sure the remote instance was installed correctly? i.e. definitely called AUTODESKVAULT, mixed mode authentication, SQL service and agent are started, you can ping the remote server ok.

When you're attempting to connect to the remote SQL instance, you're not putting the \\ before the server name? 

[Neil_Cross]

Just checking, which version and service pack level of SQL is this instance installed into? 

[Anonymous]

I can confirm that the instance was installed correctly.

The SQL version is 2014, i know ADMS Pro 2015 is not officially supported on this version, but i was able to install it for other clients.

And i also tried with ADMS Pro 2016 wich is officially supported on SQL 2014 and i have the same error.

And i totally agree with you, not easy to troubleshoot this kind of problem on forum.

[Andy.Spivey]

//Edited to add image//

Hi Eric,

Just to verify - when you view your SQL Configuration Manager, and view the netowrk configuration and protocols for the AUTODESKVAULT instance:

• TCP/IP is enabled
• When viewing the IP addresses tab under the TCP/IP properties, IPALL has NO value for TCP Dynamic Ports and TCP Port is entered with a custom port number (like 1433 for example)

If that is all correct, can you:

Run Telnet or TCPING from the vault server and attempt to reach the remote SQL box on the port specified above?

If that fail, does it fail immediatly (indicating a possible FW deny) or after several seconds (indicating a possible timeout / no response)

If it fails immediatly, please double check the firewall settings.

If it fails after several seconds, please try starting the SQL Browser service and trying it again.

-Andy

[Anonymous]

Hi Andy, thank you for your help.

A short answer to your questions is yes to all, except for the ping that worked.

And my custom port was 1443.

But i think a have found the problem, i am not sure yet i will confirm tomorrow morning.

Because i have add the port 1443 for UDP in the firewall and my customer said now the setup is working, so i think the SQL browser listen for incoming connections from UDP.

I will keep you inform and also inform the Autodesk support to add this in their procedure.

Thanks again for your help, it's very appreciated.

[Andy.Spivey]

Thanks Eric - I believe the UDP 1434 is only required if dynamic ports is in use for a named instance. But yes, the SQL Browser listens on UDP port 1434.

Perhaps the instance was not restarted when the static port was assigned?

Let us know if things are all set - happy to help.