Ramblings of a Dynamics GP Consultant
Earlier 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'.](http://www.azurecurve.co.uk/images/posts/2012/04/PSTL_Registration_Error/PSTL_Registration_Error_1.png "Microsoft Dynamics GP - Unhandled script exception: [Microsoft][SQL Server Native Client 10.0][SQL Server]Could not find stored procedure 'PI.dbo.smChangeAccountIndex2'.")
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
I’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;
I 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;
I 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
When 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;
