Skip to Content
avatar image
Former Member

Universe Connection fails - Unable to load catalog


Please can someone assist.

When I try and create a new connection.

DBD: A runtime exception has occurred (error getting list of catalogs)

When I try and refresh an existing structure, I get the following error:

Connection Error: Error loading cube XXX (catalog 0).

On Friday I had no issues, could create and refresh connections - obviously something has changed, but I do not know what to even look for.

I am connection to SAP Netweaver7.

I have checked to see all my objects are active.

My licences are current

I have also run the queries in BEx, and Analyser and they are working.

I tried to run the BAPI BAPI_MDPROVIDER_GET_CUBES, but this caused a short dump

Any assistance would be greatly appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    Oct 22, 2012 at 09:58 AM


    If your SAP user can't run BAPI_MDPROVIDER_GET_CUBES in BW transaction SE37 due to a program termination then you have an ABAP problem.

    Sounds like the Authorizations for your SAP_USR have changed - you need to contact your BASIS to resolve this get-cubes problem.



    Add comment
    10|10000 characters needed characters exceeded

  • Oct 22, 2012 at 09:53 AM

    Hi Catherine

    Please check if SSO is enabled for universe connection. Because since SSO is used in the universe connection it takes the credentials of the user logged in and the concerned user does not have the required authorization from the BW System. If you remove SSO form the universe connection, hardcore the credentials and then open the same report logging in as the concerned user, it works fine.

    As solution, please provide "S_RFC" (Authorization check for RFC access) authorization on the BW system to the concerned user.

    Best Regards



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      Thank you for the response. We use named users when we create the connections - and not SSO - would this make a difference?