BI JAVA 7.3 UME error

[Former Member]

Dear Guru's,

I have installed BI Java 7.3 system , ABAP as the data source. After installing i have done all required post installation activities. but am not able to create/display any User/role in Java UME.

It's giving the below error message while searching any role/user in java. I have given proper permissions for admin user id.

"error occurred, please contact your system administrator".

if anyone come across the similar situation, please let me know.

Regards,

[RolandKramer]

see thread -

Best Regards Roland

[larserikh]

Better late than never...check note 2126112.

Regards,

LEH

[JaySchwendemann]

Thanks Lars-Erik, that seems indeed be the root cause / solution. Unfortunately I'm still stuck ant SPS 7 for the time being. However, this error is not critical, so we bear 🙂

Cheers

Jens

[former_member188073]

If this is a Time Znoe error please check the SAP ABAP STZAC, ABAP OS and Portal OS timezones

[former_member188073]

Is it true that on 7.3 onward an ABAP datasource is not supported. IF it is so you cold check someting on this line

[Former Member]

No Varun,

We have 7.3 PI which is abap+java. And for j2ee data source is abap only we used

Sudip

[Former Member]

Hi,

Please check the role provided to user SAPJSF in the ABAP system. This user is used to communicate between ABAP and Java while performing user admini activities in the BI Java system.

If the user SAPJSF has role sap_bc_jsf_communication_ro then it means the Java UME can only read user information for the ABAP system. You cannot create any new stuff in the Java user admin. You can either create the required user/role in ABAP or else change role assigned to SAPJSF user to sap_bc_jsf_communication which allows creation of users from Java user admin as well. The latter step will need system restart for BI Java.

Regards,

Srikishan

[Former Member]

Hello ,

I have given required roles to SAPJSF user in ABAP. Still am getting the same error.

[Former Member]

Hello Venkat,

If you are logging with J2EE_ADMIN/ADMINISTRATOR, please make sure it has necessary roles assigned.

Thanks,

Siva Kumar

[Former Member]

Hi,

Just to check, are the profile generated for the assigned roles in SU01. Also check if user comparison is done.

Regards,

Srikishan

[Former Member]

hello,

Am able to assign the roles in ABAP, but am not able to creat/display any users/roles/groups in JAVA.

[Former Member]

hello ,

it's done. before assigning,i have generated all roles.

[sivakumar_kilari3]

Hi ,

Find default trace file for error.or paste the errors here.

Which roles you assigned to this user J2EE_ADM_<SID> ?

Thanks

Siva

[Former Member]

Hello siva,

I have given these roles for j2ee_adm_sid user.

SAP_BC_JSF_COMMUNICATION

SAP_J2EE_ADMIN

SAP_SLD_ADMINISTRATOR

and i have assigned s_bw_rfc profile also

Trace log is below.

#2.#2011 11 30 05:35:43:749#+00#Error#com.sap.i18n.SAPTimeZoneInfo#

#BC-I18-JAV#tc_i18nsaptimezone#C0000AE03A2C00A600000003000003E6#905601150000000004#sap.com/tc_lmitsam_uimainframe~wd#com.sap.i18n.SAPTimeZoneInfo.SAPTimeZoneException#TEST1#3##86E0911D1B1311E18218000035FA607E#c16ed9e81b1311e1c03c000035fa607e#c16ed9e81b1311e1c03c000035fa607e#0#Thread[HTTP Worker [@641656524],5,Dedicated_Application_Thread]#Plain##

CreateSAPTimeZone + failed. Reason: # #2.#2011 11 30 05:35:43:750#+00#Error#com.sap.i18n.SAPTimeZoneInfo# #BC-I18-JAV#tc_i18nsaptimezone#C0000AE03A2C00A600000005000003E6#905601150000000004#sap.com/tc_lmitsam_uimainframe~wd#com.sap.i18n.SAPTimeZoneInfo.SAPTimeZoneException#TEST1#3##86E0911D1B1311E18218000035FA607E#c16ed9e81b1311e1c03c000035fa607e#c16ed9e81b1311e1c03c000035fa607e#0#Thread[HTTP Worker [@641656524],5,Dedicated_Application_Thread]#Plain## CreateSAPTimeZone + failed. Reason: #

#2.#2011 11 30 05:35:43:751#+00#Error#com.sap.i18n.SAPTimeZoneInfo#

#BC-I18-JAV#tc_i18nsaptimezone#C0000AE03A2C00A600000007000003E6#905601150000000004#sap.com/tc_lmitsam_uimainframe~wd#com.sap.i18n.SAPTimeZoneInfo.SAPTimeZoneException#TEST1#3##86E0911D1B1311E18218000035FA607E#c16ed9e81b1311e1c03c000035fa607e#c16ed9e81b1311e1c03c000035fa607e#0#Thread[HTTP Worker [@641656524],5,Dedicated_Application_Thread]#Plain##

CreateSAPTimeZone + failed. Reason: #

#2.#2011 11 30 05:43:15:583#+00#Error#com.sap.security.wd.destinations.helper.BackendSystemManager#

#BC-JAS-SEC#sap.com/tc_secdest_uiif#C0000AE03A2C00DB00000002000003E6#905601150000000004#sap.com/tc_lmitsam_uimainframe~wd#com.sap.security.wd.destinations.helper.BackendSystemManager#J2EE_ADMIN#6##8CE0ACDB1B1511E1C71B000035FA607E#0a1316581b1611e1bccc000035fa607e#0a1316581b1611e1bccc000035fa607e#0#Thread[HTTP Worker [@2123693537],5,Dedicated_Application_Thread]#Plain##

Name must not be null for ElementName

[EXCEPTION]

com.sap.sld.api.wbem.exception.CIMMissingAttributeException: Name must not be null for ElementName

at com.sap.sld.api.wbem.cim.InternalUtil.checkNonNull(InternalUtil.java:54)

at com.sap.sld.api.wbem.cim.ElementName.<init>(ElementName.java:28)

at com.sap.security.wd.destinations.helper.BackendSystemManager.isPropertyInModel(BackendSystemManager.java:391)

at com.sap.security.wd.destinations.helper.BackendSystemManager.isPropertyInLegacyModel(BackendSystemManager.java:371)

at com.sap.security.wd.destinations.helper.UIHelper.setVisibility(UIHelper.java:34)

at com.sap.security.wd.destinations.rfc.MiscPropsView.wdDoModifyView(MiscPropsView.java:182)

at com.sap.security.wd.destinations.rfc.wdp.InternalMiscPropsView.wdDoModifyView(InternalMiscPropsView.java:512)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:94)

at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:746)

at com.sap.tc.webdynpro.progmodel.window.ViewController.modifyView(ViewController.java:254)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:432)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:438)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:438)

at com.sap.tc.webdynpro.clientserver.phases.ModifyViewPhase.execute(ModifyViewPhase.java:69)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:57)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:899)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:871)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:355)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process

Edited by: Venkatarao Daggupati on Nov 30, 2011 7:26 AM

[sivakumar_kilari3]

Hi ,

#Error#com.sap.i18n.SAPTimeZoneInfo# #BC-I18-JAV#tc_i18nsaptimezone#C0000AE03A2C00A600000003000003E6#905601150000000004#sap.com/tc_lmitsam_uimainframe~wd#com.sap.i18n.SAPTimeZoneInfo.SAPTimeZoneException#TEST1#3##

Please check this below note.

Note 1604058 - error message CreateSAPTimeZone + failed. Reason:

Thanks

Siva

[Former Member]

I have already gone through this note..but no luck