Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

Can't Post Checks after Year End update in GP 2010

Posted on by Microsoft Employee

After year end update when we go to post a check we get an error: "A save operation on table 'UPR_Check_Hist' (45)". Under more info it states: "The SELECT permission was denied on the object 'GSEEAddressHistoryChecksums', database 'ABC, Schema 'dbo'". If we click OK the check is generated but if we go into checkbook register inquiry it states "Document no longer exists in originating module". I have tried running Gant.sql, no luck. If we login as sa everything runs fine so obviously this is a permissions issue. Has anyone run into this??

*This post is locked for comments

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Can't Post Checks after Year End update in GP 2010

    Yes, as has been reported below this error can definitely be caused by a bad annual Greenshades update that was available late Thursday December 26th. The update was corrected to work for nearly all clients late Friday and then was completely rolled back Monday December 30th after we found a small percentage of clients were still experiencing issues. If you updated the Greenshades Center during this time and are now receiving this error message then it is our issue. If you have updated the Greenshades Center during that time and have not yet run payroll since updating then please re-run the Greenshades Center and apply the latest updates (you should have an email from us as well).

    To date we have seen an impact to a few dozen clients. If you are one such client then please contact us at 1-888-255-3815x1 or support@greenshades.com. You may call tomorrow: Normally January 1st is a holiday for us but we are staffing a group of support and development personnel for anyone who is having this issue and may want to resolve it immediately instead of waiting until the 2nd.

    To add a little more detail: our incorrect patch shows the referenced error message during a payrun and disallows the check header records from being added to Dynamics (UPR30100). The payroll builds and calculates, checks may be printed, most of the post process commits, the GL is updated, employees are paid, however the check headers are not created which means the checks simply do not show up on the payroll inquiry report and other screens.  We have a few different ways of addressing this, and are capable of rebuilding those check header records for most clients (using the utility that has been mentioned below), at which point they will suddenly be visible to Dynamics once more. We are working hard to get each impacted client back up and running as soon as possible after they contact us.

    Thanks to Monroe for posting here; one of our clients just alerted us to this post a few hours ago and we rushed over to comment here to help get the word out. We did email our client list but we don't always have the latest/correct emails for everyone.

  • Verified answer
    David Buzzell Profile Picture
    David Buzzell 30 on at
    RE: Can't Post Checks after Year End update in GP 2010

    Yes, our resolution was also Greenshades.  We went back to a backup - prior to running payroll on the affected companies.  Reapplied the Greenshades Yearend update (yes there was a new fix to resolve an issue), redid payroll and it worked.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Can't Post Checks after Year End update in GP 2010

    This is a greenshades issue. It seems to be a little different with each case but greenshades support will be able to help. In our case they had to drop the trigger in question.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Can't Post Checks after Year End update in GP 2010

    This is a confirmed issue for users of Greenshades Software. Please send an email to support@Greenshades.com. They have a utility to repair the payroll check history tables.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Can't Post Checks after Year End update in GP 2010

    This is beginning to look like an issue. The trigger message was the original message and we also noticed the checks never made it into history.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Can't Post Checks after Year End update in GP 2010

    I too am getting this error - on 2 of our 6 payroll databases.  Under more detail we are getting "An error was raised during trigger execution.  The batch has been aborted and the user transaction, if any has been rolled back."  The checks print, but are not in check history.

    Any input would be appreciated.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Can't Post Checks after Year End update in GP 2010

    Did you get resolution for this?  I know someone else reporting the issue.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans