Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 2013 on Server 2008...
Microsoft Dynamics GP (Archived)

GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

(0) ShareShare
ReportReport
Posted on by Community Member

I have installed GP 2013 on a Server 2008 R2 server & created a instance on a separate SQL 2008 R2 server. When I go into DB Maintenance on the GP server and try to connect to the instance on the SQL server it is telling me "Dynamics GP was not found on the SQL Server." Does Dynamics GP need to be installed on the SQL Server or am I doing something wrong. I have gone through the Installation PDF of both GP and SQL and have installed verbatim to what it is saying. I have the OBDC connector set up on the GP server and TCP/IP & Named Pipes are enabled for the \GP instance. What am I doing wrong?

*This post is locked for comments

  • Community Member Profile Picture
    Community Member on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    See that's the answer I was looking for. Thanks Richard. FYI yes I did change the default DB name.

  • Verified answer
    Richard Whaley Profile Picture
    Richard Whaley 25,195 on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    Are you sure the system database is GP?  Normally, unless you changed it, it would be Dynamics.

    Also, something people just refuse to understand.  THERE IS NO SQL INSTALL OF GP.  GP databases (DYNAMICS, TWO, YOUR COMPANY) are created on the SQL server.  You can also install a GP client on the SQL server and I typically recommend that for testing.  

    There is no such thing as a GP server.  GP is installed on each and every work station.  If you have a Terminal Server environment, GP is installed on the TS machine.  The ODBCs must point back to the SQL server and the ODBC names must all be the same.

  • Community Member Profile Picture
    Community Member on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    Also I have verified all these steps from a previous similar thread someone else posted.

    •Make sure the SQL Browser Service is running on the SQL Server.

    •Make sure that your SQL Server allows remote connections - you can check/change this in SQL Server Management Studio, under the server properties, on the Connections page.  

    •The error message says 'Named Pipes'.  Typically you want to use TCP/IP for GP, so I would make sure that TCP/IP is enabled in SQL Server Configuration Manager.

    •A lot of times we see issues with connecting to a SQL Server because of the Windows Firewall.  To test whether this is the issue, turn off the Windows Firewall on the SQL Server.  If that allows you to connect, then you will need to add exceptions to the Windows Firewall to allow SQL Server connections.

  • Community Member Profile Picture
    Community Member on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    Richard- I can ping the SQL server and RDP into from the GP box. I have created a 32bit ODBC System DSN using Native Client 11.0 on both the GP and the SQL server. I tried using IP address instead of the server name and I keep getting the error "Dynamic GP was not installed on the server".

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,796 Moderator on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    So the problem right now is that you GP(VM) does not see the GP(Physical) server at all? When you are in the 32 bit ODBC administrator and create the DSN, can you test the connection there to make sure it is good. Try using the IP address of your SQL box as opposed to the server name.

  • Community Member Profile Picture
    Community Member on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    Richard- Thanks for that. GP is installed on a Win2k8 R2 VM and SQL is installed on a physical Win2k8 R2 server. There is no possible way to link these two? It doesn't make sense that it wouldn't be able to connect to a separate DB on a different server. If I have to install GP on the physical SQL server does GP leave a large footprint or take up much resources?

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,796 Moderator on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    That would make your GP(VM) a GP client.

    In a multiuser local area network environment, Microsoft Dynamics GP

    applications are typically installed on a server, and then on each client. However,

    Microsoft Dynamics GP is not required to be installed on the server. Each client will

    have access to data stored on the server. You can install your clients using the

    Microsoft Dynamics GP media or using a client installation package. For more

    about creating an installation package for your clients, see Chapter 11, “Creating an

    installation package.”

    Please check out complete installtion instructions at this link

    technet.microsoft.com/.../hh686214(v=gp.20).aspx

  • Community Member Profile Picture
    Community Member on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    Richard- I have set up a separate instance on SQL server(physical server) that is not installed on the GP server(VM). SO there is no way to point the GP server installation to the instance on a separate machine?

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,796 Moderator on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    1) Install SQL on the server

    2) Install GP on the server

    3) Launch GP Utilities on the server

    This way all company databases will be created on the server and all initial database setup work is done on the server. Once the server is complete you move onto the workstations. I also create the GP package file on the server and store it in a share on the server poiting it to another common share for the forms,reports, letters and notes.

  • Community Member Profile Picture
    Community Member on at
    RE: GP 2013 on Server 2008 R2 will not connect to SQL Server 2008 instance

    Does GP need to be installed on the SQL server? That's what the error I originally posted seems to indicate...

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,865 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,723 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans