Skip to Content
0
Former Member
Sep 15, 2007 at 02:09 PM

Java system error: Bean BICS_CONS_GET_VIEW_DEF_J_PROXY not found

30 Views

In BEx Report Designer, click Insert Data provider under Report, and then choose one create query, system show the error message(message class:RSBOLAP, message number:018), the detail diagnosis like below, please help to solve it. Thanks!

Diagnosis

Error while loading query metadata, Check the query and portal settings

An error occurred in the BI components on the SAP J2EE Engine.

System Response

Procedure

Contact your system administrator to have the error analyzed in detail.

Procedure for System Administration

Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".

The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".

If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.