Error: Object reference not set to an instance of an object is received in different instances in Transaction (see screenshot examples below.
This is a general error that can occur during different scenarios.
Transaction, Studio, Runner
User is missing access for S_TABU_DIS RC=4 ACTVT=03 and DICBERCLS=SS.
- Perform a full user trace using SAP transaction ST01 (How to take a SAP User Security Trace) and find the missing access for S_TABU_DIS RC=4 ACTVT=03 and DICBERCLS=SS.
- Add the role that contains access to S_TABU_DIS.
- If this does not resolve the error, enable the Application trace and run an authorization check. See What authorizations do I need for Transaction? on how to do this.
- Re-run the scenario and send the generated trace file from the following location C:\Users\Your Username \Documents\Winshuttle\Runner\Log and screenshot of the authorization check to Winshuttle Support. If you have been asked for this information as part of an ongoing support ticket interaction, please reply to the current email thread. If instead, you would like to open a new case with Winshuttle using this information as a reference, please open a new case here
This issue can also be caused by macros.
Note: Macros are version specific, if the user has upgraded the Winshuttle product (Transaction, Runner), the macro will not work as the macros are not written for the changing versions.