SAP Lumira Server 1.18 - Error While creating visualization
Hi,
I installed Lumira Server 1.18 and configured as mentioned in the blogs below.
Simplified SAP Lumira Server Feature Configuration
I created following users with the roles mentioned -
LSADMIN - sap.bi.admin::BI_CONFIGURATOR and sap.bi.admin::BI_ADMIN
LUMIRADEV - sap.bi.common::BI_DATA_ANALYST
LUMIRADEMO - sap.bi.common::BI_DATA_CONSUMER
I did the configuration in SAP Fiori mentioned in the blog with LSADMIN id. I also had Technical user id LUMIRATECH with sap.bi.common::BI_TECH_USER role which was used for configurations in Fiori. It was successful. Please see the screenshot below.
After that I logged on to SAP Lumira Server Launchpad (http://<SERVER>:80<INSTANCE>/sap/bi/launchpad) with LUMIRADEV user. I acquired the dataset from excel. But when I tried to create visualization post successful acquisition, I am getting below error on dropping any dimension/measure on to chart.
Please help. Do I need to give any additional rights to LUMIRADEV?
Thanks,
Abhijit
Hi Henry,
We have SAP HANA SPS 08 Database Revision 82.
Are there any additional authorizations required for LUMIRADEV user (user which is used for Lumira Server). Please note I am able to publish stories and data sets created on top of HANA Online connection from Lumira Desktop and I am able to access, edit Stories as well as create visualization from published data set on Lumira Server. I suspect this is an issue with authorization.
Appreciate your help.
Thanks,
Abhijit
Similar Messages
-
Error while creating Visualization
Hi,
Using Excel spreadsheet(Dataset) created Charts, But not able to create Visualization or Custom Visualization on this dataset or charts.
Regards
HarishHi,
Thanks for Reply.
Yah in Explorer Tab: After clicking Create Visualization Button.
Now am getting Error #2032, still i can view Visualization with incorrect data (it is using Template data Ex: USA, Japan, Germany etc)
Regards
Harish
Edited by: Harish Ranga on May 13, 2011 2:15 PM -
Error while creating request list Unable to detect the SAP system directory
We are upgrading SAP BW (NW 7.0 EHP1) to SAP BW (NW 7.3)
source OS: Windows 2008 R2, source DB: MSSQL server 2008 R2 SP1 CU3
I had started the upgrade by running: STARTUP.BAT
I had started the DSUGui on the server (CI / DB on the same server) from: D:\usr\sap\BP1\upg\sdt\exe\DSUGui.bat
I ran both programs (run as administrators).
Once SAP Gui connects and was able to create userid/ password and when ready to start the initialization phase (click next)
gives me the error
Error while creating request list - see preceeding messages. Unable to detect the SAP system directory on the local host
I had tried STARTUP.BAT "jce_policy_zip=Z:\export-import\downloads\jce_policy-6' and still the same error.
I had started DSUGui.bat with trace and the trace file contents are
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[D:
usr
sap
bp1
upg
sdt
trc
server.trc]/>
<!PATTERN[server.trc]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jan 11, 2012 10:14:58 AM [Error]: com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:102) [Thread[ExecuteWorker,5,main]]: Execution of command com.sap.sdt.engine.core.communication.CmdActionEvent@376433e4 failed: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
Jan 11, 2012 10:14:58 AM [Error]: com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:103) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
Jan 11, 2012 10:14:58 AM [Error]: com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:103) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
Jan 11, 2012 10:14:58 AM [Error]: com.sap.sdt.engine.core.communication.CmdActionEvent [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
at com.sap.sdt.dsu.service.req.DSURequestListBuilder.persistSystemInfo(DSURequestListBuilder.java:277)
at com.sap.sdt.dsu.service.DSUService.createRequestList(DSUService.java:338)
at com.sap.sdt.dsu.service.controls.DSUListener.actionNext(DSUListener.java:144)
at com.sap.sdt.dsu.service.controls.DSUListener.actionPerformed(DSUListener.java:67)
at com.sap.sdt.server.core.controls.SDTActionListener$Listener.actionPerformed(SDTActionListener.java:46)
at com.sap.sdt.engine.core.communication.CmdActionEvent.actOnEvent(CmdActionEvent.java:43)
at com.sap.sdt.engine.core.communication.CmdEvent.execute(CmdEvent.java:69)
at com.sap.sdt.engine.core.communication.ExecWorker.handleCmd(ExecWorker.java:36)
at com.sap.sdt.engine.core.communication.AbstractWorker.run(AbstractWorker.java:93)
I could not get Upgrade started. Any help is appreciated
Thanks
PrathapDid you get this solved?
I have the same problem -
LDAP:Mapping Error while creating as per SAP Note No. 784697
Hi,
While configuring LDAP connection for Creating Users in Active
Directory from Employee Data Stored in SAP HR, we are encountering
error while mapping Structure as per the document provided at Link -
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40b0d690-0201-0010-2c86-9092407528c3
(Doc attached in attachment section also).
Error encountered is - "The filter mappings are not suitable for the
LDAP application USER", while we are mapping structure field as
provided.
Steps for Reconstruction
1. Go to transaction - LDAPMAP.
2. Go to EDIT Mode - Select LDAP server, and double click on Mapping.
3. Enter the mapping fields as provided in attached document at Page
No.17, figure No.7.
4.After entering all the mapping fields and when click on "Back"
button, an error message occured as below (error doc attached) -
"The filter mappings are not suitable for the LDAP application USER"
please let me know.Why the error had encountered.Hi Chiranjeevi ,
use the below thread to solve your issue ,
LDAP and LDAPMAP - Mapping fields
B&R,
Saravana.s -
Error While Creating Windows Server 2008 SP2 32-BIT Virtual Machine
I am facing an error while creating a Virtual Machine on the Cloud. The Error is below:
Error (610)
Virtual Machine Manager was unable to find a value for the required Sysprep parameter ProductKey.
Recommended Action
Add the missing Sysprep parameter either to the answer file or to the operating system configuration, and then try the operation again.
My Template does not have the Product Key defined. The OS is Windows Server 2008 SP2 32-BIT. Is defining Product Key absolutely necessary? I have other Templates for other Operating Systems and they are working fine. Only facing problem
with this.
Any help would be appreciated.In the SCVMM world a 'template' is composed of the following: a VHD with an OS that has been generalized (sysprep), virtual hardware profile (settings), and an OS profile.
The OS profile is required to have a product key. A MAC activation key at the minimum. But the key is required.
If you deploy a VM from a VHD, the same customization assumptions are not at play. Which is why it succeeds. (there is no template in this case, there is also no requirement that the OS in the VHD be sysprep'd).
SCVMM has rules. And lots of things don't make sense until you begin to understand them and play within them. (I am not saying that the SCVMM rules are a good thing, just saying they exist)
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat. -
Error while creating and opening a ERP sales order in SAP CRM
Hi,
I am getting an error while creating or opening a ERP sales order from SAP CRM.
"Creation of the ERP Transaction failed" this is the error i'm getting while creating. when i try to open an existing sales order I'm getting a dump.
Attached the dump screen shot. From the dump analyasis it seems the transactions are not loaded through LORD framework.
The RFC connection seems to fine as i have tested accessing an ECC RFC FM through a sample program and its successful..
please help..
Thanks
KrishnaHello Krishna,
Did you get a solution to this? I have the same dump message.
As a matter of fact, we already use ERP Sales Order and it works fine. But I have recently configured a new sales order document type, and the dump occurs only for this new Z order type.
Thanks a lot,
Luis. -
Authentication error while creating directory server through dscc
Hi
I am getting authentication error while creating a DS from dscc on windows box on a linux RHEL4 server.However I do not get an authentication issue when creating a ds on solaris box from same dscc.
Can someone guide me what might be the issue?
Thanks
AartiHi,
Please check there is no firewall issue between your windows client to Linux directory server. You may be able to login via dscc but when you create DS instance, your dscc agent port might be an issue not able to talk to Directory server because of firewall. -
Error while creating SC: Internal Error - termination type TH_RES_FREE
Hi I encountered this error while creating a SC. All attributes for this user are maintained and the "check user" transaction does not give any error.
Amol Mate
Error when processing your request
What has happened?
The URL http://punhjwsapsrm:8000/sap/bc/gui/sap/its/bbpsc02/! was not called due to an error.
Note
The following error text was processed in the system SSS : Internal Error
The error occurred on the application server PUNHJWSAPSRM_SSS_00 and in the work process 1 .
The termination type was: TH_RES_FREE
The ABAP call stack was:
Function: B40B_READ_TABLE of program SAPLBBP_BD_DRIVER_40B
Function: META_READ_TABLE of program SAPLBBP_BD_META_BAPIS
Form: LOCATIONS_READ of program SAPLBBP_ATTR_F4
Function: BBP_ATTR_F4_SLOC_PPOMA of program SAPLBBP_ATTR_F4
Form: STG_LOC_GET_FOR_LOCATION of program SAPLBBP_SC_APP
Form: STG_LOC_GET of program SAPLBBP_SC_APP
Form: LOCATION_STG_LOC_GET of program SAPLBBP_SC_APP
Form: USER_ATTRIBUTES_GET of program SAPLBBP_SC_APP
Form: SC_INIT of program SAPLBBP_SC_APP
Function: BBP_SC_APP_EVENT_DISPATCHER of program SAPLBBP_SC_APP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SSS in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server PUNHJWSAPSRM_SSS_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server PUNHJWSAPSRM_SSS_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http-c:100-u:PTEST -l:E-s:SSS-i:PUNHJWSAPSRM_SSS_00 -w:1-d:20051121-t:171904-v: TH_RES_FREE-e:Internal Error
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework TeamHi Amol,
First of all the sicf transaction is to be used only if you use the internal ITS.
Now you have to put an external breakpoint in the source code of the ABAP Program or FM you want to debug , one of these in your case :
Function: B40B_READ_TABLE of program SAPLBBP_BD_DRIVER_40B
Function: META_READ_TABLE of program SAPLBBP_BD_META_BAPIS
Form: LOCATIONS_READ of program SAPLBBP_ATTR_F4
Function: BBP_ATTR_F4_SLOC_PPOMA of program SAPLBBP_ATTR_F4
Form: STG_LOC_GET_FOR_LOCATION of program SAPLBBP_SC_APP
Form: STG_LOC_GET of program SAPLBBP_SC_APP
Form: LOCATION_STG_LOC_GET of program SAPLBBP_SC_APP
Form: USER_ATTRIBUTES_GET of program SAPLBBP_SC_APP
Then launch the transaction in IE, once the program reaches a breakpoint, you'll get the ABAP debuger in IE.
Regards.
PS: if it doesn't work, put the parameter ~generatedynpro in BBPGLOBAL service to have it applied to all BBP transactions
Vadim -
Error while creating setuppackage
Hi All,
I am getting the following error while creating a setup package.
0010 tc.mobile.admin.bl Creation of virtual mi instance failed.
Please suggest what can be the reason for the same.
Also i have certain queries while creating a setup package for Mobile 2005 device.
1.While creating a SDA file in the Operating System tab i m not able to see any option for mobile 2005 device.It shows only WINCE/PPC 2002.Can i use this one or do we have to make some settings or something.
2.I have a MI25Tom_en.CAB file for Mobile framework.But i wanted to integrate it with the trustore and some mobileengine config parameters like syncpassword handling option = loca.What i have to do for the same.If i have a cab file with all these integratd can i use that one or server will by itself put the trustore while generating a SDA file.
3.We have to create two components one for Framework and second for install sequence amd we have to install onle creme on the PDA as i read somewhere.Do i need to put JSSE1-0-3_01.CAB somewhere while defining the mobile component or JSSE also i have to install on the PDA before running the setup.cab on PDA.
Please suggest
Thanks
Regards
Devendra PhateHi Devendra,
If you have downloaded Framework sda from SAP market place.
Then generally the name for the MobileComponent is MobileEngineJsp or AWT.
You can also check the name of MobileComponent in MCD.xml by opening sda->mobile-description->mcd.xml.
Search with this name and version in NWA , if search fails then there is some problem with reload or deployment process.
Check the following.
Login to the ABAP system.
Launch transaction sm59. Create new TCP/IP type RFC connection.
Enter some name for the RFC destination. Give program ID = MEMGMT_MOBILE_CONTAINER_SYNC.
Enter appropriate gateway service and host (same as you entered in Visual Admin). Test Connection.
Launch transaction sm30.
Open table MEMGMT_J2EE_DEST . Create a new entry. Enter the name of RFC destination that you created in SM59 in RFC Destination field. Enter some description.
Save the data.
Regards,
Satyendra -
Portal runtime error while creating users in portal content administrator
I am getting this error while creating new users in portal.
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.user_administration/com.sap.portal.user_admin_ws/com.sap.portal.user_management/com.sap.portal.createNewUser/com.sap.portal.createNewUser
Component Name : com.sap.portal.usermanagement.admin.CreateNewUser
com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z.
Exception id: 03:51_27/08/08_0028_7431850
See the details for the exception ID in the log file
any help is appreciated...log file look something like
this
2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception in PortalRequestManager.dispatchRequest without timeout
[EXCEPTION]
#1#java.lang.NoSuchMethodError: com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z
at com.sap.security.core.admin.util.checkEmail(util.java:110)
at com.sap.security.core.admin.UserBean.checkFieldValidity(UserBean.java:695)
at com.sap.security.core.admin.UserBean.checkUser(UserBean.java:591)
at com.sap.security.core.admin.UserAdminLogic.performUserModify(UserAdminLogic.java:3226)
at com.sap.security.core.admin.UserAdminLogic.executeRequest(UserAdminLogic.java:552)
at com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent.doContent(UserAdminComponent.java:71)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(AccessController.java:241)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:758)
#1.5#001125A6576A008C00000015000550E2000455943BAE9D63#1219995051656#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#197794##irconepd_EPD_7431850#Administrator#f4d062d0759411ddb89b001125a6576a#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception ID:01:00_29/08/08_0043_7431850
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.user_administration/com.sap.portal.user_admin_ws/com.sap.portal.user_management/com.sap.portal.userSearch/com.sap.portal.userSearch
Component class : com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent
User : Administrator
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(AccessController.java:241)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:758)
Caused by: java.lang.NoSuchMethodError: com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z
at com.sap.security.core.admin.util.checkEmail(util.java:110)
at com.sap.security.core.admin.UserBean.checkFieldValidity(UserBean.java:695)
at com.sap.security.core.admin.UserBean.checkUser(UserBean.java:591)
at com.sap.security.core.admin.UserAdminLogic.performUserModify(UserAdminLogic.java:3226)
at com.sap.security.core.admin.UserAdminLogic.executeRequest(UserAdminLogic.java:552)
at com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent.doContent(UserAdminComponent.java:71)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 7 more -
Error while creating webi on BEx query
Hello,
I will appreciate your help on this matter.
I created a BICS connection and published it in the repository successfully. I then logged on to BI launch pad and tried to create webi report on top of BEx query but getting a following error.
I am not sure what that error is all about , may be something to do with Java. I would appreciate if you advise your help on this.
Regards.
==============================================================================
HERE IS AN ERROR MESSAGE:
java.util.concurrent.ExecutionException: com.google.protobuf.UninitializedMessageException: Message missing required fields: bytesValue
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at javax.swing.SwingWorker.get(Unknown Source)
at com.sap.webi.ui.dialog.bex.OpenBexPanel.endFetchNode(OpenBexPanel.java:801)
at com.sap.webi.ui.dialog.bex.OpenBexPanel.propertyChange(OpenBexPanel.java:1009)
at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
at javax.swing.SwingWorker$SwingWorkerPropertyChangeSupport.firePropertyChange(Unknown Source)
at javax.swing.SwingWorker$SwingWorkerPropertyChangeSupport$1.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source)
at sun.swing.AccumulativeRunnable.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.Dialog$1.run(Unknown Source)
at java.awt.Dialog$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Unknown Source)
at com.jidesoft.dialog.StandardDialog.show(Unknown Source)
at java.awt.Component.show(Unknown Source)
at java.awt.Component.setVisible(Unknown Source)
at java.awt.Window.setVisible(Unknown Source)
at java.awt.Dialog.setVisible(Unknown Source)
at com.sap.webi.toolkit.ui.dialog.GenericDialog.setVisible(GenericDialog.java:116)
at com.sap.webi.ui.dialog.bex.OpenBexDialog.setVisible(OpenBexDialog.java:94)
at com.sap.webi.ui.data.BexQueryDataSourceProvider.createDataSourceInfo(BexQueryDataSourceProvider.java:85)
at com.sap.webi.ui.context.managers.DataManager.createDataSourceInfo(DataManager.java:277)
at com.sap.webi.ui.tasks.workflows.CreateDataSourceInfoUITask.doneProcess(CreateDataSourceInfoUITask.java:127)
at com.sap.webi.toolkit.ui.tasks.WebITask.done(WebITask.java:123)
at javax.swing.SwingWorker$5.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source)
at sun.swing.AccumulativeRunnable.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.google.protobuf.UninitializedMessageException: Message missing required fields: bytesValue
at com.google.protobuf.AbstractMessage$Builder.newUninitializedMessageException(AbstractMessage.java:531)
at com.sap.sl.olap.sapbw.protobuf.generated.SapbwService$msgBytesValue$Builder.build(SapbwService.java:567)
at com.sap.sl.sdk.olap.sapbw.service.SapBwBrowsingServiceImpl.processDoIt(SapBwBrowsingServiceImpl.java:299)
at com.sap.sl.sdk.olap.sapbw.service.SapBwBrowsingServiceImpl.processInvocation(SapBwBrowsingServiceImpl.java:246)
at com.sap.sl.sdk.olap.sapbw.service.SapBwBrowsingServiceImpl.processOpenSession(SapBwBrowsingServiceImpl.java:229)
at com.sap.sl.sdk.olap.sapbw.service.SapBwBrowsingServiceImpl.openSession(SapBwBrowsingServiceImpl.java:59)
at com.sap.webi.ui.dialog.bex.ExpandRepositoryItemWorker.getBrowsingSession(ExpandRepositoryItemWorker.java:63)
at com.sap.webi.ui.dialog.bex.ExpandRepositoryItemWorker.doInBackground(ExpandRepositoryItemWorker.java:40)
at com.sap.webi.ui.dialog.bex.ExpandRepositoryItemWorker.doInBackground(ExpandRepositoryItemWorker.java:15)
at javax.swing.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at javax.swing.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)Henry,
Thanks for yor detailed answer, I am looking into it and working with an admin people to resolve this issue. will post here if able to solve it.
In the meanwhile I am getting another similar kind of error "WHILE CREATING WEBI ON TOP OF UNIVERSE" and wondering if both these error are of similar nature, Will appreciate your help and advice on this.
Here is an error and its details:
========================
[[error.RepositoryException] 0] <RepositoryImpl.getInternalResourceID() : can't find InfoObject of cuid M06604sAAW5bAJsAeAAAVVgAAgqWJIcAAAA>,<com.businessobjects.mds.repository.exceptions.RepositoryException: [[error.RepositoryException] 0] <RepositoryImpl.getInternalResourceID(): can't find InfoObject of cuid M06604sAAW5bAJsAeAAAVVgAAgqWJIcAAAA>> (WIS 00000)
DETAIL:
==========
com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: [[error.RepositoryException] 0] <RepositoryImpl.getInternalResourceID() : can't find InfoObject of cuid M06604sAAW5bAJsAeAAAVVgAAgqWJIcAAAA>,<com.businessobjects.mds.repository.exceptions.RepositoryException: [[error.RepositoryException] 0] <RepositoryImpl.getInternalResourceID(): can't find InfoObject of cuid M06604sAAW5bAJsAeAAAVVgAAgqWJIcAAAA>>
at com.businessobjects.sdk.core.exception.ExceptionBuilder.make(ExceptionBuilder.java:144)
at com.businessobjects.sdk.core.exception.ExceptionBuilder.make(ExceptionBuilder.java:101)
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.afterProcessing(CommonRequestHandler.java:127)
at com.businessobjects.sdk.core.server.internal.AbstractServer.processIt(AbstractServer.java:178)
at com.businessobjects.sdk.core.server.internal.AbstractServer.process(AbstractServer.java:133)
at com.businessobjects.sdk.core.server.internal.InstanceServer.process(InstanceServer.java:94)
at com.sap.sl.sdk.services.util.ServerRequestProcessor.processServerRequest(ServerRequestProcessor.java:49)
at com.sap.sl.sdk.datasource.strategy.BuiltInDataSourceStrategyImpl.addDataProvider(BuiltInDataSourceStrategyImpl.java:100)
at com.sap.sl.sdk.workspace.service.WorkspaceServiceImpl.addDataProvider(WorkspaceServiceImpl.java:77)
at com.sap.sl.sdk.workspace.service.WorkspaceServiceImpl.addDataProvider(WorkspaceServiceImpl.java:60)
at com.sap.webi.ui.context.managers.DataManager.addDataProviderFromDataSourceInfo(DataManager.java:395)
at com.sap.webi.ui.tasks.workflows.AddDataProviderUITask.doIt(AddDataProviderUITask.java:106)
at com.sap.webi.ui.tasks.workflows.AddDataProviderUITask.doIt(AddDataProviderUITask.java:19)
at com.sap.webi.toolkit.ui.tasks.WebITask.doInBackground(WebITask.java:113)
at javax.swing.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at javax.swing.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.businessobjects.sdk.core.server.ServerException: [[error.RepositoryException] 0] <RepositoryImpl.getInternalResourceID() : can't find InfoObject of cuid M06604sAAW5bAJsAeAAAVVgAAgqWJIcAAAA>,<com.businessobjects.mds.repository.exceptions.RepositoryException: [[error.RepositoryException] 0] <RepositoryImpl.getInternalResourceID(): can't find InfoObject of cuid M06604sAAW5bAJsAeAAAVVgAAgqWJIcAAAA>>
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.newServerException(CommonRequestHandler.java:260)
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.createAllServerExceptions(CommonRequestHandler.java:238)
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.afterProcessing(CommonRequestHandler.java:121)
... 18 more -
Error while creating the HTTP client with destination GB_DPSRetrieve
Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
KishoreHi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar -
Error While Creating TS in SLD Manually
Hi Experts,
I Got the Following Error While Creating TS as Web AS ABAP For R/3 System
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
... 27 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Fri May 18 20:03:14 IST 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en
Time of Failure Wed Jun 13 12:17:00 IST 2007 (Java Time: 1181717220451)
Web Dynpro Code Generation Infos
sap.com/tcsldwd~main
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~landscape
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/tcsldwd~businesssystem
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~technicalsystem
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
sap.com/tcsldwd~softwarecatalog
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~namereservation
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
Detailed Error Information
Detailed Exception Chain
java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Can Any Body Please Answer to This Thread. So that I Can Able to go-a- head
Regards
KhannaHi Vijaya,
Here We Are Using PI7.0.
Opened SLD Page.
Clicked on TS ->>>New TS>>Slect Web AS ABAP.
Entered<b> Web AS ABAP Name (SID),,Installation Number,,Database Host Name</b>
Click on Next.
Entered <b>Message Server Port (sapmsIDE),,,Instance Number</b>
Click on Next. Here The Above Mentioned Error Came With Pop-up Window.
Please Help Me
Regards
Khanna -
Error While Creating Iview?
Hi Everyone,
I Got the error while creating iview in the portal.
Just i went Portal COntent->Folder->New->Iview
500 Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
The initial exception that caused the request to fail, was:
java.lang.NoClassDefFoundError
at com.sap.security.core.server.csi.URLChecker._isValid(URLChecker.java:289)
at com.sap.security.core.server.csi.URLChecker.isValidURL(URLChecker.java:1202)
at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.checkURL(AbstractURLGenerator.java:697)
at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.applyWSRPTemplate(AbstractURLGenerator.java:1235)
at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.computeWebResourcePath(AbstractURLGenerator.java:945)
at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.computeWebResourceURL(AbstractURLGenerator.java:1078)
at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.getWebResourceURL(AbstractURLGenerator.java:223)
at com.sap.tc.webdynpro.services.sal.url.api.WDURLGenerator.getWebResourceURL(WDURLGenerator.java:377)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:407)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks
SubbaraoHi Subbarao,
Is this a new installation. Check whether all post installation tasks (like patch upgrade) are completed.
Also try restarting the server.
Regards.
Santhosh -
Error while creating OLAP connection in IDT
Hi friends,
I am facing error while creating OLAP connection in IDT (BO 4.1 sp2)
I am using sql server 2012.In the screen shots you can observe server name and user name of the Sql server
I am creating OLAP connection to connect CUBE
Check the screen shots for the error
Plz help me
Here you can see the server name and user name
While creating OLAP connection I gave these credentials
This is the error I am gettingHi..
To create connection and access the BW data, developer must have the password. and while create connection using Authentication Mode: Single Sign On, need to loin the username has pattern <SID~client/SAP userid>,
User Name: SID~client/SAP userid
Password for the SID,
Authentication as SAP.
Plese find the below link for more info: http://scn.sap.com/community/semantic-layer/blog/2014/06/19/pre-requisite-authorizations-in-sap-bw-side-before-develop-the-universe
Maybe you are looking for
-
Copy Open sales oder from one DB to Other DB
Hi Expets, Can any one help me how to copy Open Sale Order from one data to another Database which exact replica(Both are Same configration) Kathi.
-
Error in converting SQL 2014 Trial to Full version using VLKey
Hi, I am currently trying to upgrade my SQL 2014 evaluation version to the full version. I have purchased a Volume License for SQL Server 2014 Server/CAL and have extracted the product key from the ISO File. I have verified this product key with the
-
Can I video capture 'live action' from Viewer screen ...
Can I capture 'live action ' video as it appears on the 'viewer screen' in iMovie as I move the cursor across the 'source video' clips. Does iMovie allow me to record this 'action' to hard drive ?? ... Suggestions greatly appreciated.
-
SAP Query in ECC 6 Upgradation
Hi All , I am working in an ECC 6 Upgradation project , upgrading from 4.6 C to ECC 6. Somebody told me , Query cann't be coppied from 4.6 C to ECC 6. Is it true ? If so what is the alternative ? Thanks in advance. Regards Srikanta
-
I have a column called b_month and I its not an index column. But, in my query I need to apply a where clause on that column with some conditions like this. and extract(month from b_month)=11 and extract(year from b_month)=2007 The table has approx 4