web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Dexterity Crashes with...
Microsoft Dynamics GP (Archived)

Dexterity Crashes with Event ID 1000 when compiling a new global procedure

(0) ShareShare
ReportReport
Posted on by Community Member

I was trying to add a new global procedure to a Dexterity application and whenever I compile it, Dex crashes with this error:

Faulting application name: Dex.exe, version: 12.0.311.0, time stamp: 0x5363aedf
Faulting module name: Dex.exe, version: 12.0.311.0, time stamp: 0x5363aedf
Exception code: 0xc0000005
Fault offset: 0x002d3dba
Faulting process id: 0x2d20
Faulting application start time: 0x01d1bd042814806c
Faulting application path: C:\Dex\Dex2013R2\Dex.exe
Faulting module path: C:\Dex\Dex2013R2\Dex.exe
Report Id: 47e8bcdd-7efe-455e-abe6-3a518766d0a0
Faulting package full name:
Faulting package-relative application ID:

What's odd is that the exact same thing happens in Dex 2013 and 2015 on two completely different computers.  The procedure compiles fine if I have only parameter and local variable declarations, but as soon as I add a line of functioning code, boom.  Even tried recreating the developer dictionary by updating a brand new GP dictionary from SCC. I've had this happen before and resolved it, but can't recall how.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Figured out the issue.  The first line of code started a "for" loop referencing a local variable that was not declared.  Once I declared the local variable, the script compiled without crashing. Of course, the compiler should have simply given me an error, but I guess with a new procedure, it has problems with this.

  • Almas Mahfooz Profile Picture
    Almas Mahfooz 11,009 User Group Leader on at

    Can you share your procedure code, if you want send it me almasmahfooz@hotmail.com

  • Community Member Profile Picture
    Community Member on at

    Anything, even simple code will crash it if you reference an undeclared local variable.  Here's an example of something that will crash Dexterity:

    NewProc

    inout boolean bYesNo;

    for i = 1 to 2 do

    bYesNo = true;

    end for;

    If you instead add the following before the "for" loop starts, it'll compile without a problem:

    local integer i;

    Instead of crashing, Dexterity should give a compiler error for the undeclared integer.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans