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 - "Open operation on UPR_Temp_Post2 has incorrect record length"
Error - "Remove Range Operation on Table ddDeposits has caused known error 2"
Error - "Batches with zero transactions cannot be marked"
Error - "Another user is performing a check run"
Error - "UPR_Work_Post failed accessing SQL data"
Error - "The employee record cannot be inactivated or deleted Pay run is in progress for this employee"
Error - "Checks cannot be calculated. Errors were found."
Error - "You cannot void a check. A computer check run is in process."
Error - "You cannot edit a batch marked for posting"
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:
UPR_WORK_MSTR
UPR_WORK_MSTR_Detail
UPR_WORK_HDR
UPR_WORK_Pay_Type
UPR_WORK_Deduction
UPR_WORK_Benefit
UPR_WORK_State_Tax
UPR_WORK_Local Tax
UPR_WORK_Check
UPR_WORK_Post
UPR_Flat_Tax_Records
UPR_Account_Cache
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 clear the payroll work tables yourself, follow these steps:
a. 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.
b. 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.
c. If you use Direct Deposit, run delete statements for Direct Deposit:
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
Delete DD10100 (Direct Deposit Employee Deposit Work)
Delete DD10200 (Direct Deposit ACH Copy)
Delete DD10300 (Direct Deposit ACH Cross Reference)
Delete DD10400 (Direct Deposit ACH Header) If this file is renamed or deleted, you will lose
Delete DD10500 (Direct Deposit ACH Items) If this file is renamed or deleted, you will lose
Delete DD10600 (Direct Deposit Prenotes Completed)
Delete DD10700 (Direct Deposit Exceptions)
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:
C:\Windows\Temporary
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:
a. Use the appropriate method to open the check Links window.
In Microsoft Dynamics GP 10.0 or Microsoft Dynamic GP 2010, click Microsoft Dynamics GP, click
Maintenance, and then click Check Links.
In Microsoft Dynamics GP 9.0, click File, point to Maintenance, and then click Check Links.
b. In the Series list, click Payroll.
c. In the Logical Tables list, click Payroll Transactions, click Insert, and then click OK.
d. 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.
Step 4: Build the check file
Build the check file again. All the batches are still in the check file.
Note If you have recurring batches, and you delete the UPR10301 file in step 1, the frequency defaults back to
single use when you run the Check Links process. Before you post the batch, click Transactions, click Payroll,
and then click Batches. Select the recurring batch, and then change the frequency to a frequency other than
Single.