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 :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP2010 Client Install
Microsoft Dynamics GP (Archived)

GP2010 Client Install

(0) ShareShare
ReportReport
Posted on by Joe Critchlow 1,145

I have a client that is on GP2010 and has replaced their workstations with new ones. These are 32 bit Windows 7 with 4GB of Ram. Dynamics GP installs with no errors. When the client first boots the machine and tries to login to Dynamics it freezes on the splash screen and we have to use task manager to kill the process. If you try to login again, it logs in just fine and will continue to work properly until you shut down and reboot. We also have the same issue with the ODBC Driver, it fails the test the first time then the second time it works and will continue to work until a reboot is done. We have re-installed GP, created a new ODBC Driver, Logged in as administrator, turned off UAC, turned off Windows Firewall, enabled named piped on the SQL Server, used the IP Address in the ODBC driver instead of the name of the SQL Server, and disabled anti virus. They have several new workstations that are acting the same with this issue. All of their old XP workstation work fine.

Any help would be appreciated.

Joe

*This post is locked for comments

I have the same question (0)
  • Victoria Yudin Profile Picture
    Victoria Yudin 22,769 on at

    Joe,

    I saw something similar a while ago where basically the first attempt to reach the SQL Server timed out, the second attempt, right afterwards, connected just fine. I believe the fix was opening an additional port on the SQL Server Windows firewall. I also seem to recall this may have been specific to a SQL version / service pack.

    What version and service pack of SQL Server are you using? Also, have you tried (just as a test) turning off the Windows firewall on the SQL server? (I could not tell from your post if you tried turning it off on the local machine or the SQL server.)

  • Joe Critchlow Profile Picture
    Joe Critchlow 1,145 on at

    Victoria,

    Thanks for your response. I am checking on the fire wall on the SQL Server (almost certain it is off), it is turned off on the workstation. They are currently on SQL 2008 (10.5.2500).

    Joe

  • Victoria Yudin Profile Picture
    Victoria Yudin 22,769 on at

    Joe,

    If the firewall is already off on the SQL Server, there is something else going on. Perhaps a SQL service is not turned on automatically...and gets turned on with the first attempt, or something else going wrong...might be worth posting on a SQL forum to ask.

    If you do find that the firewall on the SQL Server is turned on and turning it off addresses the issue, then let me know and I can try suggesting some additional steps to fix it with the firewall turned on.

  • Joe Critchlow Profile Picture
    Joe Critchlow 1,145 on at

    Victoria,

    Will do. Do you think it is worth applying the latest SP for SQL. The ironic thing is they will be going to SQL2012 and GP2013 in January, they are just trying to get the new machines in place, all of the old XP machines work fine.

    Joe

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,852 Moderator on at

    Victoria is on to something here. I would try using old versions of the SQL client. Perhaps look at your old XP computers and see what version is on there. Start by try just the SQL Server client not the SQL Native client. By the way, are these users local admins? If not, try giving them full control of the Dynamics GP folder and subfolders.

  • Victoria Yudin Profile Picture
    Victoria Yudin 22,769 on at

    Joe,

    It certainly won't hurt to apply SP 2 for SQL 2008 R2 (I think that's the latest), but I would be surprised if it made a difference.

    Now that I am thinking about this some more, since the old XP machines are fine, there must be some setting on the new machines that is causing the issue. And it's entirely possible that the issue will still be there with SQL 2012 / GP 2013.

    When you test the ODBC connection and it fails the first time, is there any detail in the error? Is there anything in the Event Viewer when this happens to give you more detail?

    If you let the GP login go the first time (without crashing out), will it eventually give you an error of any kind? (I would expect a time out.)

    Another thing you can try, just to get the error (which will hopefully help track this down) is to try to connect to the SQL Server from Excel on one of the new machines.

  • Joe Critchlow Profile Picture
    Joe Critchlow 1,145 on at

    Thanks Richard, I will give both of your suggestions a try.

  • Joe Critchlow Profile Picture
    Joe Critchlow 1,145 on at

    Victoria,

    The ODBC does fail the first time and we do get a time out error. (SQL Server error 258 - SQL State 08-001) I will check the event viewer as well. I will also try connecting via excel. We have let GP sit for 15-20 minutes and it never times out.

    Joe

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans