Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Jeff Roe]

Over the last few days we have seen several users get an error message in the Sales Transaction window.

The error message states
Illegal address …in script
TRIGGER_SOP_WINDOW_PRE_ACTIVATE

I have attached a screenshot of the full message, has anyone seen this before?

——————————
Jeff Roe
Kele Inc
Bartlett TN
——————————

[Leslie Vail]

Hi,
Do you have any third party products running against the SOP window? I do not recognize that script name. Fields do not have Pre-Activate scripts. Windows have Activate scripts, but not Pre-Activate.
Leslie

——————————
Leslie Vail
Accounting Systems Consulting, Inc.
Dallas TX
——————————
——————————————-

[Jeff Roe]

We do have a number of Customizations and 3rd party modules (i.e. Hawk Mountain, CCH Sales Tax, Nodus Credit Card)

Can you tell is the message likely code or table based?

Thanks

——————————
Jeff Roe
Kele Inc
Bartlett TN
——————————
——————————————-

[David Musgrave]

Hi Jeff

Do you have GP Power Tools installed (Administrator Tools module)?

If so, go to Resource Information and change to Procedures and Functions mode.

Enter the Technical Name: TRIGGER_SOP_Window_PRE_ACTIVATE

And it will identify the product that contains this script, press Search Again to look for other products.

I would say that another way to narrow this down is to look which products have alternate windows for the SOP_Entry (Sales Transaction Entry) window.

Looks like this code is not checking the alternate window is in use and crashing because a different version of the window is in use.

Look at the Alternate Modified Forms and Reports ID window to see who has alternates for this window.

David

——————————
David Musgrave MVP, GPUG All-Star

Managing Director
Winthrop Development Consultants

Perth, Western Australia

http://www.winthropdc.com
——————————
——————————————-

[Jeff Roe]

Think we found the provider module with that script.

Appears to be in Credit Card Advantage -> System -> Global (Script Explorer).

Since it only has happened twice and with two different users, it’s not likely a permissions issue.

We have been using this module for at least 6 months so it’s not a common occurrence.

All users are accessing a terminal server farm and all servers have the identical GP environment.

Thanks

——————————
Jeff Roe
Kele Inc
Bartlett TN
——————————
——————————————-

[David Joosten]

This is most likely a user permission or the incorrect dictionaries are loaded on the user machine/session  against a modified or custom window for which custom code has been written. This means the code that is trying to execute can not find a reference to the object in the current user window. You need to check that the user security and user installation is the same for the alternate windows as a user that is working.

——————————
David Joosten
Enterprise Architect
Premier (Pty) Ltd
Waterfall City
——————————
——————————————-