Unhandled script exception: Illegal address for field '[Not Found]' in script 'Unregister_Triggers'

If you have recently upgraded to Microsoft Dynamics GP 2010 R2, a few days aback, a partner reported receiving the following errors when returning from Report Writer:

Unhandled script exception:
Illegal address for field '[Not Found]' in script 'Unregister_Triggers'. Script terminated.

EXCEPTION_CLASS_SCRIPT_ADDRESSING
SCRIPT_CMD_LOAD_ATSI7



Unhandled script exception: Illegal address for field '[Not Found]'

The error is followed closely by:

Unhandled script exception:
Object has no reference.

EXCEPTION_CLASS_SCRIPT_BAD_PARAM
SCRIPT_CMD_DEREF_TABLE

Upon review, the error appears to be an issue with Extender and also happens when returning from Modifier. This issue has been written up as a bug and is scheduled to be fixed. To workaround the issue, exit Microsoft Dynamics GP 2010 R2 and log back into the system.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Comments

Anonymous said…
MG- Thank you, that one was driving me nuts, and I had it listed to be looked at this week.
Thanks for saving me an hour or so!
The other MG (the west coast one)
Mike
May 18, 2011 at 1:55 PM
Mariano Gomez said…
Hey Mike! Good to see you around here! Glad I could help.

MG.-
Mariano Gomez, MVP
May 18, 2011 at 5:55 PM
Anonymous said…
Had been using the R2 'patch' without the error. In order to activate some of the other new features in R2 (Effective Date on Taxes) uninstalled GP2010 and reinstalled from the DVD when this problem popped up.

Resolved for now by removing Extender from set file.

Thanks for the post!

Jalene Marler
onza solutions/besttechsnw
May 31, 2011 at 4:37 PM
Terry Blaser said…
Just to add to this issue...When you click OK to the last error message GP will open up, however, the current user will lose all their home page shortcuts - permanently. If you completely exit out of Modifier/Report Writer without returning to GP then the shortcuts will not be removed.
October 24, 2011 at 4:35 PM
Mildred said…
Mariano, nice to meet you.

This error is presented in 2015R2 version in the Transaction Receipts Receipt window.
The customer does not have Extender installed nor third party products.
Do you have any idea what it could be?

Thank you,
Mildred Herrera
March 9, 2017 at 8:31 AM
Mariano Gomez said…
Mildred,

Usually when I see this error with standard GP windows, it most likely has to do with an invalid forms dictionary (forms.dic) or a missing customization.
March 10, 2017 at 10:20 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more