web
You’re offline. This is a read only version of the page.
close
Skip to main content
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 SRMESC 35

We're receiving an unhandled script exception: Index 0 of array 'Federal Wage Array' is out of range in script 'UPR_CHK_CALC_Process_Record'. Script terminated.  EXCEPTION_CLASS_SCRIPT_OUT_OF_RANGE  Script_CMD_LINDEX

The problem occurs when processing Calculating Payroll Checks and throws this error at exactly the same % of processing but will continue to process after acknowledging the error.  After diagnosing, I am lead to believe it's a possible employee setup issue.  We had added new employees and inspected the Pay Codes, Deductions & Benefits all seems right but continues to throw the error.

Any insights would be appreciated.

Thanks,

William

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    Community Member on at
    RE: Unhandled Script Exception

    Hi,

    Below is a list of possible solutions:

    Note which employee record the calculate checks process was processing when it ended.

    1. Verify a frequency is not missing on a deduction or benefit. Go to Cards | Payroll | Benefit or Deduction and check the frequency for each code set up for the employee. If the frequency information is missing for any of the codes, enter the correct frequency.

    2. Verify there is a pay period specified for the pay code in the employee pay code maintenance window, Cards | Payroll | Pay code.

    KB Article : 849410  

    vkbexternal.partners.extranet.microsoft.com/.../ViewContent.aspx

    Hope this helps,

    Regards,

    Santosh G

  • SRMESC Profile Picture
    SRMESC 35 on at
    RE: Unhandled Script Exception

    Thank you for your information,

    I had located the problem yesterday and you are correct, it was a NULL field in the pay period frequency on two employees.  Don't know how a BLANK / NULL entry got placed into a field setup for list selected validation which doesn't allow Null/Blank entries.

    Perhaps a SQL database cleanup and inspection is in order to optimize the DB.  Any good suggestions.

    Thanks Much,

    Will

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans