The System Requirements for Microsoft Dynamics GP 2015 are now available from CustomerSource (login required).
The stand out items for me is that support has been dropped for several older versions of Windows, SQL Server and Office:
- Windows XP all editions
- Windows Vista all editions
- Windows Server 2003 all editions
- SQL Server:
- 2008 all editions (including R2)
The only surprise on the above list is that some of the software listed as no longer supported was also listed as no longer supported with Dynamics GP 2013; in fact only SQL Server 2008 is new to the list.
Apart from the above retired software, the recommendations look pretty much the same as Dynamics GP 2013; Windows 8.1 and SQL Server 2014 have been added as supported.
After doing a little work linking databases together for a report, I ended up creating a script to be used within a stored procedure to quickly and easily re-add the linked server (which is required after a reboot of the SQL Server.
To run the script, change the three highlighted fields (server-name, username and password) and click Execute in SQL Server Management Studio:
DECLARE @Server AS VARCHAR(50)
DECLARE @Username AS VARCHAR(50)
DECLARE @Password AS VARCHAR(50)
SET @Server = 'server-name'
SET @Username = 'username'
SET @Password = 'password'
CREATE TABLE #linkedservers
INSERT INTO #linkedservers
IF (SELECT COUNT(*) FROM #linkedservers WHERE SRV_NAME = @Server) < 1
EXEC sp_addlinkedserver @Server, 'SQL Server'
DROP TABLE #linkedservers
EXEC sp_addlinkedsrvlogin @Server, 'false', NULL, @Username, @Password
A while ago I was setting up SQL Server for a test system, I obviously wasn’t paying enough attention because when I tried to launch Microsoft Dynamics GP Utilities I received the below error:
Microsoft Dynamics GP Utilities: This login failed. Attempt to log in again or contact your system administrator
When Reporting Tools Setup is used t deploy the reports to SQL Server Reporing Services an error be produced if the default configuration of SSRS has not been amended (I thought I’d blogged about this error before, but when trying to find it to send the post to someone I couldn’t find it).
The error produced is the following:
Microsoft Dynamics GP – The deployment has exceeded the maximum request length allowed by the target server. Set maxRequestLength=”20690″ in the web.config file and try deploying again.
Victoria Yudin, the longest serving Microsoft(R) Most Valuable Professional for Microsoft Dynamics GP, has just released Microsoft Dynamics GP 2013 Implementation via Packt Publishing.
This is an update of the Microsoft Dynamics GP 2010 book she wrote a few years ago, which has been updated for Microsoft Dynamics GP 2013:
In brief this book covers:
- Plan, install, and implement Microsoft Dynamics GP 2013 with real-world advice from a Microsoft Dynamics GP MVP
- Learn how to set up the core modules in Microsoft Dynamics GP effectively following detailed, step-by-step instructions
- Discover additional tools and resources available for your Dynamics GP
We upgraded a client from Microsoft Dynamics GP 9 to Microsoft Dynamics GP 2010 recently, and the first time they tried to run the VAT 100 report they received a number of errors:
Microsoft Dynamics GP – An error occurred executing SQL statements.
I’m currently involved with a couple of projects where we have needed to migrate databases from one SQL Server to another and needed to do so more than once.
Prior to the first copy, we used a script to load the users into SQL Server and then restored the databases and had no problems.
Later on, after changing some of the permissions to databases we had need to remigrate some of them over. However, we found that users could not access some databases and when we tried to add them we got the following error;
Msg 15023, Level 16, State 1, Line 1
User, group, or role 'pidev' already exists in the current database.
It was looking very like we would need to go through each database and remove access and then regrant it all; a labourious process. A quick Google found me a page from Julian Kuiters which introduced me to the ALTER USER command. The following code will run against the selected database and tie together the SQL Server user with the user in the database without any other work;
ALTER USER pidev WITH LOGIN = pidev
The first highlighted element needs to be changed to the database you want to update the user on and then the following two entries are the usernames which need to be linked (these should be set to the same value).
I was in the process of building a virtual machine to do a test upgrade of Microsoft Dynamics GP for a client when I got this error message;
I know things go wrong and I don’t mind error messages telling me that they have gone wrong; in fact, a good error with details is a good thing to see when there is a problem. But I do mind when the error message doesn’t actually tell me anything (one company I worked with produced error code 0 for every single error which everyone hated but it took about five years before the error handler got fixed to return the real error).
I did a little digging and it turned out to be a nice easy fix; when the VM was created the HDD space allocated hadn’t been big enough for the size of the databases being restored to it. I added a new (larger) virtual HDD to the VM and was able to restore the databases without further error.
I covered a wide variety of topics mainly around GP and related products as well as a few around SQL Server but I’ve not actually done a post on the “correct” installation process of installing SQL Server for use with Microsoft Dynamics GP (I highlight correct as I’m sure some people will disagree with how I am doing the installation).
With the release of Microsoft SQL Server 2012 I thought it was time to rectify this. I am going to be installing the Enterprise Edition of Microsoft SQL Server 2012 but the process is the same for each of the versions. The install is being done as I usually do them on a VM for testing/demo purposes; I would pay more attention to security and the location of the log and data folders if this were being done on a production machine.
To install SQL Server, run the setup utility on the installation media which will open the SQL Server Installation Center;
Microsoft have started the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The thirty first feature they’ve announced is Named System Database.
In all versions of Microsoft Dynamics GP so far, the System database has been called DYNAMICS and could not be changed. This meant only a single instance (System and Company databases) of Microsoft Dynamics GP could be installed into an instance of SQL Server.
In Microsoft Dynamics GP 2013 this restriction has been removed in a new deployment. From this version onwards, the System database no longer needs to be called DYNAMICS but can be named during the installation/deployment process.