When you select a batch in the Build Payroll Checks window in Microsoft Dynamics GP, you may receive one of the following error messages:
Error message 1
Error - "Open operation on UPR_Temp_Post2 has incorrect record length"
Error message 2
Error - "Remove Range Operation on Table ddDeposits has caused known error 2"
Error message 3
Error - "Batches with zero transactions cannot be marked"
Error message 4
Error - "Another user is performing a check run"
Error message 5
Error - "UPR_Work_Post failed accessing SQL data"
Error message 6
Error - "The employee record cannot be inactivated or deleted Pay run is in progress for this employee"
Error message 7
Error - "Checks cannot be calculated. Errors were found."
Error message 8
Error - "You cannot void a check. A computer check run is in process."
Error message 9
Error - "You cannot edit a batch marked for posting"
Error message 10
Error - "Batch is marked for posting and cannot be edited."
Additionally, an Open Operation error, a Get/Change error, or a Save Operation error may occur on one of the following files to indicate that the Payroll batch is stuck:
This problem may occur if the payroll work tables have not been cleared. The payroll work tables must be cleared to release the batch.
Note Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs
To resolve this problem, follow these steps:
Step 1: Delete records in Payroll work tables
Follow one of the options below to delete the activity from the payroll work tables. To have us delete records for you, go to the Option 1: "Fix it for me" section. To delete records yourself, go to the Option 2: "Let me fix it myself" section.
Option #1: Fix it for me
To clea the payroll work temp tables automatically, have all users exit Microsoft Dynamics GP, and then click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Option #2: Let me fix it myself
To clear the payroll work tables yourself, follow these steps:
Open Microsoft SQL Server using the appropriate method below:
If you use Microsoft SQL Server 2008, start SQL Server Management Studio. To do this, click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
If you use Microsoft SQL Server 2005, start SQL Server Management Studio. To do this, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
If you use Microsoft SQL Server 2000, start SQL Query Analyzer. To do this, click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.
Run delete statements against the company database.
Note The first two lines in the script delete the contents of the activity files in the Dynamics database. The other lines delete the contents of the work files and the activity files in the Company database.
Delete DYNAMICS..UPR10300 Delete DYNAMICS..UPR10304 Delete UPR10200 Delete UPR10201 Delete UPR10202 Delete UPR10203 Delete UPR10204 Delete UPR10205 Delete UPR10206 Delete UPR10207 Delete UPR10208 Delete UPR10209 Delete UPR10213 Delete UPR10301 Delete UPR19900 Delete UPR19901
If you use Direct Deposit, run this delete statement for Direct Deposit Work table:
Delete DD10100 --(Direct Deposit Employee Deposit Work)
Step 2: Delete temporary files
To delete temporary files, open Windows Explorer, and then click the Temporary directory. The Temporary directory has the following path:
In the directory, delete the files that begin with TNT. Then, delete the files that have a .tmp file name extension.
Step 3: Perform Check Links
Check Links will check the linking of the data between the tables to ensure data integrity. To do this, follow these steps:
Open the check Links window. In Microsoft Dynamics GP click Microsoft Dynamics GP, click Maintenance, and then click Check Links.
In the Series list, click Payroll.
In the Logical Tables list, click Payroll Transactions, click Insert, and then click OK.
In the Report Destination dialog box, click to select the appropriate check box, and then click OK.
Note You can safely ignore the error messages that occur in the error log. The Check Links process is reattaching the batch ID to the existing transactions.
NOTE: If your batch should have been a recurring batches, and was rebuilt by the Check Links process, the batch frequency was set to 'single use' by default. Click Transactions, click Payroll, and then click Batches and select the Batch ID that was recreated, and review the Batch settings. If this should be a recurring batch, change the frequency to a Frequency other than Single Use.
Step 4: Build the check file
Build the check file again. All the batches are still in the check file.
Q1: I don't want to delete the whole payroll batch and start completely over, should I still follow the steps above?
A1: Yes, the Transactions in the payroll batch are stored in the UPR10302 Payroll Transactions table, and you are not deleting that table in the scripts above, so the transactions are not getting removed. The scripts only remove the batchheader record (UPR10301) and when you run checklinks, the system will recreate that batch header record again (because it sees it on the transactions still, so it will recreate it.),
Q2: I posted the new batch and it disappeared. It should have been a recurring batch.
A2: When you ran check links to rebuild the batch, it built it with a 'single use' frequency by default. You should have edited the batch frequency before posting it, if it should have been a recurring batch. If you posted the batch, it's too late now. You will need to manually key the batch/transactions back in again (starting on the next posting date needed), and change the frequency on the new batch to be used going forward.