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) / Unhandled script excep...
Microsoft Dynamics GP (Archived)

Unhandled script exception

(0) ShareShare
ReportReport
Posted on by Vincent claeys 70

We began experiencing problems this morning with Dynamics Great Plains. While attempting to print a Purchase Order Entry we are prompted with the following exception:

 

Unhandled script exception:

Invalid year '100' in date function. Script terminated.

 

EXCEPTION_CLASS_SCRIPT_OUT_OF_RANGE

SCRIPT_CMD_SETDATE

 

I believe Great Plains is parsing the date incorrectly using the day and month (10-01) as the year however I'm clueless as to what I should do to solve the problem.

*This post is locked for comments

I have the same question (0)
  • Richard Whaley Profile Picture
    Richard Whaley 25,195 on at

    Does this happen with every purchase order?  Does this happen at every workstation?

    If it only happens with one PO, try to edit the PO, change the dates and reprint.

    If it only happens on one workstation and others can print, try reinstalling the GP client.

  • Rashid Farooq Profile Picture
    Rashid Farooq 1,000 on at

    Adding more in Richard's reply, if error raised on every workstations then change the User Date and also check regional setting (Date Format) and system date too.

     

  • Vincent claeys Profile Picture
    Vincent claeys 70 on at

    I tried it this morning using another workstation and got the same error. Then I tried it with our terminal server and I got an error again but a different one this time.

    Unhandled script execution:

    Invalid Product ID 2418.

     

    EXCEPTION_CLASS_SCRIPT_OUT_OF_RANGE

    SCRIPT_CMD_CALL

     

    I've also added a trace to our SQL Server using Profiler and managed to pull out the following error code which seems to be causing the first error:

    Error: 207, Severity: 16, State: 3

  • Community Member Profile Picture
    Community Member on at

    When did you get this error message exactly? At what point in the PO entry pocess.

    Did you get any error messages when you logged in to GP?

    Can you check the dynamics.set file on your terminal server install and look for a product code 2418?

    Have you and customised add on software?

     

     

  • Vincent claeys Profile Picture
    Vincent claeys 70 on at

     This error occurs when I attempt to print the PO entry.

    When logging into Great Plains I get no errors, however every time I open Great Plains on the terminal server I get the following warning:

    The Microsoft_Dynamics_GP.vba project references some objects that cannot be found. These objects are listed in the file C:\Program Files\Microsoft Dynamics\GP\Dynamics.txt

    Looking at the dynamics.set on the terminal server revealed no trace of product code 2418.

    As for add-on software, I personally  haven't developped any however I know we are using 2 add-ons. One is Nolan SOP Import and the other is Myridas Setup from Trinity Computer Services.

  • Vincent claeys Profile Picture
    Vincent claeys 70 on at

     I believe I have found the source of the problem.

    The product code 2418 which caused the error on the terminal server was actually set to "Nolan SOP Import" on the other workstations.

    I'm guessing this 3rd party software parses the date using the "MM/dd/yyyy" format while the workstation's regional settings were set to "yyyy/MM/dd".

    Switching the date format to "MM/dd/yyyy" on the user's workstation seems to have resolved the issue.

    Many thanks to all of you, your help is very much appreciated. :)

  • Community Member Profile Picture
    Community Member on at

    Thats great. Well done.

  • Community Member Profile Picture
    Community Member on at

    The typical culprit is a third party add-on assuming a certain regional setting. There are ways for the developer to ensure that that doesn't happen and most of them would entail adding preliminary code before the setdate command. You may want to contact the developer of the add-on and let them know of the issue to help them improve their product or at least add the regional setting as a requirement in their documentation.

  • Richard Whaley Profile Picture
    Richard Whaley 25,195 on at

    Have you notified Nolon?  Their product should react to the proper data format setting but it sounds like it does not.  They need to know this so they can fix the issue.

  • Vincent claeys Profile Picture
    Vincent claeys 70 on at

     Nolan has been notified. I'm still waiting for a response on their part.

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
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans