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
Posted in Dynamics, GP, Integration Manager, Microsoft, Packt Publishing, Review, SQL Server
Tagged Distributions, Financials, GP, Implementation, Integration Manager, Microsoft, Microsoft Dynamics, Microsoft Dynamics GP 2013, Microsoft SQL Server, MVP, Packt Publishing, Review, Victoria Yudin
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.
Posted in Dynamics, GP, Microsoft
Tagged Microsoft, Microsoft Dynamics, Microsoft Dynamics GP 2010, Microsoft SQL Server, Mircosoft Dynamics GP, Reports, SQL Collation, VAT 100, Vat Daybook
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.
Posted in Dynamics, GP, Microsoft, SQL Server
Tagged GP, Installation, Installation & Configuration, MDGP 2013 Feature of the Day, Microsoft, Microsoft Dynamics, Microsoft Dynamics GP 2013, Microsoft SQL Server
I typically like to see rollups come out as they tend to fix bugs and add new features but yesterday I advised a customer to install rollup 1 for Management Reporter.
Hopefully, I can catch them first thing in the morning and get them onto rollup 2 instead, of which Sivakumar has just announced the release on the Dynamics Partner Technical Services team blog.
Rollup 2 can be downloaded from here (CustomerSource or PartnerSource login required).
This one adds support for SQL Server 2012 as well as other bug fixes and enhancements to the currency translation.
Posted in Dynamics, Management Reporter, Microsoft, SQL Server, SQL Server 2012
Tagged Installation, Installation & Configuration, Management Reporter, Management Reporter 2012, Microsoft, Microsoft Dynamics, Microsoft SQL Server, Microsoft SQL Server 2012, Multicurrency, Reporting, Rollups
One of the points I make (repeatedly until I see a confirmation they’ve done so) to clients when implementing Microsoft Dynamics GP is that they need to make sure that a maintenance backup of the SQL databases and other resources are being made.
In some cases the maintenance backup is a once a night job, other clients have had one done every twelve hours with log backups made every hour. As long as a regular backup is being made I’m happy and stop nagging them.
Posted in Dynamics, Excel Reports, FRx, GP, Integration Manager, Microsoft, Reporting Services Reports, SQL Server
Tagged Backups, Customisations, FRx, GP, Integration Manager, Management Reporter, Microsoft, Microsoft Dynamics, Microsoft SQL Server
I was doing some testing to compare the SSRS Trial Balance against the standard report version but ran into a problem straight away when I found the SSRS version returned no data.
A quick search online found me this post SSRS: GL Trial Balance Summary report returns no data – Follow Up by Mariano Gomez where he discussed the exact problem I had encountered.
As Mariano says this has been fixed in the upcoming SP3 but for now there is a Knowledge Base article covering a workaround which is to alter the stored procedure (seeglPrintSRSTrialBalance) which is used for returning the data: GL Trial Balance SRS Reports return no data using Microsoft Dynamics GP.
Posted in Dynamics, GP, Microsoft
Tagged Financials, General Ledger, Microsoft, Microsoft Dynamics, Microsoft Dynamics GP 2010, Microsoft SQL Server, Microsoft SQL Server 2008 R2, Reporting, Reports, SSRS, TSQL
I was doing some work with a custom table yesterday and at one point needed to make a change to the table layout via SQL Server Management Studio. However, when I tried, I got the below error message;