Microsoft Dynamics GP Developing for Dynamics GP
A blog dedicated to the Microsoft Dynamics GP Developer & Consultant community
 
Welcome to MSDN Blogs Sign in | Join | Help

Developing for Dynamics GP

by David Musgrave (Australia) and the Microsoft Dynamics GP Developer Support Team (USA)

News

  • Please use the Blog Feedback? - Contact Us link at the top of the page to email questions relating to the blog itself.

    If you wish to ask a technical question, please use the links below to ask on the Newsgroups. If you ask on the Newsgroups, others in the community can respond and the answers are available for everyone in the future.

    Please do not use comments on pages and posts to ask questions unrelated to the topic on that page or post.



    Dates of Interest:

    11-Jul-2008: Blog Created by David Musgrave.
    03-Oct-2008: Syndicated to the Dynamics Communities.
    10-Oct-2008: First Post by Scott Stephenson.
    04-Nov-2008: First Post by Dave Dusek.
    11-Nov-2008: First Post by Beth Gardner.
    28-Nov-2008: First Post by Chris Roehrich.
    30-Dec-2008: First Post by Patrick Roth.
    24-Feb-2009: First Post by Greg Willson.
    22-Apr-2009: First Post by David Clauson.
    04-May-2009: First Post by Ryan Wigestrand.
    19-Jun-2009: First Post by Dawn Langlie.
    03-Jul-2009: First Post by Emily Halvorson.
    23-Sep-2009: Created Twitter account with blog feed.
    20-Nov-2009: First Post by Alice Newsam.



    WorldMaps Statistics since
    24-Feb-2009:




    Click for WorldMaps Stumbler



    Translator Tool:




    Social Networking & Syndication

    Follow David Musgrave and the blog on:

    David Musgrave on Twitter

    David Musgrave on LinkedIn

    This blog at Dynamics Communities


    Disclaimer

    This blog is provided "AS IS" with no warranties, and confers no rights.

    The links in this blog may lead to third-party Web sites. Microsoft provides third-party resources to help you find customer service and/or technical support resources. Information at these sites may change without notice. Microsoft is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.

Contents

Favourite Posts

Blog Links

Newsgroups Links

Resources Links

Running dag.exe on 9.0 Dynamics forms dictionary fails with runtime error at 86% complete

Patrick Roth - Click for blog homepageA few months ago, a partner was attempting to create an Application.Dynamics.ModifiedForms.dll using the Dictionary Application Generator (dag.exe) against his 9.0 SP4 Dynamics forms dictionary.

This failed for him.  Trying to determine if it was a "forms dictionary issue" or not, he renamed his Application.Dynamics.dll as a test and attempted to generate a new one using Dag.exe.  This also failed in the same manner but at a different spot.

The partner logged a support incident that I took and after making sure that dag.exe ran successfully on my 9.0 SP2 system, I updated to 9.0 SP4 as well.  After doing so, I found I had the exact same issue.

So that was nice - at least I could replicate the issue.

What we found was that generating the modified forms assembly using the command line:

Dag.exe 0 /F

The Dag.exe would fail with a Microsoft Visual C++ runtime error at 86% complete.

If we renamed the Application.Dynamics.dll and attempted to generate it again with the command line:

Dag.exe 0 /M

Then the Dag.exe would fail with a Microsoft Visual C++ runtime error at 17% complete.

After spending a good time debugging this in Visual Studio 2005, I was able to determine what was happening.

Sometime after 9.0 SP2, two procedures were introduced into the Dynamics.dic.  These procedures used parameters that included two new fields.  Unfortunately however, the fields themselves were not included in the update cnk file.

While not causing any issues for the GP client - as I believe the new procedures would only be used for Latin American customers - the Dag.exe was finding the procedures and attempting to locate the new fields in the dictionary.  As they didn't exist, the runtime crashes on the first one it couldn't find.

While very unusual for support to do, the workaround was for me to make a cnk file that contains the missing fields that would merge into the Dynamics.dic.  After giving the cnk file to the partner and merging it into his Dynamics.dic, his dag.exe would run to completion successfully.

This issue is scheduled to be fixed in the next release - probably a tax release coming up.  In the meantime, if you run into this issue log a support case and mention that you need the MBSGP_53972.zip file to resolve this issue.  Also make sure you give your exact dictionary version 9.0.352 or 9.0.371 as the cnk file will alter your Dynamics.dic and they need to be the same version.  As this is a bug, you won't be charged for the case.

Hope this helps,
Patrick
Developer Support

Posted: Friday, November 27, 2009 9:00 AM by Patrick Roth [MSFT]

Comments

No Comments

Leave a Comment

(required) 

(required) 

(optional)

(required) 

  
Enter Code Here: Required

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker