Error in phases MAIN_SWITCH/JOB_RSVBCHCK2 or Checks after phase MAIN_INIT/JOB_RSVBCHCK* were negative

Symptom:

Error in phases MAIN_SWITCH/JOB_RSVBCHCK2 or MAIN_SWITCH/JOB_RSVBCHCK_D; Checks after phase MAIN_INIT/JOB_RSVBCHCK* were negative.

Cause:

1. The update requests have been canceled, but entries in tables related to the update process are not     empty and these tables must be empty during upgrade process.

2. Outstanding update requests (visible in transaction code SM13) and queued RFCs (visible with transaction code SMQ1) exist in the system.

Solution:

Scenario A: Error

Batchjob RSVBCHCK failed. 

Detected the following errors due to error summary in /<SUM_Directory/abap/log/PSVBCHCK.ELG:

1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

In Log file: PSVBCHCK.ELG

1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

Scenario B: Error

Batchjob RSVBCHCK failed. 

Detected the following errors due to error summary in ../SUM/abap/log/PSVBCHCK.ELG:

1 ETH010XRSVBCHCK: Check of open update requests

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->

Log file: PSVBCHCK.ELG

1 ETH010XRSVBCHCK: Check of open update requests

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->

Scenario C: Error

Batchjob RSVBCHCK failed. 

Detected the following errors due to error summary in /SUM_Directory/abap/log/PSVBCHCK.ELG:

1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->

In Log file: PSVBCHCK.ELG

1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

A2EEMCEX 151 Entries for application "xx" still exist in the extraction queue ->

Scenario A: Solution

Make sure that you have cleaned up all outstanding updates.

To find terminated or unresolved updates, proceed as follows:

Call transaction SM13.

Delete the default values for the client, user, and time.

Select all the update requests and clear them.

Use the delete/reorg functionality of the update report RSM13001 or RSM13002 as described on the WIKI page Reports RSM13001 and RSM13002 

Scenario B: Solution

Please follow the steps described in the SAP Note 1083709 according to the reported error message A2EEMCEX 140 , A2EEMCEX 141, A2EEMCEX 149 or A2EEMCEX 151. 

See also the SAP Note  328181 

To be able to logon to each listed client, please unlock the system first and then logon. (see also the SAP KBA 1901463)

Make sure that you lock the system back after you executed the steps and then continue with the upgrade.

Scenario C:Solution

Execute the steps described in Scenario A   AND   in Scenario B.

Hope this helps!!!

Abraham