PI 7.1 EHP1 Step Logical Ports error

Hello,
I got the below error when in ran the managed system configuration for PI 7.1 EHP1 system.
Our solman is on SP22
Step Logical Ports Details
A failure occured while creating the logical port for JAVA XI : An exception occurred that was not caught.
!! Exception : An exception occurred that was not caught.
Exceptions
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1514)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
at java.lang.Thread.run(Thread.java:534)
EW Report for PI system is only 9 pages ,may be the above error is causing it.
Please help us to solve it
Thanks,
Srini

Hi Balbinot,
Thanks for your reply.
1. SMD_RFC user is not locked (in Solman).
2. According to note 1008474 in Visual Administrator of Solman CTC System Properties ,I found that the BACKEND_CLIENT property is having "001" as value (001 is our BW client) but the regular client is 201 .Should the value be 201 or 001 ????
And TTJAVA_HOME is having /usr/j2sdk1.4.2_13 but our java home is /usr/jdk/instances/j2sdk1.4.2_18 should i go ahead and change this one as well?
3.E2E_WS_CONN_LOG_PORT_CREATION does not exist in PI 7.1 system ,should this be run in Solution manager ?
Please help me to solve this issue?
Thanks,
Srini K

Similar Messages

  • SMD Error in managed system type PI 7.1 EHP1 Step Logical Ports error

    Hi people,
    Solution Manager Ehp1 7.0 SPS24
    I am currently runnig the wizard setup for managed System, everything is fine but when I run for PI 7.1 I get the following error:
    Fri Sep 10 20:29:48 2010 Logical Ports A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
    Step Logical Ports Details
    A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
    !! Exception : PORT_NOT_CREATED
    Exceptions
    com.sap.mw.jco.JCO$AbapException: (126) PORT_NOT_CREATED: PORT_NOT_CREATED
    at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1511)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
    at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
    at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
    at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
    at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
    at java.lang.Thread.run(Thread.java:534)
    Any ideas?
    Thanks in advance

    Hi everyone,
    Thanks everyone.
    Guilherme, finally I understand what really happens.  "Refresh" is not working properly in the Setup Wizard.
    First I have done what I can:
    System    Type      Managed Products                    Product Instances
    DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP  (I could not select PI at the same time)
    DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
    But, when I refresh the browser Internet Explorer appears the following:
    System    Type      Managed Products                    Product Instances
    DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP + Process Integration
    DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
    And then I do not get the error anymore. (I have to repeat step 2 in the wizard "Check Prerequisites for Diagnostics)
    And If I run transaction SMSY, I can see how PI is mantained since the wizard refresh SMSY.
    Product Instance Selection tab:
    Application Server ABAP (Flag selected: relevant)
    Process Integration (Flag selected: Also Installed, Technical System[ DPI, Java])
    Application Server Java (Flag selected: relevant, Technical System[ DPI, Java])
    So, if I use this configuration in the SMSY, when I run "solman_setup",  configuring DPI (My PI7.1), when I run "Configure Diagnostics", the wizard shows ABAP + PI as expected.
    Thanks a lot Guilherme!!

  • Logical port error (WS_LOGICAL_PORT) when consuming WS in PI

    Hi All,
    I am trying to integrate simple Currency Conversion Web Service witm my ECC program.
    Program displays two fields in the selection screen (Currency From and Currency To)
    WS is: http://www.webservicex.com/ws/WSDetails.aspx?WSID=10&CATID=2
    The scenario is as below:
    Proxy (Z-PROGRAM ) <-sync-> PI <-sync-> WS (Currency Convertor)
    Looks like ABAP Proxy is done ok.
    PI configuration also looks ok as I am trying it in IB's Test Configuration tool - all steps are 'Green / Passed'
    Based on WSDL 3 interfaces were generated:
    CurrencyConvertorHttpPost
    CurrencyConvertorHttpGet
    CurrencyConvertorSoap
    I am using Soap one... along with WS Communication Channel
    CC has configuren itself based on WSDL likn provided,
    Technical Transport Settings were set to:
    Target Host:               www.webservicex.net
    Service Name / Port:     -1
    URL Access Path:          /CurrencyConvertor.asmx
    Transport Binding:          SOAP 1.1 Using HTTP
    Why am I getting logical port error?
    Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
    I searched the web for error message and I found obsolete logical port configuration using LPCONFIG, and also some 'new' approach with SOAMANAGER LogPort configuraton
    (When I try to do this as suggested in [document |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b04408cc-f10e-2c10-b5b7-af11026b2393?QuickLink=index&overridelayout=true]
    then I cannot see my newly created services on the list)
    ... but is this the right track to follow?
    Should I run Logical Port configuration in PI?
    I would appreciate your comments on this.
    Regards,
    bob.

    Hello,
    Why am I getting logical port error?
    Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
    WS Adapter is used for those that are using WS-RM (Webservice-Reliable Messaging)...See this blog
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b00bbb77-75bc-2a10-6b9a-a6f8161515a6, but I think for now this is limited to SAP-to-SAP connections. That is why in your error it is searching for a logical port (ABAP Proxy).
    You should be using the SOAP Receiver Adapter instead.
    Hope this helps,
    Mark

  • Logical port error when accessing e-recruiting web pages

    Hi,
    We are trying to set up our e-recruiting 3.0 and web dispatcher systems. We were receiving an error in our e-recruiting system in transaction SM20 that states “Logon Failed (Reason=34, Type=H)”.  The user is SAPSYS for client 000.  The system was attempting to log on to our web dispatcher system.  SAP suggested creating an entry in SM30, table VUSREXTID, mapping the External ID to our web dispatcher  system.  This entry helped in that we are not receiving the above error message anymore.  However, when we attempt to access the web pages we are receiving the error “Name of logical port ‘&lp_name&’ is invalid.  Prior to adding this entry we were able to access the logon page by entering the following url using an external alias (ex. https://recruiting.mphi.org/internal).  Recruiting.mphi.org is our web dispatcher system.  We do not want our e-recruiting system to be accessible from the outside.  We want everything to go through our web dispatcher.  Has anyone had a similar issue setting these up?
    Thanks!
    Heather

    Hello Heather,
    I am no specialist in network infrastructure but i remember a customer setting up a web dispüatcher szenario. I also encountered this &lp_name& error from time to time during my work.
    The error points towards damaged urls and the customer also encountered such problems when setting up the web dispatcher landscape. Sometimes the last parameter of the URL was ignored or lost. Sometimes the web dispatcher transformed the URL including the parameters. But as parameters are case sensitive transforming them to upper/lower result in errors as the system no longer recognizes them.
    Perhaps you can check the URL with which the web dispatcher is calling the sap server to find out if it does any funny things w/ the links.
    Best Regards
    Roman Weise

  • How to view logical port error log

    can anybody tell me how to view the logicalport error  log

    Usually in a distributed environment you would point the logical addresses to the http web server and port or to the load balancer, if you are just using a web server like OHS you can set all the logical addresses by running configure web server and select "Set the logical web address for the web applications to the web server"
    If you want to see all the configuration in the Shared services registry then you can run <MIDDLEWARE_HOME>\user_projects\epmsystem1\bin\epmsys_registry.bat to generate a report and the web app configurations will be under LOGICAL_WEB_APP
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Error while creating logical port for Reporting

    Hi,
    In one of the training materials for Duet Enterprise, i saw the steps for creating logical port for the consumer proxy /IWTNG/CO_PXY_RECORDS_REPOSITO.
    When i am trying to create the logical port, i am getting an error saying,
    " SRT Framework exception: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:500 Native SSL error
    https://<server:port>/_vti_bin/OBAFileReceiver.asmx?wsdl "
    I would like to know is it really necessary to create this logical port for "Reporting Scenario" and is it not created automaticallly using the Installation Wizard??
    And in case it has to be created, how to resolve this SRT framework exception?
    ~ Ramanath.

    Hi,
    the consumer proxy  /IWTNG/CO_PXY_RECORDS_REPOSITO was used in Duet Enterprise SP01. Now with SP02 the consume proxy /IWTNG/CO_OBAFILE_RECEIVER_SOA is created.
    However, the SSL error that you are getting looks a little strange (it does not mean that there is an error, but it is worth checking):
    So can you go to SOAMANAGER -> Service Administration -> Single Service Configuration. In here select "Consumer Proxy" from the "Search by", Search Pattern "/IWTNG/CO_OBAFILE_RECEIVER_SOA" and Field: Both.
    You should find one entry. Select it and click "Apply Selection".
    Now go to the Configurations tab. Here you should see one Logical Port with name "LOGICALPORTFORREPORTING" with Creation Type "Manually Created". In fact this logical port was created by the Wizard.
    Click on Display and scroll down again. Now in the "Additional Information" tab there is a string after HTTP Destination, e.g. 0050568E3F5A1ED096F22339C44BAF83.
    Copy this value and go to your SAP GUI -> Transaction SM59.
    Here click on Find/Search and search for this HTTP Destination. You should find one Type G RFC Destination that has the target host of your SharePoint server and the path prefix /_vti_bin/OBAFileReceiver.asmx.
    Now you can test the service. Just click on Connection Test. The result should be a HTTP Response: 200.
    If not, then something went wrong with the automatic configuration and we should take another look at it (for example maybe the SSL certificate from SharePoint that was imported by the Wizard is not valid)
    Regards,
    Holger.
    PS. Don't use the "Ping Web Service" test from SOAMANGER -- unfortunately this is not working consistently.

  • Error Message "No logical port exists to call web services" installing SM7

    I am trying to use SLM to download a service stack.  However, the option is not available in step 2.5.  There is an error message "No logical port exists to call web services".  I have performed the Wizard install, but the Wizard seems to have left out this step.  I have looked around for documentation on how to configure the port, but cannot find anything more useful than comments to the effect that I should configure the port.

    I found the problem, I think, although I am now on to the next problem.  "Web Services for software lifecycle manager not available'.
    The documentation is lacking.  When the RFC connection is set up, the user id is j2ee_admin, using the install password.  This is not specified anywhere in the install instructions that I could find, there is only a reference to a 'user id and password'.
    The LPCONFIG is used to create a logical port, that ties the RFC to the LP.  However, no name is specified that is to be used for the LP.

  • Error while determining logical Port

    Hi
    This is a ECC to SRM scenario:
    I get this error in the Call Adapter step. I am using WS Adapter at the receiving side.
    "Error while determining logical port Cannot find logical port for agreement abc and interface xyz"
    Why do I get that error and any suggestions ?
    Regards
    Harish

    Baskar,
    I didn't fix any issue. I was trying tofind out why the error happens. There is a proxy created at ECC side. I saw that. But target is using WS Adapter and it's that adapter which is throwing errors about logical port.
    I read the blog but couldn't figure out. Does WS Adapter need proxy code? Can it work without proxy code? I don't see any proxy code for receiver WS Adapter. I was wondering whether the absence of the proxy code gave this error about logical port
    Regards
    Harish

  • ERROR: [DRC 23-20] Rule violation (NSTD-1) Unspecified I/O Standard and ERROR: [DRC 23-20] Rule violation (UCIO-1) Unconstrained Logical Port

    I am attempting to follow the "after the out of the box" demo for the Zybo board. I am trying to generate a bitstream on vivado 2015.1 and I keep getting these two errors
    ERROR: [DRC 23-20] Rule violation (NSTD-1) Unspecified I/O Standard - 96 out of 226 logical ports use I/O standard (IOSTANDARD) value 'DEFAULT', instead of a user assigned specific value. This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all I/O standards. This design will fail to generate a bitstream unless all logical ports have a user specified I/O standard value defined. To allow bitstream creation with unspecified I/O standard values (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks NSTD-1].  NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: gpio_rtl_tri_i[31:0], gpio_rtl_1_tri_io[31:0], gpio_rtl_0_tri_o[31:0].
    ERROR: [DRC 23-20] Rule violation (UCIO-1) Unconstrained Logical Port - 96 out of 226 logical ports have no user assigned specific location constraint (LOC). This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all pin locations. This design will fail to generate a bitstream unless all logical ports have a user specified site LOC constraint defined.  To allow bitstream creation with unspecified pin locations (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks UCIO-1].  NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run.  Problem ports: gpio_rtl_tri_i[31:0], gpio_rtl_1_tri_io[31:0], gpio_rtl_0_tri_o[31:0]
    when first creating the project in Vivado 2015.1 i could not find the Zybo board in the list of boards to choose from. so i followed the "how to import Zybo board into project" topic located on the Xilinx community forum. Since i could not directly select the board some of the instrution for the demo had to be modified. In step seven i could not select the "apply board preset" box and in step 9 i could not assign "btn_4bits" and "sws_4bits" to the gpio blocks. The "After the box demo" can be found here
    https://reference.digilentinc.com/zybo:gsg
    Please help me with setting the I/O standards or importing the Zybo boards as one of the boards I can select insted of me selecting the properties of the board.
    Thank you
     

    Hi
    As mentioned in the link (http://www.xilinx.com/support/documentation/user_guides/ug361.pdf), can you try the design with Vivado 2014.3?
    Thanks,
    Vinay

  • Error activating logical port for service group

    Hi,
    I reconfigured the Starter Services because I changed the backend.
    It all worked fine, but in SOAMANAGER it throws an error when trying to activate logical ports for service group /IWCNT/BPC_SERVICE_GROUP (error is thrown for all 4 service groups he wants to activate)
    Configuration of proxy '/IWCNT/CO_BPC_CONT_BYID_QR_OB' failed
        Failed to create logical port for local shortcut.
             Service group '/IWCNT/BPC_SERVICE_GROUP' is not assigned to the own business system.
                Failed to create a logical port using Service Registry.
                    Use profile name = 'SAPLOGONPROFILE' version = '4'
                          Failed to create a logical port for inbound interfaceCustomerERPRelationshipContactPersonByIDAndContact'            'http://sap.com/xi/APPL/SE/Global'
                                 UDDI error: No Primary Services Registry maintained in this System.
    I checked:
    1. The provider system name
    2. WSIL works fine
    3. The profiles used are the same
    If i take a deeper look at the service groups there where no logical ports created.
    Thank you
    Regards
    Pit

    Hi Alex,
    I followed the steps mentioned in the guide (3.3.2) but it didn´t work at all.
    The services uses all the same profile. The profile is importet in the SCL.
    When I process the pending tasks this massages shown up:
      Failed to create a logical port using WSIL (This step is red)
      Use profile name = 'SAPLOGONPROFILE' version = '4'  (This step is OK = green)
      Target WSIL type SAP_6.40  (This step is OK = green)
      Failed to create a logical port for inbound interface 'CustomerERPRelationshipContactPersonUpdateRequestC' 'http://sap.com/xi/APPL/Global2'  (This step is red)
       Could not determine service using WSIL query  (This step is red)
    Is it normal that on the SCL, in the Business Scenario Configuration there are no entries in the Service Definitions for the Duet_Starter_Service_All scenario.
    Regards

  • Error while creating logical port for Consumer Proxy in SOAMANGER

    Hi,
    While creating logical port for my consumer proxy in SOAMANGER, I am getting the error shown below
    SRT Framework exception: HTTP: Current user does not have the required authorization to access the HTTP destination
    I have searched in the forums but none of the answers helped me.
    I have specifed my PI user ID and password and the user has the followwing roles assigned to it.
    SAP_BC_WEBSERVICE_SERVICE_USER
    SAP_BC_WEBSERVICE_ADMIN_TEC
    SAP_BC_WEBSERVICE_CONSUMER
    SAP_BC_WEBSERVICE_ADMIN
    Current user in the error message refers to the PI user that i have specified or the user with which i have logged in the backend ABAP system?
    Please help me reslove this issue.
    Thanks and regards
    Sreehari Nambiar

    Hi,
    Please add the following roles as well.
    SAP_BC_WEBSERVICE_ADMIN_BIZ
    SAP_BC_WEBSERVICE_DEBUGGER
    SAP_BC_WEBSERVICE_OBSERVER
    Also make sure that you are doing the role comparison  after adding all SAP* roles in your profile.
    Let me know if this works?
    Thanks,
    Sridhar

  • Error while creating logical port from WSDL in SOAMANAGER

    Hi,
    I am trying to create a logical port for the webservice TerritoryCRMBasicDataByIDQueryResponse_In with the WSDL
    http://usciq9e.wdf.sap.corp:50077/sap/bc/srt/wsdl/sdef_TERRITORYCRMBASICDATABYIDQUERY/wsdl11/ws_policy/document?sap-client=506
    In SOA Manager, I selected the proxy object and clicked on 'Create Logical Port' ,
    gave the name and description for the port and set it as default.
    The other settings are :
    Configuration type : WSDL based configuration
    WSDL base is : Via HTTP Access 
    Then I gave the address of the WSDL in  the URL and the proper username and password. When I clicked on 'Apply Settings' I get the following error:
    "Error when building binding view: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL "
    Please advise me on how to approach the problem.
    Thanks,
    Sashi

    Creating logical ports is done here:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/44/cc8fd368c873dfe10000000a11466f/frameset.htm

  • Error while creating logical port in SOAMANAGER

    Hi,
    Im consuming the webservice.While creating the new logical .Im getting the following error.
    Error: Error in WSDL access: Exception occurred in communication framework:Error in HTTP Framework:401Unauthorizedhttp://vmtmasterdev.rune2emaster.rune2e.com:1080/sap/bc/srt/wsdl/sdef_Z_NUMBER/wsdl11/ws_poli
    I have entered logical port name,description, URL for WSDL access.When i press enter i got the above eeror.
    Please help me.
    Regards,
    Brahmaji

    Hi,
    tell me please wenn you run SOAMANAGER you have to apply an user Authentication or not?
    If yes If the service that you want to configure is an Enterprise Service or Self-Modelled Service.
    In case of Web Services Please Check again in The ICF Services under
    sap/bc/srt/SAP and Check if your Service activated or not.
    If you don´t have Access to SOAmanagement you can see the specified Roles hier
    http://help.sap.com/saphelp_nw04s/helpdata/en/2b/07074155bcf26fe10000000a1550b0/frameset.htm
    Regards
    A.Labrache

  • Error in logical port while connecting to SAP CRM cloud

    Dear Members,
    I have created a logical port manually to connect to SAP CRM cloud system. But when I ping the web service I am getting below error. Please let me know how to solve this error.
    SRT Framework exception: Service Ping ERROR: Error when calling SOAP Runtime functions: SRT: Couldn't create Object: ("ICF Error when creating HTTP client object by Config for URL <WSDL URL>

    Hello Nihar,
    The error message indicates the HTTP client object cannot be created by the given URL. Please check if your URL is correct.
    You also need to check what protocol is used, HTTP or HTTPS, and ensure the protocol is active in your local ABAP system as well. You can check them by t-code SMICM->Goto->Services.
    Regards,
    Robert

  • Error in Logical Port Creation

    Hi,
    When I try to create a logical port in my consumer system I am getting error
    "Error: HTTP: Error in interface for management of HTTP destinations; "
    Any ideas on how to fix this?

    Sorry - I should have been more clear earlier.
    I am using SOAMANAGER to create the logical port.  The error occurs when I choose 'WSDL Access Settings' to obtain the WSDL.  I was able to get around the problem by going into SOAMANAGER on my provider system, locating the service & binding I want, and then downloading that file.  This is a workaround as I would like to get the file via HTTP access.
    I suspect this has to do with configuration but I do not know where this needs to be setup.

Maybe you are looking for