Child pages
  • Common Error Messages from the Broadcast Log
Skip to end of metadata
Go to start of metadata

Below are some common error messages that may appear in the Broadcaster log. The transaction to read the log in the BW backend is RSRD_LOG. For more information about broadcasting please see this link http://help.sap.com/saphelp_nw70ehp1/helpdata/en/bf/220c40ac368f5ce10000000a155106/frameset.htm

ERROR: 'Java communication error: Error when opening an RFC connection'
ERROR: 'Java system error: Call of FM RSRD_X_PRODUCE_PROXY to ProgId.....SSO not authorized'
  • Such errors are generally intermittent & most likely caused by Out-Of-Memory issues in a java server node. When an OutOfMemory (OOM) issue occurs the java server is restarted and synchronization fails which results in the user becoming invalid. Check the Java Default Trace for any Out-Of-Memory errors. As there may be a huge Java Default Trace in the system use the time that the error occurred to isolate the correct trace. The trace reader provided with the Portal tools can be used to decode the date and time.
  • To avoid Out-Of-Memory issues reduce the load on java server. Change Broadcasting to serial processing. To do this set parallelprocessing = 1. For further information see http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/807834109a1b5ae10000000a42189c/frameset.htm
  • Execute Support Desk Tool as per Note 937697. Download the latest version of the tool attached to the note. Ensure that all items are Green by following the solutions provided in the generated supportdesk.zip file.
  • Check through SAP Note 701205 - Troubleshoot Single Sign-On with SAP Logon Tickets.
ERROR: 'Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException'
  • This is most likely an underlying error in execution of the object being broadcast in PDF format. Test the solution from Note 1112132 - The SAP BI Export Library
  • Also review:
    1. Note 1004321 - ADS error: Incorrect content type found
    2. Note 944221 - Troubleshooting if problems occur in forms
  • Execute Support Desk Tool as per Note 937697. Download the latest version of the tool attached to the note. Ensure that all items are Green by following the solutions provided in the generated supportdesk.zip file.
ERROR: 'Java system error: Exception in method processFunction.'
  • Execute Support Desk Tool as per Note 937697. Download the latest version of the tool attached to the note. Ensure that all items are Green by following the solutions provided in the generated supportdesk.zip file.
  • Check the Java Default Trace for errors. As there may be huge java default trace in the system use the time that the error occurred to isolate the correct trace. The trace reader provided with the Portal tools can be used to decode the date and time.
ERROR: 'Error: DomReaderError'
  • Check SAP Note 1025835 'Executing broadcasting settings terminates with DomReadError'
  • Execute Support Desk Tool as per Note 937697. Download the latest version of the tool attached to the note. Ensure that all items are Green by following the solutions provided in the generated supportdesk.zip file.
ERROR: 'RSRD 191 Setting XXXX User YYYY cannot be used for background processing'
  • At the time the broadcaster setting was executed in BACKGROUND the user YYYY could have one or more of these issues.
    • 'user_locked, user_not_active'
    • 'password_expired'
    • 'wrong_password'
    • 'username_not_exists'
    • 'password_logon_disabled'
    • 'user_has_no_password'
  • The user may be able to logon and work in BW via the Portal but in Broadcasting it will be checked if the user is valid in ABAP. This is designed for security reasons. To confirm this, in transaction SE37 execute 'SUSR_LOGIN_CHECK_RFC' and 'SUSR_USER_PASSWORD_STATUS_GET' for the user YYYY and check for any error or exception.
ERROR: 'Precalculation server XXXX is not ready'
  • When using SAP BW Precalculation Service Multi Instance a BExPrecalcWorker.exe process is started for each instance. Once a worker process finishes processing, it ends itself and is then restarted after some time. The service itself is not restarted.
    In the time between ending the old worker process and the new worker process connecting to the system (around 20
         seconds) this instance appears RED in RSPRECALCADMIN. This is as designed. The message "Precalc server is not ready" may appear in the log during the worker process restart.
ERROR: Unresolved exception occurred

'Unresolved exception occurred on the precalculation server system.Runtime.InteropServices.COMException(0x800706BE). The remote procedure call failed.
at Microsoft.VisualBasic.CompilerServices.LateB Binding.LateGet(Object o, Type objType, String nam, Object[] args, String[] paramnames, Boolean[] CopyBack)
at com.sap.bi.et.precalculation.BexExcelPrecDll l.StartCalc (Exception& eException, String& eTrace, String iVariant, DataTable iVarTable) The remote procedure call failed.
at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String nam, Object[] args, String[]paramnames, Boolean[] CopyBack)
at com.sap.bi.et.precalculation.BexExcelPrecDll l.StartCalc(Exception& eException, String& eTrace, String iVariant, DataTable iVarTable) Precalclulation in thread failed.'

  • This is a typical error when Precalculation is run from virtual machines. It is critical to run Precalculation on virtual machines. We do not recommend to do that because you have no real access to Host resources. If on the real host a lot of VMwares are installed the IO Rate is quite bad and in some cases this leads to an issue in RPC automation
    because the RPC server (Excel) will not react in time and will throw Automation errors like:
    System.Runtime.InteropServices.COMException (0x80010105): The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
  • So we only recommend to use physical servers. See Note 1236773 for more details.
ERROR: 'Precalculation server XXXX does not exist'
  1. Check transaction RSPRECALCADMIN and ensure that the Precalculation server is maintained there, showing Green with status Ready.
ERROR: 'Parallel processing not possible: no processing of X package(s)'
  1. To overcome Parallel Processing errors create a Process Chain which executes settings using report RSRD_BROADCAST_BATCH.
    1. Create the variants for report RSRD_BROADCAST_BATCH: Start transaction SE38 and execute the report RSRD_BROADCAST_BATCH. Select the Broadcaster setting(s) and save them as a variant.
    2. Include a process step in a process chain which executes an ABAP program. In the process step, choose the report RSRD_BROADCAST_BATCH and the variant (from step 1) in the process chain step. Do not use more tham 1 ABAP program with  RSRD_BROADCAST_BATCH in 1 Process chain. You may include as many Broadcaster setting(s) as required in 1 variant. The main goal is that only ONE  RSRD_BROADCAST_BATCH should be running in BW system at any point of time.
    3. Number of parallel process to be triggered can be defined in Transaction RSBATCH. If nothing is defined for Process 'Broadcast' in Transaction RSBATCH then a default value of 3 is used. In case a precalcualtion server is involved in this broadcasting senario, please make sure that the 'number of parallel process' is less than the total number of precaclualtion server instances defined in RSPRECALCADMIN.
    4. The Parallel processing implementation assuming a hardcoded waiting time of 30 seconds per cycle and use this in conjunction with workload duration and number of packages to calculate maximum number of cycles to retry. The standard number of retry per process is generally limited to 10. A process after triggering for 10 times in an interval of 30 seconds each (10 * 30seconds = 5 minutes) does not get the resources (precaclualtion server instance OR JAVA process) free to proceed, then it is killed and the above mentioned error is raised. Thus implement the ABAP correction from note 1431856 and maintain the parameter BC_MAX_WAIT_CYCLES and BC_WAIT_SECONDS_PER_CYCLE as per your requirement.
ERROR: Error while executing function module: BICS_PROV_GET_RESULT_SET 
  • Issue occurs when the broadcast is processing a huge volume of data for a single query. The behavior is documented by SAP Note 2217051 - Error while executing function module: BICS_PROV_GET_RESULT_SET. As solution, you can setup the safety belt parameter and reduce the query result set.

 


Link to this page: https://wiki.scn.sap.com/wiki/x/2IH9Cw


 

  • No labels