Error While Creating Runtime Systems on an Existing Track in NWDI

Hi,
There is already a track in NWDI with No runtime Systems.
I have to create the RunTime Systems to do development on this track.
When I try to select the Development checkbox in Runtime systems,
select configure  without wizard, Gave   Deploy Host name: **********.com
            Deploy Port :50018  (SDM port)
           Deploy PSWD:  SDM Pswd
It gives me a warning..
Synchronization of Runtime System triggered for system dev. Log can be found at
http://*****************************LogViewer?LogName=%2Fsapmnt%2FEPQ%2Fglobal%2FTCS%2FLOG%2FEPQ_WHRBD_D2010081322030045.log&Bsname=EPQ_WHRBD_D
When i go to the  log file
I see this Error Message
20100813180502 Info   :cannot create a connection for the buildspace:  EPQ_WHRBD_D //connect to deploy tool failed:Server <Host Name> did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to <Host name> at port 50018: Connection timed out:could be due to invalid address
Can you please tell me what could be the Reason.
Basis has already opened the Ports : http port and SDM Port.
I am able to ping the server from cmd prompt.
Points will be allocated for the answer.
Thanks.
Venkat

Hi,
There's no need to update CMS or to check whether the buildspace is open, do not click on JSPM flag (unless you need nwdi control at upgrade)...
The error message means only that from the host where you configure the RTS the SDM cannot be reached or logon request cannot be accepted.
This can be either , because the
- SDM password is wrong (you checked it already)
- the port is wrong (you also checked it. If this is really a 700 RTS, i.e. it has SDM, and the instance number is 00, then the port is really 50018, so this should be fine as well. Only mention, because as of 71X we use the P4 port 5<xx>04 for the deploy controller, as there's no more SDM). Still you can use "netstat -a" to see the status of the ports.
- The host is wrong. I agree with Dao, check not only FQDN, but also IP address.
Using this guide you can always check whether the entered data is correct:
http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CMS%29Q0002
Best regards,
Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

Similar Messages

  • 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

  • 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

  • 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

  • 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,
    Vineeth

    Hi ,
    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
    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 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 from a par file

    Hi all,
    I am trying to integrate a web app to our portal.
    When i am trying to create a from a par file (any par file ,even the system defined parfiles), i am getting the following error.
        Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 02:43_07/07/10_0005_8678350
    Refer to the log file for details about this exception.
    Please suggest me what to do??
    Thanks in advance

    hi Sandeep,
    thanks for the quick reply
    below is the error from the default trace file
      error 2010-07-08 10:13:32:132 10:13_08/07/10_0001_8678350
    [EXCEPTION]
    java.lang.ClassCastException... [see details]
    n/a com.sap.portal.prt.runtime sap.com/irj delep01 Server 0 0_86783
    Full Message Text
    10:13_08/07/10_0001_8678350
    [EXCEPTION]
    java.lang.ClassCastException
    at com.sap.portal.pcm.NewObjectDescriptor.addText(NewObjectDescriptor.java:167)
    at com.sap.portal.pcm.NewObjectDescriptor.putTextAttribute(NewObjectDescriptor.java:115)
    at com.sap.portal.pcm.iviewserver.NewIVSObjectDescriptor.setTitle(NewIVSObjectDescriptor.java:447)
    at com.sap.portal.admin.wizard.AbstractPCMWizard.setSpecialAttributes(AbstractPCMWizard.java:578)
    at com.sap.portal.admin.wizard.AbstractPCMWizard.finalizeDescriptor(AbstractPCMWizard.java:297)
    at com.sap.portal.admin.wizard.panes.SavePane.doAfterSubmit(SavePane.java:113)
    at com.sapportals.admin.wizardframework.core.WizardInstance.doPost(WizardInstance.java:356)
    at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:174)
    at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:99)
    at com.sapportals.admin.wizardframework.AbstractDynamicWizard.doContent(AbstractDynamicWizard.java:98)
    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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    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:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

  • 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

  • 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

  • Error while creating source system in BI: Modification not possible

    Hi All,
    We are about to move to production, and therefore it's necessary to create in BI the source system related to our ECC (R/3). While trying to perform this action from BI side we received the error message:
    SAP system has status 'not modifiable'. Because of this, and following with known consultants practices we've changed the client to customazing but it still not working although the message at this time is: Changes to repository or cross-client Customazing are not permitted. We have also verified transaction SE06 but it's not possible to change the Cross-Application Component to Modifiable. 
    Did someone face with this same problem before?
    Thanks to all in advance,
    Regards,
    José.-

    Hi Rick,
    I really appreciate your quick response. We followed your recommendation and could create the source system without problems. Thanks once again!
    Best Regards,
    José.-

  • 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 New System

    Hi,
    I am working on the HANA Sandbox and getting the following Error when I am trying to create a new system.
    u201CLicense Key could not be installedu201D.
    Regards,
    Surya Kumar

    To revert to the new snapshot, if you don't see the red bar...follow this steps...
    Go to Actions (Just below Logout) and press Revert Now.
    You will be redirected to the snapshot.
    Greetings,
    Blag.

  • 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

Maybe you are looking for

  • How to catch error in the Active Sync process

    Hi, we are using Flat File active sync to update IDM user attribute. Once IDM found matched record, it builts view. However, during this period, the the matched user is locked, for example. Then IDM stop processing this record then go to next record.

  • Lenovo Twist - How do you copy Win 8 Pro onto recovery partition?

    I upgraded my Lenovo Twist (3347-4HU) from Win 8 to Win 8 Pro with Windows Media Center (WMC).  How do I copy the newly purchased operating system and WMC to my HDD recovery partition so that if I ever have to do a restore, it will restore Win 8 Pro

  • For loop in whlie loop

    How can I change this programm, that i will always replace the variable C instead of adding it to the value from the last while loop. It is supposed to calculate a new C because the temperature T0 and the pressure P0 are changing. Right now it will a

  • Table for rule details.

    Hi All , I have written a rule in transformations. I want to see the details of rule like description , technical name etc. Is there any table where I can find out these details. Thanks & Regards, Rohit Garg

  • Adobe Captivate 5.5 Simulation Slide Issue

    Hello everyone, Recently we recorded 7 separate simulations in Captivate 5.5. We created a new Captivate 5.5 project and interjected these simulations throughout. When playing them back, the first simulation does not play the first slide of its serie