Author Archive: David Musgrave
It is time to release a new build of the Support Debugging Tool for Microsoft Dynamics GP for versions 10.0, GP 2010 (v11.0) and GP 2013 (v12.0). Build 19 primarily improves support for Microsoft Dynamics GP 2013 R2 as well as including some fixes and enhancements to existing features
How to Fix a Setup File is from a later version Error from the Support Debugging Tool when doing a Test Upgrade
This post revisits the issue previously discussed in the blog post: How to Fix a Setup File is from a later version Error from the Support Debugging Tool . The issue is that you receive the error message below from the Support Debugging Tool just after logging into Microsoft Dynamics GP: Setup File is from a later version (##.##.####) than the version (##.##.####) of the Support Debugging Tool on this workstation. Please check with your administrator if the correct location for the Debugger.xml setup file is being used
In my last post: Backup regimes and synchronizing folders across your network , I discussed my method of backing up data from four folders off the root of the drive across my network and how I use the free SyncToy 2.1 tool from Microsoft. So in this post I wanted to take it to the next level. Introducing the Cloud Here is the next bit of the puzzle…
On my computers at home I have a backup and synchronization regime to ensure that each computer has access to the files I want (even when offline) and that there is no chance of losing any data in the event of a disaster. In this post, I will explain my regime and some of the tools and tricks I have learnt. While I am sure others will have their own systems and might not agree with what I am doing.
Last week, I resolved a rather bizarre case for a customer. The Situation Each time the customer’s SQL Server was restarted for whatever reason, only the ‘sa’ user was able to log into Microsoft Dynamics GP. Once the ‘sa’ user had logged into Microsoft Dynamics GP at least once, then all the other “normal” users could log in and everything was fine until the next time the SQL Server was restarted.