web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Upgraded from GP2013 to GP2016 and ODBC 32-bit fails on all workstations but ok on server

(0) ShareShare
ReportReport
Posted on by 246

I just upgraded GP2013 to GP2016.  I installed SQL Express 2014 sp2.  The upgrade was performed on the server and all upgraded successfully.  I was able to create the ODBC 32-bit connection on the server no problem.  However, when I try to create the odbc connection on the workstation it fails on all of them (4 workstations)  The workstations are all windows 10pro.  I did verify that remote connections are enabled.  I also reinstalled SQL 2014 R2 and had the same result.   HELP???

I get the following error:

Microsoft SQL Server Native Client Version 11.00.7001

Running connectivity tests...

Attempting connection
[Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
[Microsoft][SQL Server Native Client 11.0]Login timeout expired
[Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

TESTS FAILED!

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Steve Rodionoff Profile Picture
    261 on at

    Make sure you have allowed the SQL port through the firewall (normally 1433)

    here is the script I run (elevated command prompt) on the SQL Server.

    @echo =========  SQL Server Ports  ===================
    @echo Enabling SQLServer default instance port 1433
    netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433
    @echo Enabling Dedicated Admin Connection port 1434
    netsh advfirewall firewall add rule name="SQL Admin Connection" dir=in action=allow protocol=TCP localport=1434
    @echo Enabling Conventional SQL Server Service Broker port 4022
    netsh advfirewall firewall add rule name="SQL Service Broker" dir=in action=allow protocol=TCP localport=4022
    @echo Enabling Transact SQL/RPC port 135
    netsh advfirewall firewall add rule name="SQL Debugger/RPC" dir=in action=allow protocol=TCP localport=135
    @echo Enabling SQL Server Browser Service port 2382
    netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
    @echo Enabling port for SQL Server Browser Service's 'Browse' Button
    netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=UDP localport=1434
    @echo Enabling SSAS Default Instance port 2383
    netsh advfirewall firewall add rule name="Analysis Services" dir=in action=allow protocol=TCP localport=2383

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    In addition to the firewall remember that since you are using SQL Express the SQL instance is SQLEXPRESS\servername not just the server name.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
HP-11021721-0 Profile Picture

HP-11021721-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans