Hands On With Microsoft Dynamics GP 2015 RTM: Desktop Client Installation

Microsoft Dynamics GPNow that Microsoft Dynamics GP 2015 RTM is available, I thought I could follow my usual pattern of posting a series of posts o how to install and configure both Dynamics GP, but also the additional products which ship with it. You can find the series index for these posts here. I am assuming you already have your server built with Windows, an Active Directory Domain, SQL Server and SSRS for this series.

In this first post, I’ll be taking a look at the installation of the Dynamics GP 2015 RTM desktop client which, since the abolition of the server components prior to the release of Dynamics GP 10, needs to be done on at least one machine in order to deploy the system database.

Once you have downloaded an unpacked the media for Dynamics GP 2015 RTM, open the folder and double click on the setup.exe to launch the Microsoft Dynamics GP2015 setup utility. In the Install section click on Microsoft Dynamics GP and choose Install:

Microsoft Dynamics GP 2015 - Setup Utility

Continue reading “Hands On With Microsoft Dynamics GP 2015 RTM: Desktop Client Installation”

FRx – Such A Small Typo, Such A Big Effect

Microsoft Dynamics GPSometimes it is difficult to see the cause of a problem. We’re in the process of upgrading a heavily customised installation of Microsoft Dynamics GP for a client and are installing the new version on a new environment.

When it came to installing FRx I had a bit of a problem. I had installed and configured it on the SQL Server without any problem, but when I installed it on a Terminal Server I ran into the following error;

FRx Professional - FRx32.OSFIMain.CheckOFSIConnection - 8900: Frx is unable to open a connection to the general ledger database because the specified ODBC data source is not value. Verify that the data source exists on the computerFRx Professional – FRx32.OSFIMain.CheckOFSIConnection – 8900: Frx is unable to open a connection to the general ledger database because the specified ODBC data source is not value. Veryify that the data source exists on the computer

Continue reading “FRx – Such A Small Typo, Such A Big Effect”

Management Reporter Legacy Connector Company Logon Works Only For sa

Microsoft Dynamics GPI’ve been having a bit of a Management Reporter time recently; not that I especially mind as I like Management Reporter. In this instance I did some configuration of Management Reporter for a client (see my recent post on the Data Mart) and checked everything out as A-OK.

I then asked one of the clients to try, but she got an error stating “Unable to connect to the LIVE company. The connection to the Microsoft Dynamics GP database failed. Contact your system administrator”.

Well, I logged back in and tried again and was again able to log in without a problem. A little more exploring and I was able to establish that only when I logged in as the sa user was I able to run Management Reporter without a problem.

This is not an error I have seen before so a little investigation determined the problem is because I configured the Management Reporter Data Mart Connector I had used the machine name as the connection to the server, but the client machines are configured to use the CNAME alias in the ODBC connection instead of the machine name.

KB Article 2737852 outlines two methods of correcting the problem. The first is to change the client machines ODBC entry to match that used to configure the Data Mart and which I did not want to do as it was set up so passwords would not need to be reset if GP was moved to a different server.

The second method is to edit some data in the Management Reporter database to change the GLEntityConnectionInformation column so that it matches the ODBC on the client machines. This is the method I opted for and, after making the change, the client confirmed she was able to access Management Reporter.

Updated following comment from Peter Bailey

How To Create An ODBC For Microsoft Dynamics GP 2010

Microsoft Dynamics GPI’ve recently had the need to document the install process for Microsoft Dynamics GP 2010 for a new client so I thought I might as well finish off the task and but turning it into a small series of blog posts, the first of which will cover the manual creation of an ODBC connection.

To connect the Microsoft Dynamics GP client to the databases on SQL Server, an ODBC connection needs to be setup. In an x86 version of Windows this can be done using the ODBC Control Panel applet, but in an x64 version you need to use the x86 version of the ODBC Data Source Administrator.

The easiest way of accessing this is by using the Run window and opening %windir%\SysWOW64\odbcad32.exe;


Continue reading “How To Create An ODBC For Microsoft Dynamics GP 2010”

PSTL Registration Error

Microsoft Dynamics GPEarlier this month the Microsoft Dynamics GP Support Blog announced that the Professional Services Tools Library had been made free of charge and can be downloaded from here (PartnerSoruce login required; Customers will need to contact their partner).

It’s a while since I did much with PSTL so I decided to download it and take a look. I got it installed correctly but when I tried to open it I got this error;

Microsoft Dynamics GP - Unhandled script exception: [Microsoft][SQL Server Native Client 10.0][SQL Server]Could not find stored procedure 'PI.dbo.smChangeAccountIndex2'.

Continue reading “PSTL Registration Error”

Transferring GP To A New Server Without Resetting All Passwords

[One of the annoyances when migrating a client’s installation of Microsoft Dynamics GP to a new server is that, unless the new server has the same name as the old one, the password of every user needs to be reset as the server name is encrypted in with the password.

The is another alternative though and that is to create a DNS CNAME Alias and use this as the server name in the SQL Server ODBC instead of the servers actual name. When GP is migrated to a new box you only need to amend the DNS CNAME Alias and users can continue logging in with the same password. Continue reading “Transferring GP To A New Server Without Resetting All Passwords”

Error: Attempting To Log In From A Data Source Using A Trusted Connection

Microsoft Dynamics GPI’ve been building a test environment in a virtual machine the last few days to do a migration from Microsoft Dynamics GP 9 SP3 to 2010 R2.

After completing the upgrade I tried to log into GP and received the following error;


Continue reading “Error: Attempting To Log In From A Data Source Using A Trusted Connection”

Earlier Version of Dynamics.dic Than Installed

Microsoft Dynamics GPI did a test upgrade for a client recently (yes, I’ve been doing a few of these) so they could make sure everything still works and allow them to check out some of the new features.

I got this error message forwarded to me by one of the clients after he tried to login to do some testing;

You are using an earlier version of Dynamics.dic than the one that

Continue reading “Earlier Version of Dynamics.dic Than Installed”

Missing Data Source When Installing Microsoft Dynamics GP 2010

Microsoft Dynamics GPI have recently been upgrading an existing client to Microsoft Dynamics GP 2010 R2 from GP 10 SP1 on their test system. As they have lagged somewhat on versions I needed to upgrade them to GP 10 SP5 before then upgrading them to GP 2010 R2.

The databases were also being moved from a server running Microsoft SQL Server 2000 to one running SQL Server 2008; I would have preferred to move them to SQL Server 2008 R2 but due to some other business critical software to be installed on the same server, it needed to be SQL Server 2008 R1. Continue reading “Missing Data Source When Installing Microsoft Dynamics GP 2010”

ODBC For Microsoft Dynamics GP on Windows Server 2008 R2

Microsoft Dynamics GPWhen installing Microsoft Dynamics GP on an x64 OS such as Windows Server 2008 R2 the Data Sources (ODBC) in Control Panel cannot be used as this will create an x64 data source whereas Microsoft Dynamics GP will only work with an x86 data source.

An x86 ODBC connection can be created by using the Data Sources (ODBC) which is located in %windir%\syswow64\odbcad32.exe. You can navigate to it using Windows Explorer or by using the Windows Run command;

Create an x86 ODBC On Windows 2008 R2