How to resolve a status 4 batch

This article explains the possible reasons for and troubleshooting steps to resolve a status 4 batch.

NOTE: The steps below can also apply to a status 2 or 3 batch if you want to post it.  However, in status 2 or 3 you still have the option to set batch to Open and edit or clear the batch before posting if desired.

CAUTION:A stuck batch will display a Status of "4 - Posting in Progress" in HQ Batch Control.  It is important to leave the status as is, since this indicates that only part of the batch has posted. The batch cannot be deleted. 

1. Go to the module where the batch was created and open Programs - Batch Process.

   NOTE: Different rules apply to batches from the PM module that may require assistance from the Viewpoint Support team.  PM Projection Batches can be posted through JC Batch Process.  For other PM source batches, please refer to KB PM Interface Error Message: Unable to post - SL batches must have SL source.   

2. Enter the batch month and batch number (it probably will not be included in the F4 list so you will need to key it in).

   NOTE: If you receive an error saying the batch is "In Use" go to HQ Batch Control and clear the 'in use by' field for this batch.

3. DO NOT REVALIDATE THIS BATCH. If for some reason the Validate option is available (it should not be when the batch is Status 4), do not select Validate. Go straight to step 4.

4. Click Post.

5. If the problem was caused by a loss of connection, OR a setup issue has been resolved since you originally posted, the batch should post successfully.

6. If there is still an error, you should get an error message with details of the problem. Take a snapshot or write down the exact details of the error message. If you cannot determine the problem from the error message itself, look up the error in our Knowledgebase. A resolution for most posting errors can be found there.

7. If you are still unable to resolve the problem, please open a support case with the details of your posting error.

Batches get stuck in Status 4 for two common reasons:

1. Loss of power or connection between the workstation and the server,

2. A "trigger error" indicating a setup problem that conflicts with the data in the batch.