Instance connection in management studio 2014 but neither of the Access migration apps connect to the SQLSERVER

I get an error 0 connection refused by the SQLSERVER instance. 2014 SQL Server Management studio connects! But neither of the migration tools do! I've gone to http://go.microsoft.com/fwlink/?LiinkId=197502 and install the Microsoft access 2010 runtime and rebooted the system. NOT...still getting connection refused by the DB engine instance.

Now what?

September 2nd, 2015 7:13pm

  1. Open SQL Server Configuration Manager, and then expand SQL Server 2012 Network Configuration.
  2. Click Protocols for InstanceName, and then make sure TCP/IP is enabled in the right panel and double-click TCP/IP.
  3. On the Protocol tab, notice the value of the Listen All item.
  4. Click the IP Addresses tab: If the value of Listen All is yes, the TCP/IP port number for this instance of SQL Server 2012 is the value of the TCP Dynamic Ports item under IPAll. If the value of Listen All is no, the TCP/IP port number for this instance of SQL Server 2012 is the value of the TCP Dynamic Ports item for a specific IP address.
  5. Make sure the TCP Port is 1433.  ---check your port number
  6. Click OK.

If there are any more questions, please let me know.

Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2015 9:39pm

Hi kevomac,

Are you connecting from the migration tool to remote SQL Server instance? Do you get the following error message?

TCP Provider, error: 0 - No connection could be made because the target machine actively refused it

If that is the case, please go through the following checklist to troubleshoot the "connection refused" problem.
1. Make sure you are able to ping the server where SQL Server is installed.
2. As other post, ensure the SQL Server instance is enabled TCP/IP protocol in SQL Server Configuration Manager (SSCM) and it is listening on a valid TCP port.
3. If you connect to a named instance, make sure that the SQL Server Browser service is running.
4. Configure the Windows Firewall for the SQL Server TCP port and SQL Browser service if firewall is on.
5. Check out IPSec setting if you still face problem. See whether IPSec specification make dropping any packets.

For more details, please review the following blog.
http://blogs.msdn.com/b/sql_protocols/archive/2007/07/19/tcp-provider-no-connection-could-be-made-because-the-target-machine-actively-refused-it.aspx

Thanks,
Lydia

September 3rd, 2015 9:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics