SAP Knowledge Base Article - Public

3528819 - Error message 'Lookup of function RSAO_BICS_OPEN metadata failed for destination xxx' is displayed when opening AO workbook

Symptom

  • When opening an AO workbook, following error message is displayed when AO tries to connect to the BW system:

    [290e-2329-17] Lookup of function RSAO_BICS_OPEN metadata failed for destination XXX
    [290e-2329-17] The only destination xxx available failed when retrieving
    metadata from XXX -- see log for details

  • Issue may occurs only for specific users.

  • In AO_Trace, following exception can be found:

    General .NET Exception [290e-2329-17]:
    Lookup of function RSBOLAP_BICS_STATISTIC_INFO metadata failed for destination XXX
         SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadataClassic(String name)
         SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadata(String name)
         SAP.Middleware.Connector.RfcRepository.GetFunctionMetadata(String name, Boolean reload)
         SAP.Middleware.Connector.RfcRepository.CreateFunction(String name)
         com.sap.ip.bi.base.application.service.rfcproxy.impl.nco3.Nco3Proxy.createFunctionWithoutGracefulFailure(String name)
         com.sap.ip.bi.base.application.service.impl.statistic.StatisticService.writeEvents(Boolean stepClose)
         com.sap.ip.bi.base.application.statistic.impl.StatisticApplicationStep.endApplicationStep()
         com.sap.ip.bi.base.application.statistic.impl.StatisticManager.stepClose()
         com.sap.ip.bi.base.application.impl.Application.endApplicationStep(Int32 commitMemoryTag, Int32 exceptionReason)
         com.sap.ip.bi.base.application.impl.Application.endApplicationStep()
         com.sap.ip.bi.base.application.impl.Application.destroy()
    >>
    General .NET Exception [290e-2329-17]:
    The only destination XXX available failed when retrieving metadata from XXX -- see log for details
        SAP.Middleware.Connector.RfcRepository.FindAlternateDestination(Int32& destIndex, Int32& alternativeDestinationsCount, Exception ex)
        SAP.Middleware.Connector.RfcRepository.Execute(RfcFunction function)
        SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadataClassic(String name)
  • In 'dev_nco_rfc.log' trace, following exception can be found:

    SAP.Middleware.Connector.RfcAbapRuntimeException: No RFC authorization for function module RFC_FUNCTION_SEARCH.
       at SAP.Middleware.Connector.RfcFunction.RfcCallReceive(RfcConnection conn, RFCID rid)
       at SAP.Middleware.Connector.RfcRepository.Execute(RfcFunction function)
       at SAP.Middleware.Connector.RfcRepository.UseRfcMetadataGet()
       at SAP.Middleware.Connector.RfcRepository.LookupFunctionMetadata(String name)
       at SAP.Middleware.Connector.RfcRepository.GetFunctionMetadata(String name, Boolean reload)
       at SAP.Middleware.Connector.RfcRepository.CreateFunction(String name)
       at com.sap.ip.bi.pioneer.core.Connections.Rfc.CrRfcProxy.GetInternalRfcFunction(String destinationName, String functionName)
       at com.sap.ip.bi.pioneer.core.Connections.Rfc.CrRfcProxy.call_RSAO_BICS_SESSION_INITIALIZE(String iDestinationName, String iSessionId, Dictionary`2 iFrontendParameters, Boolean& oNoBwFunctionalityAvailable)

Environment

SAP Analysis for Microsoft Office

Reproducing the Issue

  1. Open an Analysis Office workbook.
  2. Refresh All.
  3. Error message is displayed.

Cause

  • Analysis on the client PC requests data from the BW server. This communication is carried out with a synchronous Remote Function Call (RFC) connection. User need sufficient authorization for the RFC. Otherwise RFC error occurs.
  • Issue may also occur when the system cached RFC data in local PC is inconsistent or incorrect.

Resolution

  1. Ensure RFC authorization is assigned to affected user for the required function module and function group. The RFC authorization object is S_RFC. 
    See details in: KBA 3286403 - Invalid program status\: RFC_ERROR_SYSTEM_FAILURE: No RFC authorization for function module <FM> - RFC_NO_AUTHORITY
  2. If issue persists, navigate to the following path: %APPDATA%\SAP AG\SAP BusinessObjects Advanced Analysis\cache. There you will find a list of all cached systems. Delete the cache file for the system to which the user is not able to connect to. 

See Also

KBA 3286403 - Invalid program status\: RFC_ERROR_SYSTEM_FAILURE: No RFC authorization for function module <FM> - RFC_NO_AUTHORITY

Keywords

Analysis Office, Analysis for Office, A4O, Analysis for Excel, A4O, access, authorized , KBA , BI-RA-AO-XLA , Excel Addin , Problem

Product

SAP Analysis for Microsoft Office all versions