cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Error accessing the BEx Web Application

joo_migueldimas
Active Participant

on ‎06-22-2015 12:52 PM

0 Kudos

Hello,


This is an error in SAP BW Netweaver 7.31.

We done a support packages update a week ago to SP11.

Now, we´re facing one error when we try to connect to BEx Web Application (web access to reports):

The error details show the following error:

The initial exception that caused the request to fail was: com/sap/tc/ur/browser/BrowserDescriptor : cannot initialize class because prior initialization attempt failed


We already tried to apply the SAP notes 1995970 and also the 2000082 but unfortunately they are not applicable through SNOTE transaction, because we searched for a solution and we found the

Any tips? Can you help us to find a solution for our problem?

Kind regards,

JD

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (2)

Answers (2)

divyanshu_srivastava3
Active Contributor
‎06-22-2015 3:02 PM
0 Kudos

Hi Dimas,

Can you share the logs of the log ID that you see at the bottom of your browser ?

Also about your system specification that includes release, SP and patch level ?

Regards,

Show replies
Show replies
joo_migueldimas
Active Participant
‎06-22-2015 3:53 PM
0 Kudos

Hello Divyanshu Srivastava,

The patch level of this SAP system (Java side) is that I mentioned in my previous message (my answer to Carlos Behlau). Can you check please?


Can you share the logs of the log ID that you see at the bottom of your browser ?

Where do we check that log files? Can you tell us please?


Kind regards,

JD

divyanshu_srivastava3
Active Contributor
‎06-22-2015 4:02 PM
0 Kudos 


EP-BASIS sap.com SAP AG 1000.7.31.11.0.20140224203900

The number in bold is the patch level which is '0' and should be '3' for SP11 for EP_BASIS.

So you need to appy the patch using SUM or telnet and try this again.

BTW, all logs can be found in /usr/sap/SID/instance/j2ee/cluster/server0 and in log folder insider server0 for above error.

Regards,

behlau_carlos
Contributor
‎06-22-2015 2:56 PM
0 Kudos

Hello João,

did you patch as in note http://service.sap.com/sap/support/notes/1995970 to patch level 3 for your SP11 (your basis component of your BI Portal)?

If yes, I would create a SAP support request.

Best regards

Carlos Behlau

Show replies
Show replies
joo_migueldimas
Active Participant
‎06-22-2015 3:35 PM
0 Kudos

Hello Carlos Behlau,

This is the list of JAVA components of our SAP BW (Java side) system.

I don´t know exactly what is to do with sap note 1995970... as I mentioned I tried to implement this SAP note through SNOTE transaction but the system informs that is impossible (not applicable).

NameVendorLocationVersion
AJAX-RUNTIMEsap.comSAP AG1000.7.31.11.0.20140212000100
BASETABLESsap.comSAP AG1000.7.31.11.0.20140213211900
BI-BASE-Bsap.comSAP AG1000.7.31.13.0.20140820184400
BI-BASE-Esap.comSAP AG1000.7.31.13.0.20140820184400
BI-BASE-Ssap.comSAP AG1000.7.31.13.0.20140820184400
BI-IBCsap.comSAP AG1000.7.31.13.0.20140820184400
BI-REPPLANsap.comSAP AG1000.7.31.13.0.20140820190600
BI-WDALVsap.comSAP AG1000.7.31.11.0.20140116201100
BIWEBAPPsap.comSAP AG1000.7.31.13.0.20140820184400
BI_UDIsap.comSAP AG1000.7.31.11.0.20140116232200
CFG_ZAsap.comSAP AG1000.7.31.11.0.20140116191700
CFG_ZA_CEsap.comSAP AG1000.7.31.11.0.20140116191700
COMP_BUILDTsap.comSAP AG1000.7.31.11.0.20140116214400
CORE-TOOLSsap.comSAP AG1000.7.31.11.0.20140116191700
CU-BASE-JAVAsap.comSAP AG1000.7.31.11.0.20140116223300
CU-BASE-WDsap.comSAP AG1000.7.31.11.0.20140117021000
DATA-MAPPINGsap.comSAP AG1000.7.31.11.0.20140116223300
DI_CLIENTSsap.comSAP AG1000.7.31.11.0.20140116192000
ECM-ADMINsap.comSAP AG1000.7.31.11.0.20140116200300
ECM-APPSsap.comSAP AG1000.7.31.11.0.20140116200300
ECM-COREsap.comSAP AG1000.7.31.11.0.20140116200300
ECM-JEE-COMPsap.comSAP AG1000.7.31.11.0.20140116200300
ECM-STOREsap.comSAP AG1000.7.31.11.0.20140116200300
ENGFACADEsap.comSAP AG1000.7.31.11.0.20140116171500
ENGINEAPIsap.comSAP AG1000.7.31.11.0.20140116191700
EP-ADMINsap.comSAP AG1000.7.31.11.0.20140116232900
EP-APPS-EXTsap.comSAP AG1000.7.31.11.0.20140116232900
EP-BASISsap.comSAP AG1000.7.31.11.0.20140224203900
EP-BASIS-APIsap.comSAP AG1000.7.31.11.0.20140116232900
EP-CONNECTIVITYsap.comSAP AG1000.7.31.11.0.20140116232900
EP-CONNECTIVITY-EXTsap.comSAP AG1000.7.31.11.0.20140116232900
EP-RUNTIMEsap.comSAP AG1000.7.31.11.0.20140131042700
EP-WPCsap.comSAP AG1000.7.31.11.0.20140116232900
EP_BUILDTsap.comSAP AG1000.7.31.11.0.20140116214400
ESCONF_BUILDTsap.comSAP AG1000.7.31.11.0.20140116214400
ESI-UIsap.comSAP AG1000.7.31.11.0.20140117015500
ESMP_BUILDTsap.comSAP AG1000.7.31.11.0.20140116223300
ESP_FRAMEWORKsap.comSAP AG1000.7.31.11.0.20140116225100
ESREG-BASICsap.comSAP AG1000.7.31.11.1.20140416205600
ESREG-SERVICESsap.comSAP AG1000.7.31.11.1.20140315070000
FRAMEWORKsap.comSAP AG1000.7.31.11.0.20140116192000
FRAMEWORK-EXTsap.comSAP AG1000.7.31.11.0.20140116232200
GROUPWAREsap.comSAP AG1000.7.31.11.0.20140117004300
J2EE-APPSsap.comSAP AG1000.7.31.11.0.20140116191700
J2EE-FRMWsap.comSAP AG1000.7.31.11.0.20140211235000
JSPMsap.comSAP AG1000.7.31.11.0.20140116191700
JWFsap.comSAP AG1000.7.31.11.0.20140117004300
KM-KW_JIKSsap.comSAP AG1000.7.31.11.0.20140116232200
KMC-BCsap.comSAP AG1000.7.31.11.0.20140117004300
KMC-CMsap.comSAP AG1000.7.31.11.0.20140117004300
KMC-COLLsap.comSAP AG1000.7.31.11.0.20140117004300
KMC-WPCsap.comSAP AG1000.7.31.11.0.20140117004300
LM-COREsap.comSAP AG1000.7.31.11.0.20140211235000
LM-CTSsap.comSAP AG1000.7.31.11.0.20140116201100
LM-CTS-UIsap.comSAP AG1000.7.31.11.1.20140618173000
LM-MODEL-BASEsap.comSAP AG1000.7.31.11.0.20140116201100
LM-MODEL-NWsap.comSAP AG1000.7.31.11.0.20140116201100
LM-PORTALsap.comSAP AG1000.7.31.11.0.20140117021000
LM-SLDsap.comSAP AG1000.7.31.11.0.20140116201100
LM-TOOLSsap.comSAP AG1000.7.31.11.0.20140117021000
LMCFGsap.comSAP AG1000.7.31.11.0.20140116201100
LMCTCsap.comSAP AG1000.7.31.11.5.20141014180900
LMNWABASICAPPSsap.comSAP AG1000.7.31.11.0.20140116202900
LMNWABASICCOMPsap.comSAP AG1000.7.31.11.0.20140116202900
LMNWABASICMBEANsap.comSAP AG1000.7.31.11.0.20140116202900
LMNWACDPsap.comSAP AG1000.7.31.11.0.20140116201100
LMNWATOOLSsap.comSAP AG1000.7.31.11.0.20140117021000
LMNWAUIFRMRKsap.comSAP AG1000.7.31.11.0.20140116201100
MESSAGINGsap.comSAP AG1000.7.31.11.30.20141125200000
MMR_SERVERsap.comSAP AG1000.7.31.11.0.20140116232200
MOIN_BUILDTsap.comSAP AG1000.7.31.11.0.20140116191600
NET-PDKsap.comSAP AG1000.7.31.11.0.20140116232900
NWTECsap.comSAP AG1000.7.31.11.0.20140116201100
ODATA-CXF-EXTsap.comSAP AG1000.7.31.11.0.20140116201100
RTCsap.comSAP AG1000.7.31.11.0.20140117004300
RTC-STREAMsap.comSAP AG1000.7.31.11.0.20140117004300
SAP-XI3RDPARTYsap.comSAP AG1000.7.31.1.0.20110918004000
SAP_BUILDTsap.comSAP AG1000.7.31.11.0.20140116191600
SECURITY-EXTsap.comSAP AG1000.7.31.11.0.20140116191700
SERVERCOREsap.comSAP AG1000.7.31.11.0.20140116191700
SERVICE-COMPsap.comSAP AG1000.7.31.11.0.20140116223300
SOAMONBASICsap.comSAP AG1000.7.31.11.9.20140827015800
SR-UIsap.comSAP AG1000.7.31.11.0.20140117015500
SUPPORTTOOLSsap.comSAP AG1000.7.31.11.0.20140116191700
SWLIFECYCLsap.comSAP AG1000.7.31.11.0.20140117021000
UDDIsap.comSAP AG1000.7.31.11.0.20140116225100
UISAPUI5_JAVAsap.comSAP AG1000.7.31.11.0.20140116192000
UKMS_JAVAsap.comSAP AG1000.7.31.11.0.20140117015500
UMEADMINsap.comSAP AG1000.7.31.11.0.20140116201100
UWLJWFsap.comSAP AG1000.7.31.11.0.20140117004300
VC70RUNTIMEsap.comSAP AG1000.7.31.11.0.20140116232200
WD-ADOBEsap.comSAP AG1000.7.31.11.0.20140116195000
WD-APPSsap.comSAP AG1000.7.31.11.0.20140116212000
WD-RUNTIMEsap.comSAP AG1000.7.31.11.0.20140303130000
WD-RUNTIME-EXTsap.comSAP AG1000.7.31.11.0.20140116212000
WSRMsap.comSAP AG1000.7.31.11.1.20140326125700

Any tips?

Best regards,

JD

divyanshu_srivastava3
Active Contributor
‎06-22-2015 3:45 PM
0 Kudos

Hi,

If you see, your EP-BASIS is at patch 0 and you need patch 3 to fix it.

EPBASIS11P_27-20007130.SCA

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/swdc/notes/default.htm?cvnr=01200314690...

Regards,

divyanshu_srivastava3
Active Contributor
‎06-22-2015 3:46 PM
0 Kudos

Also, this was a KBA not a an SAP note that you can apply thru snote

That is why I asked you to share your system specification.

Regards,

behlau_carlos
Contributor
‎06-22-2015 3:49 PM
0 Kudos

Hello João,

you need to create on your SAP Solution Manager a update request for your SAP BI Portal instance and approve the patch.

This generates a file, that you later use of with SUM (Software Update Manager).

Best regards

Carlos

joo_migueldimas
Active Participant
‎06-22-2015 4:53 PM
0 Kudos

Hello Divyanshu Srivastava,

Ah ok...

But tell me one thing can I only import that file that you sent me or it´s recommended to perform the Maintenance Optimizer check to know if there are some compatibility issues!?

Kind regards,

JD

divyanshu_srivastava3
Active Contributor
‎06-22-2015 4:55 PM
0 Kudos

I don't think so.. but you can check the SCA dependency in the link I posted above or try with MOPZ.

Regards,

divyanshu_srivastava3
Active Contributor
‎06-22-2015 5:09 PM
0 Kudos

Also, you should check below KBA for clarification.

1641062 - Single component update and patch scenarios in SUM
You should use MOPZ for as "The rules are checked with the stack xml file of the SP generated by the MOpz" however, manual application of patches if also possible if there is no such dependencies on patch and if there, it should be taken into account.

BTW, in your case, I would still raise an incident with SAP for a confirmation.

Regards,

joo_migueldimas
Active Participant
‎06-22-2015 6:03 PM
0 Kudos

Hum Ok Divyanshu,

I checked the link that you posted and it seems to me there are some dependencies of others SAP components. So... will I need to import all those files at once or one by one using the SUM tool?

Thank you,

JD

divyanshu_srivastava3
Active Contributor
‎06-22-2015 6:10 PM
0 Kudos

once using SUM is easy and safe.

Regards,

joo_migueldimas
Active Participant
‎06-22-2015 7:01 PM
0 Kudos

Ok Divyanshu,

I will try that, but I´m afraid that will not solve this problem... why? Because before I performed the support packages update to SP11 this system had the SP09 with patch level 0, as you can see below, and I never faced this situation/error when we started the BEx Web Application.

EP-BASISsap.comSAP AG1000.7.31.9.0.20130802015500

Kind regards,

JD

joo_migueldimas
Active Participant
‎06-26-2015 6:05 PM
0 Kudos

Hello Divyanshu Srivastava,

I´m trying to update the Java stack using the SUM tool, with the following seven files which are the ones that you mentioned.

For this I´m using the "Manually prepared directory" option in SUM tool:

But unfortunately the SUM tool show me the following error:

In details I see this:

Can you help me please to understand why the SUM shows this error? Any idea? I need the .xml stack file!? I guess I have all the requirements that is described in the sap note 1641062 (Single component update and patch scenarios in SUM)... am I right?

Best regards,

JD

divyanshu_srivastava3
Active Contributor
‎06-26-2015 7:32 PM
0 Kudos

Hi Dimas,

The stack file shows that these components are at SP09 and you are applying patches of SP11 components.

In general, you 1st need to update the definition of your JAVA system in SOLMAN, the place from where you have to generate the stack.xml file.

Goto NWA - and trigger SLD data supplier to the SLD which is connected to LMDB.

Once the system definitions are updated in LMDB, you can generate a stack.xml file for updating java patches which will include the current component version of your JAVA system and you won't get this error. Make sure to add java patches .

The above was a standard practice to update a JAVA stack including latest patches.

Now for the above error in case of manually prepared directory case, read the below wiki - it has a solution section which talks about it.

1837305 - SCA provided using Manually Prepared Directory are rejected and not detected by SUM tool during validation or while scanning

(SUM)-Manually prepared directory SCA are rejected - Technology Troubleshooting Guide - SCN Wiki

Regards,

Ask a Question