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 me

pls check this
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
as per ur doubt
1. host name:; sap system (can find under system status info-->database of R/3)
2. SId is system status->database>name (3) characters
3.while creating business system for this technical system am not able to find the option under RELATED INTEGRATION SERVER--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

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 Raheja

HI 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,
Nishant

Can 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

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 "RFC call failed : Error opening an RFC connection"
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
Points will be Given If the Problem Is Solved
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

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,
RP

Hi,
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

PI7.0: SLD - Technical System of type "Exchange Infrastructure"

Hi Guys,
The adapter engine was empty in the integration directory and as part of it i followed the steps in the sap note - 764176 Error in XI due to inconsistency in the sld. I did the following steps
1. Switch to "Home" in the "Technical Landscape" view, and select the
"Exchange Infrastructure" technical system type there. Select all
domains and XI components for the host and delete these by selecting
them and pressing 'Remove'.
2. Restart the J2EE server. After you restart the server, the XI
components log on to the SLD again and create a new entity of class
"XI Integration Server".
3. To register the directory and repository again, you must also log on
to the two tools.
I have restarted the j2ee server and looged into the IR and ID but they are not automatically registered in the central sld.
central sld is on solmanger box. How to register IR, ID, RWB and central adapter engine under the technical systems of type exchange infrastructure ?
any help would be really appreciated
Thanks,
Raj

Hi Reddy,
i faced the same problem few days back...
check this link
/people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
and also cross-check the post installation steps.
In my case the Business system for XI was created of type web as java... but it should be of type web as abap.
Sachin

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 file

Hi,
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

How to find Installation Number in R3 to create Technical system in XI.

Hi,
how to find Installation Number in R3 to create Technical system in XI. can you please help me out.
thanks
siva.

Hi Siva,
Host name you can find at same location. Not sure about message server port (Basis team shall be able to provide this information)....
However there is a very simple way fo creating technical system..
Check out this Michals blog...its very easy
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
Nilesh

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
Rock

hi,
check the log file and let me the the error.
manish

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 AM

I 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 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.K

Hi,
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 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,
Gaurav

I 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

Regarding no party no technical system, or anything when log into IR

Hi all:
Technical systems(ABAP type) and business systems(ABAP type) have been created in SLD, however when log into Integration Repository, there is nothing on object Panel, no technical system or party , totally empty, could you please tell me how to import or the possible reason for this ?
Thanks in advance!!!

HI Sony,
Can you confirm r u in the Integration Directory or in Integration Repository??
You can not find the Business System and Party in IR.
If you are in ID you need to create the Scenarion and then you can get the party, servicewithoutpary,receiver determination, Interface determination, sender agreement and receiver agreement.
Now you can assign the Business systems from the SLD to the Business System under servicewithoutparty-> Business Systems.
YOu cannot findout the Technical Systems in the ID also.
Regards
Sridhar Goli

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
Shilpa

Hi 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

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,
Priya

Read the note listed below, which addresses your issue.
Link: [Note 1178572|https://service.sap.com/sap/support/notes/1178572]

Regarding error in creating technical system of type WEB AS ABAP

Similar Messages

Maybe you are looking for