Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
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 Microsoft Employee

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

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Dexterity Crashes with Event ID 1000 when compiling a new global procedure

    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.

  • Almas Mahfooz Profile Picture
    Almas Mahfooz 11,003 User Group Leader on at
    RE: Dexterity Crashes with Event ID 1000 when compiling a new global procedure

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

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Dexterity Crashes with Event ID 1000 when compiling a new global procedure

    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.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans