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.


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

The error is followed closely by:

Unhandled script exception:
Object has no reference.


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!

Mariano Gomez, MVP
IntellPartners, LLC


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)
Mariano Gomez said…
Hey Mike! Good to see you around here! Glad I could help.

Mariano Gomez, MVP
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
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.
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
Mariano Gomez said…

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.

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

#MSDYNGP: Named Printers and Redirected Printers in RDP environments

Integration Manager 10 INI settings