Microsoft Dynamics Bite Sized Webinars – November 2014

This article contains the list of Microsoft Dynamics Bite Sized webinars which we have scheduled EXCLUSIVELY for partners for November 2014, so that partners can get benefited from these workshops. If you are a partner of Microsoft, please feel free to register for these sessions and improve your readiness on the latest and super cool technologies. In case you are a customer, you can get in touch with your partner and they would be able to re-deliver these sessions to you.

See original article:
Microsoft Dynamics Bite Sized Webinars – November 2014

September 17, 2014 · Sivakumar V · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 130

The Mystery Behind Paid Transaction Removal | Dynamics GP Blog

What is the Paid Transaction Removal function in Dynamics GP and why should it be used? Over the years this has been a question that is asked often by GP customers. This Sales Routine title is daunting to say the least!

The Mystery Behind Paid Transaction Removal | Dynamics GP Blog

September 17, 2014 · tidestone · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 125

How to Fix a Setup File is from a later version Error from the Support Debugging Tool when doing a Test Upgrade

David Meego - Click for blog homepageThis post revisits the issue previously discussed in the blog post: 

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.


This error occurs when the Support Debugging Tool’s Setup file Debugger.xml has been used with a later version of the tool than the version on the current workstation.

The previous article covered the situation where you are updating the Support Debugging Tool code on a system and had not yet finished installing the update on every workstation. The solution in this case is to complete the updates and ensure that every workstation has the latest build.

However, there is another situation which can cause this error and that is what this article discusses.


I was doing a Test Upgrade and now my Live System has the error 

If running the Support Debugging Tool in the recommended configuration (shared setup file with administrator controlled location), when you first run your Test Upgrade system, that workstation will inherit the shared setup file location. Prior to Build 18, it would update the version information in the Debugger.xml setup file (and also the cache tables in the Debugger folder). Then when the Live system accessed the setup file, it would generate the error as the versions no longer matched.

Note: From Build 18 onwards you will be warned about this situation, see the next section below.


If you are already getting the error. Here are the manual steps to resolving the issue:

  1. On the Test system edit the Dex.ini file to update the following settings.
    Remove MBS_Debug_Path Dex,ini setting to restore the default location of the application’s Data folder.
    Add MBS_Debug_ConfigurationOverride=TRUE setting, to prevent the location from being updated for this workstation. This setting is also available at the bottom of the Dex.ini Configuration window and can be used to prevent the SDT automatically updating any Dex.ini setting for the current workstation.

  2. To fix the Live system we need to restore the version information in the Debugger.xml setup file to its previous value.
    Open the Debugger.xml setup file with notepad.exe and search for “Version”. You can then update the 3 version values to set them back to the version of the Support Debugging Tool actually installed in the Live system.

    eg: 11018

  3. The final step is to force the Debugger.xml setup file to be re-read by removing the cache tables. 
    Locate the Debugger folder in the shared location and remove its contents. There should be 20 or so .dat and .idx files to delete. They will be recreated automatically the next time the Support Debugging Tool reads its data from the Debugger.xml setup file.


How to do a Test Upgrade with the Support Debugging Tool installed

If your build is prior to Build 18, BEFORE running Dynamics GP, please perform the manual step 1 above, to disconnect the Test upgrade system from the recommended configuration. If you don’t then you will need to perform all the manual steps above.

From Build 18 onwards functionality was added to avoid this issue occurring. You should get a series of dialogs (shown below) which will allow you to prevent the overwriting of the file and also remove the current workstation from the recommended configuration.

Click No for Test Upgrade

Click No for current workstation only

Click OK

If you answer the dialogs above incorrectly, you will need to perform the manual steps to resolve the issue.


You might also find this article useful:

Hope this is helpful.


View article:
How to Fix a Setup File is from a later version Error from the Support Debugging Tool when doing a Test Upgrade

September 17, 2014 · David Musgrave · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 140

Management Reporter Error Opening Column Definition | azurecurve

Management Reporter Period 13 Is Not Valid For Company … CRM Perfect Image Email azurecurve View Ian Grieve’s View Ian Grieve’s profile on LinkedIn View azurecurve’s Feed on Twitter MVP Profile View azurecurve’s facebook page View azurecurve’s Google+ View azurecurve’s Summary RSS Feed View azurecurve’s Detailed RSS Feed. Buy My Book. Microsoft Dynamics GP 2013 Cookbook by Ian Grieve and Mark Polino. Search azurecurve …

Originally posted here:
Management Reporter Error Opening Column Definition | azurecurve

September 16, 2014 · Ian Grieve · No Comments
Tags:  · Posted in: Blogs I Follow Total Views: 147

SQL view to verify unposted SOP transaction totals in Dynamics GP

Over the years we have seen a number of situations where a sales transaction total will be calculated incorrectly. It does not happen often and we’ve never been able to reproduce this on demand, so it’s very difficult to track down the cause for this. I have also seen a number of newsgroup posts talking …

Continue reading here:
SQL view to verify unposted SOP transaction totals in Dynamics GP

September 12, 2014 · Victoria Yudin · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 323

Backup regimes and synchronizing folders across your network

David Meego - Click for blog homepageOn 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. I hope you find this information helpful and maybe something in this post will save your data one day.

Note: This system was set up when I was running Winthrop Dexterity Consultants from home and is probably a little over the top. After you lose data a few times, it does not seem over the top anymore.


My Configuration

Basically, I store all my data in 4 folders:

  1. C:Backups
    This folder contains backups of any content created by me that is not a document. For example: Development projects, Exchange/Outlook files, Websites, etc.
  2. C:CD_Temp
    This folder contains all the install files for tools and utilities that I like to use as well as drivers for my machines: Files I want to be able to access, but not created by me.
    Its name is a legacy of the fact that I used to burn each sub folder to a CD, so I could carry it around with me. Now I just carry the files and folders I want on a USB Drive.
  3. C:My Documents
    This is where all my documents are created. I don’t use the default user folders as they cannot be shared so easily across users and machines.
    In Office options, I change the application’s default save folder from C:UsersDavidDocuments to C:My Documents.
  4. C:Media
    This folder has sub folders for Music, Pictures and Videos and contains all my media files. I don’t use the default user folders as they cannot be shared so easily across users and machines.
    I manually add the appropriate folders to the Windows Libraries so the windows apps can find my media.
    Hint: On my Surface Pro tablet, I have added a micro SD card which I use to store the Media folder on. It is drive D: on the machine. However, I created a blank folder C:Media and then using the Disk Manager (Computer Management >> Storage >> Disk Management), I right click on the drive and select Change Drive Letters and Paths and Add the C:Media path to mount drive D: as though it is the C:Media folder.  This is a great way to expand storage on a tablet for files which are write once, read many (WORM) times files. 

Now that you know how I have my data stored, we can discuss how I back it up.


My Hardware 

Each of my computers has an extra drive. In a couple, that is a secondary internal drive and in the others it is a USB external drive. Note that this drive needs to be a separate physical drive and not a partition on the same drive. If it was a partition and the drive failed, you would lose both the original and the backup.

I also have a NAS (Network Attached Storage) drive, which is the central storage and the link between each of the machines on my network. This is a NetGear 4 bay NAS device which currently has two mirrored 2TB Drives in it. With two free bays, I have room to expand when I need it. It you don’t have a NAS, select a machine which is always at home and share the folders so it can become the central link.


My Synchronizing Regime

Using the wonderful SyncToy 2.1 free tool from Microsoft, on each machine I set up synchronization for the four folders (above) between the matching shares on the NAS and to the local extra drive on the machine.

By running SyncToy on each machine every week or so, any changes made on any machine are synchronized up to the NAS and onto the extra drive. To get all machines and drives synchronized normally takes running SyncToy once on every machine to move all changes to the NAS and then running it twice more on each machine to bring the changes from the NAS to the local drive and then from the local drive to the external drive. While this is a manual process, it does not take long.

On one of my machines I have an extra external drive which is also synchronized with SyncToy. This drive is swapped regularly with an identical drive that lives at my Mother-in-law’s house. She backs up her system with a similar SyncToy arrangement I set up for her. This means that my data is offsite and her data is also backed up and offsite. I would highly recommend buying two large external drives so you can set up a swapping arrangement with a good friend or family member.

Using this arrangement, you will never lose much data, even if you have drives fail, machines fail or worse a disaster hits your house.


So here is a summary of the tips:

  • You can add other folders to your Libraries for Music, Pictures, Videos so you are not limited to the default user folders.
  • You can mount flash drive storage so it appears as part of your main C: drive.
  • Backup or synchronize your data to a separate physical drive.
  • Use a central machine or NAS drive to allow all machine to synchronize to a central location.
  • Take a backup offsite. Swap an external drive with a friend or family member.
  • Use SyncToy to only copy the changes made. 


Hope you found this information useful.


Backup regimes and synchronizing folders across your network

September 10, 2014 · David Musgrave · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 280

Tech Tuesday: What is creating these XML files?