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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

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

(0) ShareShare
ReportReport
Posted on by

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

I have the same question (0)
  • Suggested answer
    Howard Swerdloff Profile Picture
    845 on at

    If the server is 64 bit, be sure you are setting up a 32 bit odbc. Go to run and choose C:\Windows\SysWOW64\odbcad32.exe

  • Community Member Profile Picture
    on at

    Thanks for the reply Howard. I have done this process as the PDF requested. ODBC Tested successfully with sa credentials.

  • KirkLivermont Profile Picture
    5,985 on at

    Have you ran GP Utilities yet?

  • Richard Wheeler Profile Picture
    75,848 Moderator on at

    Check your firewall setting. SQL uses port 1433 as a default. Perhaps this port is not open. Does this work if you on the same server as GP and SQL?

  • Suggested answer
    Community Member Profile Picture
    on at

    Hi Benp,

    it Supports SQL Server Native Client 11.0 and above

  • Suggested answer
    Community Member Profile Picture
    on at

    if it is 64 bit machine,it Supports SQL Server Native Client 11.0 and above or set 32 bit odbc. Go to run and choose C:\Windows\SysWOW64\odbcad32.exe

  • Community Member Profile Picture
    on at

    I have ran the GP Utilities and was able to log in but go the following errors then it exited.

    "Error message 35100 doesn't exist"

    "Failed upgrading table: DB_Upgrade."

  • Community Member Profile Picture
    on at

    Natarajan- I have ran on the GP server should I set up another OBDC on the SQL server as well pointing to the GP server?

    Richard - I opened these ports still no go.

  • Community Member Profile Picture
    on at

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

  • Richard Wheeler Profile Picture
    75,848 Moderator on at

    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.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans