web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Dynamics GP 10 Crash During Payroll Posting Process

(0) ShareShare
ReportReport
Posted on by 470

Our company processes payroll for our 2,000+ employees weekly.  We recently had a crash during the posting and report printing process (after the paychecks had been generated).  If I understand correctly, GP does not have a reliable procedure in place such that the system can pick up where it left off in the posting process.  We restored from last night's backup and started the day over again for all modules, all departments and had to re-create all work for the day.  Please confirm if this is the only acceptable 'best practice' for recovering from a problem like this during the posting of a Payroll batch posting failure.  Regardless of the cause of the problem, this is an unacceptible recovery model.  I may be missing some recovery procedures pertaining to payroll.  When this type problem occurred in the past, whatever procedure we followed resulting in incorrect W2s, etc.

Your feedback is appreciated!

*This post is locked for comments

I have the same question (0)
  • Richard Wheeler Profile Picture
    75,850 Moderator on at

    You should this this KB article. support.microsoft.com/.../851664

    If you can I would want to restore both the company database and the DYNAMICS database. There really is no way to separate modules from each other plus there is no way in telling where in the posting process the breakdown occurred. Given that it has now been days since this occurred each day the goes by means just that much more work that has to be made up.  I would try creating a test company and then copy the production database over to the test and then run check links on payroll and GL. Maybe you will get lucky. At least by doing this in a test company you will know how much hot water you are in. Were you just about to post when the system crashed or was it the posting of the payroll that caused the crash?

  • Jonathan Herman Profile Picture
    on at

     Good Afternoon Jeff,

     

    I am sorry to hear that you have experienced an interruption during your payroll posting process.

     

    As it has already been mentioned, when an interruption happens during a payroll posting process, you need to verify where the interruption had occurred.  Here are some areas you can look to verify what had been updated correctly:

     

    You can run the following select SQL Statements:

     

    select * from UPR30100 where AUCTRLCD='XX' --| Payroll Check History

    select * from UPR30200 where AUCTRLCD='XX' --| Payroll Tax Liability

    select * from UPR30300 where AUCTRLCD='XX' --| Payroll Transaction History

    select * from UPR30400 where AUCTRLCD='XX' --| Payroll Distribution History Header

    select * from UPR30401 where AUCTRLCD='XX' --| Payroll Distribution History Detail

    select * from CM20200 where AUDITTRAIL='XX' --| Bank Rec - CM Transaction

    select * from GL20000 where ORGNTSRC ='XX' --| General Ledger - Year-to-Date Transaction Open

     

    Please Note: Replace the XX with the audit trail code associated to the payroll run

     

    Once you have determined the extent of the interruption, you do have a couple of option to recover from an interrupted pay run:

     

    Option 1:  Restore from a SQL backup your company and dynamics data base.  As Richard has stated, if you restore your company database, it is recommended that you restore your Dynamics database as well.  The Dynamics Database does get updated by specific modules.

     

    Option 2:  If restoring from a backup is not an option, there is a way you can remove the entire pay run in question from the tables based off the audit trail code.  Correct the employee’s summary information and associated payroll reports (ex. period end reports), along with correcting any sub-module that was affected by the pay run.

     

    We recommend opening a support case to have a support engineer assist you with determining the extent of the interruption and help you decide what the best plan of action to resolve your issue.

     

    Thank you for your time Jeff and have a wonderful day.

     


    Best regards,

    Jonathan Herman
    Partner Online Technical Community
    -----------------------------------------------------------------------------------------
    We hope you get value from our new forums platform! Tell us what you think:
    http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
    ------------------------------------------------------------------------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights

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…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans