RFC Error While Creating Technical System in SLD As Web AS ABAP
Hi Experts,
I was Posted This Thread in Most of the Modules like ABAP, Exchange Infrastructure.
But there is No Such Right Answers . So Finally I Got Idea to Post it in SAP NetWeaver Administrator Module.
For Creating a TS for Web AS ABAP For R/3 in SLD Automatically I Followed these Steps.
Log on to R/3 System
1) Go to SLDAPICUST TC
2)Entered Host name of the XI System ,Port, User As PIAPPLUSER, and Master PWD.
And Checked Primary Check Box.Saved
3) Goto RZ70 TC
4) Entered Host name And Gateway Service of XI System.And Activated
5) Clicked on Start Data Collection.
Here I Got the Error As <b>"RFC call failed : Error opening an RFC connection"</b>
Then
1) If I Executed SLD_NUC in SM59 With SAP XI Details Means It's giving Error Like as Follows "TheGetT1002 : error ( Msg - 10 not found )"
If I Executed SLD_NUC in SM59 With SAP R/3 Details Means It's giving Error Like as Follows "program SLD_NUC not registered"
Please let me Know the Solution
<b>Points will be Given If the Problem Is Solved</b>
Regards
Khanna
Hi Tanuj,
When I Executed SLDCHECK in R/3 System it's Giving The Following Wrror.
Exchange Infrastructure: Test LCR Connection
Properties of RFC destination SAPSLDAPI
RFC host: %%RFCSERVER%%
program id: SAPSLDAPI_NONUNICODE
gateway host: SAPPLMIDES
gateway service: sapgw00
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
Error opening an RFC connection.
Summary: Connection to SLD does not work
=> Check SLD function and configurations
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host: %%RFCSERVER%%
program id: LCRSAPRFC_NONUNICODE
gateway host: sapplmides
gateway service: sapgw00
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
Error opening an RFC connection.
Please Help me....
Regards
Khanna
Similar Messages
-
Error while creating Technical System
Hi
i am creating Technical system in SLD. I gave all inputs for host name, Instance, License correctly.
When i press next, It is throwing this error. Do anyone have any idea about this.
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; InfoPath.1; .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: Sat Oct 14 19:38:14 GMT+05:30 2006
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 Sat Nov 11 14:04:06 GMT+05:30 2006 (Java Time: 1163234046750)
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)
Thanks in Advance
Vijay RahejaHI Michal Krawczyk,
Thanks for your response. i am working on XI 7.0 and when i go to SLD-> Adminitsrtion-> SLD Data Supplier. There i tried to add SLD CLient.
It is asking me for :
-URL of target SLD system, e.g. http://host:port/
-User
-Password.
What should i give here. WHat will be port for R/3 system to which i want to connect.
Just to add: I have already created Technical system for R/3(CLient 600). I added this through SLD only. But now it is giving error for Technical SYstem for same R/3(Clinet 812).
Thanks,
Vijay Raheja -
Error While Creating Technical System for SNC
Hi There,
I am trying to create technical system for SNC in SLD, I am not able to seee SNC as a s/w component/product in the list.
when I checked the list of components in SLD, I found SNC is there under product "SCMSNC" but this product is not in the list of products.
Please help me how I can get "SCMSNC" product in the product list.
Thanks,
NishantCan you please explain it little bit clearly?
I think you first create product, then SWC and then try to create Technical system.
While you will create the Technical system, in the last step it will ask you for installed products.
There you can specify ur product.
Thanks,
Hetal -
Error while importing technical systems in SLD
Hi all,
I was importing technical systems from one SLD to another by Export-Import.
While importing the content i got an error 92 out of 93 objects successfully imported.
for one object following error is shown.
CIM_ERR_FAILED: Instance referenced in role Dependent of association SAP_BCSystemJ2EEEngine does not exist:
Antecedent: SAP_BCSystem.CreationClassName="SAP_BCSystem",Name="IRX.SystemNumber.0020312094.SystemHome.prdcixi"
Dependent: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="IRX.SystemHome.prdcixi".
SAP_BCSystemJ2EEEngine.Antecedent=ref"SAP_BCSystem.CreationClassName=\"SAP_BCSystem\",Name=\"IRX.SystemNumber.0020312094.SystemHome.prdcixi\"",Dependent=ref"SAP_J2EEEngineCluster.CreationClassName=\"SAP_J2EEEngineCluster\",Name=\"IRX.SystemHome.prdcixi\""
After that i continued with Business sytems which was sucessfully imported.
Will there be an issue because of the above error? and how to resolve this error?
Regards,
PriyaRead the note listed below, which addresses your issue.
Link: [Note 1178572|https://service.sap.com/sap/support/notes/1178572] -
CIM_ERR_ALREADY_EXISTS: Error while creating Business System
Hi,
I am getting following error while creating Business System in SLD, the Technical System is already created from RZ70 transaction in the IDES system
Error Creating business system: CIM_ERR_ALREADY_EXISTS: Instance already exists://inbbssun01/sld/active:SAP_LogicalALESystem.CreattionClassName="SAP_LogicalALESystem", Name = "LSIDES800.SystemName.800.SystemName.IDS.SystemNumber.0020224902.SystemHome.idesecc"
Thanks,
RPHi,
This error means that a business system with this name(or associated with this technical system) is already there in SLD.
You need to check that before you try creating it (might be someone else have created it before)
Updated
If you have created and deleted a business system and then trying to recreate one then you need to delete all the instance of it from Content Management (in SLD)
Regards
Suraj
Edited by: S.R.Suraj on Nov 9, 2009 12:34 AM -
Regarding error in creating technical system of type WEB AS ABAP
while creating technical system of WEB AS ABAP i have few doubts
1) host name:(do we have to give sap system name or xi system name)
and while creating business system for this technical system am not able to find the option under RELATED INTEGRATION SERVER i.e xi3/sxi what ever it may be,so am facing very difficulty while creating communication channel and not able to select the integration engine under the ADAPTER ENGINE ,so please provide me suitable solution with screen shoits if possible ,it very urgent for mepls check this
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
as per ur doubt
1. <i>host name</i>:; sap system (can find under system status info-->database of R/3)
2. <i>SId is system status</i>->database>name (3) characters
3.<i>while creating business system for this technical system am not able to find the option under RELATED INTEGRATION SERVER</i>--as fra as this info that is there when u follow the wizard of creating Business system , also did u select business system role as application system name then probly u can get the related server name ,make sure ur technical system is created well
<i></i> -
Portal Runtime Error while creating new system in portal content
Hi
Can anyone solve my problem, i am geting error while creating new system in p ortal content
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log fileHi,
Check this link for creating system object
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
Regards
Arun -
RUNTIME ERROR WHILE CREATING NEW SYSTEM IN EP6
Hi
Can anyone solve my problem, i am geting error while creating new system PORTAL FOR to connect biw 3.5 system
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file
thanks in advance
Rockhi,
check the log file and let me the the error.
manish -
Error while creating return order(Complaint) in IC web client
Hi SAP Experts,
I am getting following Error while creating return order(Complaint) in IC web client.
Error when processing your request
What has happened?
The URL http://sapcrd.comfort.com:8000/sap/bc/bsp/sap/crm_ic/default_delta.do was not called due to an error.
Note
The following error text was processed in the system CRD : Exception condition "NON_EXISTING_HANDLE" raised.
The error occurred on the application server sapcrd_CRD_00 and in the work process 2 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Function: PRC_PD_HEAD_ADD_COND of program SAPLPRC_PRICING_API
Function: CRM_PRIDOC_UPDATE_EC of program SAPLCRM_PRIDOC_COM_EC
Form: EXECUTE_CALLBACKS_PLANNED of program SAPLCRM_EVENT_OW
Function: CRM_EVENT_SET_EXETIME_OW of program SAPLCRM_EVENT_OW
Function: CRM_ORDER_COMPLETE_SINGLE_OW of program SAPLCRM_ORDER_OW
Function: CRM_ORDER_MAINTAIN_SINGLE_OW of program SAPLCRM_ORDER_OW
Function: CRM_ORDER_MAINTAIN_MULTI_OW of program SAPLCRM_ORDER_OW
Function: CRM_ORDER_MAINTAIN of program SAPLCRM_ORDER_API
Method: IF_EX_ORDER_SAVE~PREPARE of program ZCL_IM_PRICE_ADJUSTMENT=======CP
Method: IF_EX_ORDER_SAVE~PREPARE of program CL_EX_ORDER_SAVE==============CP
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 CRD 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 sapcrd_CRD_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 2 in transaction ST11 on the application server sapcrd_CRD_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: 330 -u: VORUSX -l: E -s: CRD -i: sapcrd_CRD_00 -w: 2 -d: 20080324 -t: 021723 -v: RABAX_STATE -e: RAISE_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Maximum points will be awarded for useful information.
Thanks,
RonyHi,
I notice there is a Z class being called.
Method: IF_EX_ORDER_SAVE~PREPARE of program ZCL_IM_PRICE_ADJUSTMENT=======CP
You should check this customized class.
Cheers,
cady. -
Error while creating SOURCE SYSTEM
Hi All,
I have a problem while creating Source System to a Solman syatem configured with BW content. I have configured few some source systems already in the same Solman System.The system shows the following error, previous to this i get the message a "generating connection to the source system"
<b>Error in source system RXX_100
Message no. RSAR502
Diagnosis
With Remote Function Call to system RXX_100 error Screen output without connection to user. ccurred.
Procedure
Remove the cause of the error.</b>
Kindly provide me suggestions and DOCS related to the same.
Suitable points will be awarded for replies.
Expecting your kind reply,
VineethHi ,
In SCC4 the source client should not set as production when creating the source system connection between two systems.Please check below SAP note
973555 - System must be open for creating/connecting source systems
Thanks,
Shanaka -
Error while creating MDM system on Portal
Hi All,
I am trying to create MDM system in EP. MDM is 5.5 SP06. EP is 7.0 . We have upgraded the MDM sca files on Portal from SP05 to SP06.
While creating the system , after entering the server, we are getting the following error.
com.sap.mdm.internal.protocol.manual.ServerException: File failed a crc check
Please help
Regards
ShilpaHi Shilpa,
If this is your MDM build version 5.5.63.80 SP06. It means you are using MDM 5.5 SP06 Patch3 hotfix 80.
You need to find the Sca file of compatible with this version.
So they should be
- MDMJAVAAPI06_03.sca
- BPMDMAPPLN06_03.sca
- BPMDMTECHN06_03.sca
The hotfix number can slightly differ but the Support pack and patch number must match.
You need to follow this link:
http://service.sap.com/swdc
(download MDM support packages) Download>support packages and patches>entry by application
group>sap netweaver>sap mdm>sap mdm 5.5>Entry by component>Portal content
Then select which MDM portal content you want and check what is the version of those available sca files.
based on the availablity of the sca files you need to upgrade/downgrade or server.
As compatibility between the server version and sca files is a must for proper functioning.If its not possible to change your mdm server version then you can ask your Basis team to hunt the matching sca files for you.
Hope It Helped
Thanks & Regards
Simona Pinto -
No Installed Products while adding Technical System in SLD!
Hello,
I am trying to add Technical Systems in SLD. when I was at the point to select the software components, I am not seeing any installed products on the left side.
I already gave the ABAP system details in the previous screens, in this wizard.
Why is it that I am not seeing any installed products.
Thanks
SrinivasHi Jazz,
Here are the errors I am getting.
Import finished with 72 errors
Errors:
CIM_ERR_FAILED: CIM qualifier Alias is currently not supported by this implementation
QUALIFIER.DECLARATION Alias
CIM_ERR_FAILED: CIM qualifier BitMap is currently not supported by this implementation
QUALIFIER.DECLARATION BitMap
CIM_ERR_FAILED: CIM qualifier BitValues is currently not supported by this implementation
QUALIFIER.DECLARATION BitValues
CIM_ERR_FAILED: CIM qualifier Composition is currently not supported by this implementation
QUALIFIER.DECLARATION Composition
CIM_ERR_FAILED: CIM qualifier Counter is currently not supported by this implementation
QUALIFIER.DECLARATION Counter
CIM_ERR_FAILED: CIM qualifier Delete is currently not supported by this implementation
QUALIFIER.DECLARATION Delete
CIM_ERR_FAILED: CIM qualifier Deprecated is currently not supported by this implementation
QUALIFIER.DECLARATION Deprecated
CIM_ERR_FAILED: CIM qualifier DN is currently not supported by this implementation
QUALIFIER.DECLARATION DN
CIM_ERR_FAILED: CIM qualifier Expensive is currently not supported by this implementation
QUALIFIER.DECLARATION Expensive
CIM_ERR_FAILED: CIM qualifier Experimental is currently not supported by this implementation
QUALIFIER.DECLARATION Experimental
CIM_ERR_FAILED: CIM qualifier Gauge is currently not supported by this implementation
QUALIFIER.DECLARATION Gauge
CIM_ERR_FAILED: CIM qualifier Ifdeleted is currently not supported by this implementation
QUALIFIER.DECLARATION Ifdeleted
CIM_ERR_FAILED: CIM qualifier In is currently not supported by this implementation
QUALIFIER.DECLARATION In
CIM_ERR_FAILED: CIM qualifier Invisible is currently not supported by this implementation
QUALIFIER.DECLARATION Invisible
CIM_ERR_FAILED: CIM qualifier Large is currently not supported by this implementation
QUALIFIER.DECLARATION Large
CIM_ERR_FAILED: CIM qualifier MaxValue is currently not supported by this implementation
QUALIFIER.DECLARATION MaxValue
CIM_ERR_FAILED: CIM qualifier MinLen is currently not supported by this implementation
QUALIFIER.DECLARATION MinLen
CIM_ERR_FAILED: CIM qualifier MinValue is currently not supported by this implementation
QUALIFIER.DECLARATION MinValue
CIM_ERR_FAILED: CIM qualifier Nonlocal is currently not supported by this implementation
QUALIFIER.DECLARATION Nonlocal
CIM_ERR_FAILED: CIM qualifier NonlocalType is currently not supported by this implementation
QUALIFIER.DECLARATION NonlocalType
CIM_ERR_FAILED: CIM qualifier NullValue is currently not supported by this implementation
QUALIFIER.DECLARATION NullValue
CIM_ERR_FAILED: CIM qualifier Octetstring is currently not supported by this implementation
QUALIFIER.DECLARATION Octetstring
CIM_ERR_FAILED: CIM qualifier Out is currently not supported by this implementation
QUALIFIER.DECLARATION Out
CIM_ERR_FAILED: CIM qualifier PropertyUsage is currently not supported by this implementation
QUALIFIER.DECLARATION PropertyUsage
CIM_ERR_FAILED: CIM qualifier Provider is currently not supported by this implementation
QUALIFIER.DECLARATION Provider
CIM_ERR_FAILED: CIM qualifier Read is currently not supported by this implementation
QUALIFIER.DECLARATION Read
CIM_ERR_FAILED: CIM qualifier Schema is currently not supported by this implementation
QUALIFIER.DECLARATION Schema
CIM_ERR_FAILED: CIM qualifier Source is currently not supported by this implementation
QUALIFIER.DECLARATION Source
CIM_ERR_FAILED: CIM qualifier SourceType is currently not supported by this implementation
QUALIFIER.DECLARATION SourceType
CIM_ERR_FAILED: CIM qualifier Static is currently not supported by this implementation
QUALIFIER.DECLARATION Static
CIM_ERR_FAILED: CIM qualifier Syntax is currently not supported by this implementation
QUALIFIER.DECLARATION Syntax
CIM_ERR_FAILED: CIM qualifier SyntaxType is currently not supported by this implementation
QUALIFIER.DECLARATION SyntaxType
CIM_ERR_FAILED: CIM qualifier Terminal is currently not supported by this implementation
QUALIFIER.DECLARATION Terminal
CIM_ERR_FAILED: CIM qualifier TriggerType is currently not supported by this implementation
QUALIFIER.DECLARATION TriggerType
CIM_ERR_FAILED: CIM qualifier UnknownValues is currently not supported by this implementation
QUALIFIER.DECLARATION UnknownValues
CIM_ERR_FAILED: CIM qualifier UnsupportedValues is currently not supported by this implementation
QUALIFIER.DECLARATION UnsupportedValues
CIM_ERR_FAILED: CIM qualifier Write is currently not supported by this implementation
QUALIFIER.DECLARATION Write
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property ScheduledStartTime
CIM_Job
CIM_ERR_FAILED: Unknown qualifier Write found in property DeleteOnCompletion
CIM_JobSettingData
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_ConcreteJob: CIM_Job
CIM_ConcreteJob
CIM_ERR_FAILED: Unknown qualifier Write found in property EnabledDefault
CIM_EnabledLogicalElement
CIM_ERR_FAILED: Unknown qualifier Write found in property PrimaryOwnerName
CIM_System
CIM_ERR_FAILED: Unknown qualifier Write found in property PrimaryOwnerName
CIM_Service
CIM_ERR_FAILED: Unknown qualifier Gauge found in property AvailableSpace
CIM_FileSystem
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property array PowerManagementCapabilities
CIM_ComputerSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property NumberOfUsers
CIM_OperatingSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property FileSize
CIM_LogicalFile
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property PowerManagementSupported
CIM_LogicalDevice
CIM_ERR_FAILED: No such override property in superclass CIM_System: EnabledState
CIM_ApplicationSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property WorkingSetSize
CIM_Process
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_LogicalPort: CIM_LogicalDevice
CIM_LogicalPort
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_Processor: CIM_LogicalDevice
CIM_Processor
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_NetworkAdapter: CIM_LogicalDevice
CIM_NetworkAdapter
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_NetworkPort: CIM_LogicalPort
CIM_NetworkPort
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_OSProcess
CIM_OSProcess
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_FRUIncludesProduct
CIM_FRUIncludesProduct
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_ProductParentChild
CIM_ProductParentChild
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_FileStorage
CIM_FileStorage
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class CIM_ProvidesServiceToElement
CIM_ProvidesServiceToElement
CIM_ERR_FAILED: Class CIM_OperatingSystem referenced by association CIM_RunningOS does not exist.
CIM_RunningOS
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_SystemDevice
CIM_SystemDevice
CIM_ERR_FAILED: Class CIM_OperatingSystem referenced by association CIM_BootOSFromFS does not exist.
CIM_BootOSFromFS
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property CompiledBits
SAP_BCApplicationServer
CIM_ERR_FAILED: Unknown qualifier STATIC found in property AccSldModelVersion2
SAP_ACEEngine
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class SAP_ACENetworkInterface: CIM_NetworkPort
SAP_ACENetworkInterface
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_JCODestination
SAP_JCODestination
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_MsgServJCODestination
SAP_MsgServJCODestination
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_AppServJCODestination
SAP_AppServJCODestination
CIM_ERR_FAILED: Class SAP_ACENetworkInterface referenced by association SAP_ACENetworkToNetworkInterface does not exist.
SAP_ACENetworkToNetworkInterface
CIM_ERR_FAILED: Class SAP_ACEEngine referenced by association SAP_ACEAssociatedVirtualizationManager does not exist.
SAP_ACEAssociatedVirtualizationManager
CIM_ERR_FAILED: Class SAP_ACEEngine referenced by association SAP_HostedACEEngine does not exist.
SAP_HostedACEEngine
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class SAP_ACENetworkInterfaceComponent: CIM_SystemDevice
SAP_ACENetworkInterfaceComponent -
Error while creating a system in portal
Hi,
Iam trying to create a technical system(SAP System with Load Balancing) in the portal.When i try to test the connections im getting the following error:
The WAS ping service (http://hostname:portnumber/sap/bc/ping) was not pinged successfully. If the ping service is not activated on the WAS, you can try to call the ping service manually.
Can anyone please tell me how to resolve this?
Please suggest.
Regards,
Padmalatha.KHi,
Pls check out these links on SLD-
Steps to configure R/3 system to Portal implementation
Configuration Guide for R/3 in SLD as backend system
Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak
/community [original link is broken]
threadID=484726&tstart=0
Regards
Lekha -
Error while creating a system object for R3 in portal
Hi,
I am getting error while trying to create a system object in portal.
Following are the details I used :
Under WAS...
Web AS Host Name :<XXXX>:8001
Web AS path: /sap/bc/bsp/sap/
Web AS protocol : http
Under User management:
Authentication Ticket Type : SAP Logon Ticket
Logon Method :SAPLOGONTICKET
User Mapping Type : admin,user
Under Connector:
SAP Client : <Client NO>
SAP System ID : <System ID>
SAP System No : <System No>
System Type : SAP_R3
While trying with connection test... I am getting like this:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
5. The host name <FQDN Server Name> was resolved successfully.
6. The server sapdwh01 could not be pinged successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
Kindly help.
Regards,
Niraj
Edited by: Niraj Kumar on Dec 11, 2008 10:41 AMI created a SAP Transactional iView for transaction SE80.
Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
Got portal Runtime error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 12:57_11/12/08_0003_2795650
See the details for the exception ID in the log file.
Regards,
Niraj -
Error while creating source system entry in SAP BW system
Hi,
I am creating source system entry in SAP BW system for ECC system.In T-Code RSA1 i entered all the details of source system and BW system like RFC destination of source system and RFC user passowrd.
After clicking on enter system is promting me to enter into the souce system using administrator user.but i don't have admin user with SAP_ALL and SAP_NEW profiles because in my organisation they don't assign these profiles to any user.
So can you please update me what are the authorization required for dialog user in source system.
Regards,
GauravI would recommend to create a USER ID as COMMUNICATION type and assign SAP_ALL for it... this way, it can never be misused..
This will ensure that the user ID will have correct authorization in the source system and will not face any authorization related errors later on
Maybe you are looking for
-
Hi When i press the run button while mapping the tables I get the following errors. "Table has more than one role ignoring all the roles." Culd you please help me out in resolving this. Thanks & Regards, Suji
-
Photoshop CS6 on Retina...
I've downloaded CS6 for use with Apple's amazing Retina display. Why is my Photoshop UI still pixelated? I was expecting something amazing, and it's not all that great. Maybe I have to adjust something in my settings? Does anyone know when Adobe's ot
-
HDR merge edit not showing correct
When I try to merge for HDR the edit page does not show correctly. There is big white gap in the merge. I am using mac book pro retina and photoshop CC 14.1.2
-
FDMEE- Can the subledger data be brought into HFM using FDMEE?
Hi Experts, Is it possible to bring the sub-ledger data from PeopleSoft using FDMEE to HFM. As per one of the requirement of client it is required to bring the transaction level data directly into HFM. Please suggest whether it is possible to bring t
-
Embed color profile for Spot Multichannel
Is it possible to embed a color profile into a multichannel file made up of spot colors onlys ? More specifically can you embed custom dot gain curves into such file like you can for other color spaces like CMYK. ?