Port error

Hi,
When I am teting my custom idoc in we19 I am getting error "<b>Port does not
exist in the table of port descriptions</b>". I created port, partner profile, Attached
the messaget type and every thing.
wha will be reason?
regards,
Ansar.

Hi Ansar,
when testing from SE19 you have to you use the system id for your port. When your system id = 'ABC' use port 'SAPABC'.
Regards,
John.

Similar Messages

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

Unable to print to network printer // sometimes with port error

I upgraded to Leopard and am now _*unable to print to my network attached*_ *_Lexmark x9350_*. In prefs it shows the printer and driver installed. Once a print job is submitted, it reads printing, but there is no action on the printer. Other times it gives a port error. I tested the printer under OSX 4 and it printed with no problem. I also have a similar problem on the XP partition of this system. Please advise.

I don't think Lexmark has a Leopard driver for this printer yet. This problem was discussed earlier here
http://discussions.apple.com/thread.jspa?messageID=5702119&#5702119

Ask for help :( "%ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/17: Power given, but Power Controller does not report Power Good"

This question is used a translator....
Current conditions
- SW1 ----- Power injector ------ AP(cisco is not another model)
- Port, AP, Power injector, Switch <-> Injector UTP cable Problems occur even after replacement
- Power injector <->AP UTP canle No exchange
- Poe was OFF the function. This is because it is being used for Power Injector. -> Do not generate failure logs
- But even if another AP is turned ON POE function, no error messages.
SW1#show logging (5 mins cycle persists)
May 4 10:37:32.527: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Gi1/0/17: Power given, but Power Controller does not report Power Good
May 4 10:37:42.556: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to down
May 4 10:37:43.562: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to down
May 4 10:37:50.032: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/17, changed state to up
May 4 10:37:52.046: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/17, changed state to up
May 4 10:38:03.238: %ILPOWER-7-DETECT: Interface Gi1/0/17: Power Device detected: IEEE PD
SW1#show cable-diagnostics tdr interface gi 1/0/17 <----- Issues AP
TDR test last run on: May 04 10:49:14
Interface Speed Local pair Pair length Remote pair Pair status
Gi1/0/17 1000M Pair A 84 +/- 10 meters Pair B Normal
Pair B 84 +/- 10 meters Pair A Normal
Pair C 84 +/- 10 meters Pair D Normal
Pair D 84 +/- 10 meters Pair C Normal
SW1#show cable-diagnostics tdr interface gigabitEthernet 1/0/18 <--------- Normal AP
TDR test last run on: May 04 11:01:04
Interface Speed Local pair Pair length Remote pair Pair status
Gi1/0/18 1000M Pair A 92 +/- 10 meters Pair B Normal
        Pair B 92 +/- 10 meters Pair A Normal
   Pair C 92 +/- 10 meters Pair D Normal
      Pair D 92 +/- 10 meters Pair C Normal
SW1#show cable-diagnostics tdr interface gigabitEthernet 1/0/1 <--------- Normal AP
TDR test last run on: May 04 11:01:56
Interface Speed Local pair Pair length Remote pair Pair status
Gi1/0/1 1000M Pair A 79 +/- 10 meters Pair B Normal
   Pair B 79 +/- 10 meters Pair A Normal
      Pair C 79 +/- 10 meters Pair D Normal
    Pair D 79 +/- 10 meters Pair C Normal
SW1#show power inline <-------- (Check every 5 seconds)
Module Available Used Remaining
(Watts) (Watts) (Watts)
1 370.0 200.2 169.8
Interface Admin Oper Power Device Class Max
(Watts)
SW1#show power inline | in 17
Gi1/0/17 auto off 0.0 n/a    n/a 30.0
SW1#show power inline | in 17
Gi1/0/17 auto on 15.4 Ieee PD   0 30.0
SW1#show power inline | in 17
Gi1/0/17 auto on 15.4 Xirrus XR2426, 1.0G 0 30.0
SW1#show power inline | in 17
Gi1/0/17 auto faulty 0.0 n/a n/a 30.0
SW1#show power inline | in 17
Gi1/0/17 auto off 0.0 n/a n/a 30.0

Plug the Xirrus AP directly to the switch port and see if the logs go away or not.

Equium M50 will not recognise the LAN port - error: Network Cable unplugged

I own a Toshiba Equium M50 and have problems with the Marvell Yukon 88E8036 PCI-E Fast Ethernet Controller.
I used to connect via an 'ADDON' Modem/ADSL Switch and had no problems. I then replaced the ADDON with a 'NETGEAR' DG834G ADSL Modem/Router to gain the wireless port, and since then my machine will not recognise the LAN port. <error: Network Cable unplugged>.
I know that the cables are OK as I used them with other laptops and had no trouble. I can also plug in a PCI card to connect without any problems. It looks to me as if the Marvell Yukon 88E8036 PCI-E Fast Ethernet Controller has a problem with the netgear Modem/Router.
Anyone out there with a similar experience and some advice/suggestions?
PLEASE

Hi
For me it doesnt show like a LAN card problem but your router is a problem.
Check the device manager if the LAN card was properly recognized. If there are no yellow exclamation marks so everything is ok!
You can try to delete the LAN card from the device manager and after new reboot install the LAN driver again.
The issue has stared after installing or connecting the new Netgear modem router.
Therefore I would recommend to checking firstly the settings or to update the firmware on this router.
I have found additionally these useful websites
http://compnetworking.about.com/od/windowsnetworking/f/cableunplugged.htm
http://www.experts-exchange.com/Networking/Broadband/DSL_Cable/Q_20381405.html

Port error while deploying a dictonary project to j2ee server

Hello,
I created a dictonary project in sap netweaver developer studio 7.1.The j2ee server and the database (both on a remote server) are running and configured.
When i try to deploy it i get the following errors
[#3]: DC API is trying to connect to '<server name>:50004' [INFO: Jan 31, 2008 9:28:26 PM /userOut/daView_category (eclipse.UserOutLocation) [Thread[main,6,main]] ]
om.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.
The error is guess is the port number.My server is configured on port 50000 and here it is showing 50004.If i am correct then how do i configure my applications port number?
I searched and saw some messages like open \usr\SAP\<SID>\SYS\profile ,edit the port and similar solutions.Where is this "\usr\SAP\<SID>\SYS\profile " location?My server is on a remote machine.How do i configure my client to pick up the correct port ?
Thank you in advance.
Thanks and Regards
Siri

the issue got solved..the error was not about the port..on restarting the server i was able to deploy my project..

Install port error.

Howdy all. I just installed 10g and during the install got an error about not being able to use the assigned port because it was set to NULL. It also said I would be able to go back and fix in Enterprise Manager after the install was complete. But then at the end of the install there is no link displayed for EM the way there is for iSQLPlus. Can someone pelase assist?
TIA, ChrisR

Hi,
http://dbataj.blogspot.com/2007/01/oc4j-configuration-issue.html
go through above link and create if not configure OEM for your database or CONFIGURE your database for OEM.
regards
Taj

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!!

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

Sender Port Error in SAP ECC for IDoc

Hi,
I am creating scenario IDOC -> XI -> JDBC with Customer Master IDoc.
After sending it with we19 he said "IDoc sent to SAP system or external program".
In we02 and we05 the IDOC it says "Data passed to port OK".
But in SM58, the IDoc ends in error saying
Transaction IDX1: Port SAPIDST100, client 600, RFC destination contains error.
What I identified that the port SAPIDST100 is the sender port in the IDoc being send. However, for PI we do not need to maintain sender port.
Business Systems:
Sender : SAP ECC
Receiver: SAPPID
Kindly provide your inputs.
Thanks
Rahul

Hi Rahul,
thanks for the information that your scenario is working fine.
But i want to clarify some points:
   - If you send out an IDoc from an ECC system, the senderport is filled with SAP+<system-id> by the SAP IDOC API,
     i.e. if your system id is "ABC", the senderport is "SAPABC"
      => your senderport SAPIDST does not match this template, so i assume you entered the value for the senderport
     manually in the idoc test utility WE19
   - if you send out an idoc, only the receiver port must be created in transaction WE21, it is not necessary to create
     the senderport in WE21, this is not necessary and did not solve your problem
- the idoc was send from ECC (application system with application IDoc metadata) to an XI/PI system (basis system
    without application idoc metadata
   The IDoc adapter on the pi system must analyze the IDoc segments and must know the idoc application metadata,
   but this is not known. So the idoc adapter on PI side looks at the senderport to identify the sender.
   In transaction IDX1 an rfc-destination can be configured to point to the sendersystem with that senderport
   With this rfc-destination the IDoc adapter tries to read the idoc aplication metadata from the ECC system and stores it on PI side.
   If there is no rfc-destination configured in transaction IDX1 on PI side you get the error mentioned in your request.
   I assume that in transaction IDX1 somebody configured the correct RFC-Destination.
I hope this clarification helps you to understand the error and the solution.
Kind regards,
Andreas Dahl

AS Java 7.01 Install - Port Error

Experts, I'm in the process of installing NetweaverAS Java (only no ABAP) 7.01 instance on Lunix Redhat 5. I am getting the following error after starting sapinst:
Logon Error:
Connection to SAPisnt could not be established, see following message
Could not connect to host localhost on port 21200
java.net.ConnectException: Connection timed out
java.net.ConnectException: Connection timed out
I have confirmed with the unix/server group that the ports are not in use
This obviously looks like an issue with the port, but I've been assured that the port is open/available. Does anyone have any insight?

Hello Michael,
Check for the all variable before s tarting the sapgui like java_home, LD_LIBRARY and DISPLAY try again.
Also try to use below commands
./startInstGui.sh -server -host <Linux Server IP Address> -p 21200
or
./startinstgui.sh -host <your_linuxserver_host_name>
or
./sapinst GUISERVER_DIALOG_PORT=21215
and let us know if you are still facing issues.
Thanks and Regards,
Ram

Nexus 5500 - Fabricpath Core Port - Error disabled. Reason:DCX-No ACK in 100 PDUs

Has anyone seen Fabricpath Core Interfaces between two Nexus 5596UP switches error-disabled because of missing DCBX Acks after 50mins?
I do not see interface errors and the peer is another 5500.
Both switches are running 5.1(3)N2(1) with this port config:
int e1/3
switchport mode fabricpath
! Cisco 5m Twinax cables
Log messages
2012 May 25 17:40:59 nexus1 %L3VM-5-FP_TPG_INTF_DOWN: Interface Ethernet1/3 down in fabricpath topology 0 - Interface down
2012 May 25 17:40:59 nexus1 %ETHPORT-5-IF_DOWN_NONE: Interface Ethernet1/3 is down (None)
2012 May 25 17:40:59 nexus1 %ISIS_FABRICPATH-5-ADJCHANGE: isis_fabricpath-default [3365] P2P adj L1 nexus5 over Ethernet1/3 - DOWN (Delete All) on MT-0
2012 May 25 17:40:59 nexus1 %CDP-5-NEIGHBOR_REMOVED: CDP Neighbor nexus5(FOX1550GDH1) on port Ethernet1/3 has been removed
2012 May 25 17:40:59 nexus1 %LLDP-5-SERVER_REMOVED: Server with Chassis ID 547f.ee63.fa88 Port ID Eth1/1 on local port Eth1/3 has been removed
2012 May 25 17:40:59 nexus1 %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet1/3 is down (Error disabled. Reason:DCX-No ACK in 100 PDUs)
Robert

Can you send the output of
show lldp interface ethernet 1/3
show lldp dcbx interface ethernet 1/3
a workaround may be to disable lldp on both sides on these physical interfaces

UTL_DBWS accessing web service gives 'not contain port' error

Hello
I am trying to call a web service from https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl
In the WSDL xml, i get the targetNamespace (http://PlanonWebServices.ws),
the service name (PlanonSession),
the wsdl URL (https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl),
the portType name (PlanonSessionHttpEndpoint),
the operation name (login).
When i call the web service, i get an error about the port :
-29532 - ORA-29532: Java call terminated by uncaught Java exception: service:
{http://PlanonWebServices.ws}PlanonSession does not contain port:
{http://PlanonWebServices.ws}PlanonSessionHttpEndpoint
The code is :
CREATE OR REPLACE PROCEDURE planon_Login AS
planon_username     VARCHAR2(50):= 'XXXXXX'; --- removed for security
planon_passwd     VARCHAR2(50):= 'XXXXX'; --- removed for security
service_ sys.utl_dbws.SERVICE;
call_ sys.utl_dbws.CALL;
service_qname sys.utl_dbws.QNAME;
port_qname sys.utl_dbws.QNAME;
operation_qname sys.utl_dbws.QNAME;
string_type_qname sys.utl_dbws.QNAME;
username     sys.utl_dbws.QNAME;
password      sys.utl_dbws.QNAME;
--retx               ANYDATA;
retx_string VARCHAR2(1000);
l_namespace     VARCHAR2(1000);
l_wsdl_url VARCHAR2(1000);
l_input_params      sys.utl_dbws.ANYDATA_LIST;
outputs      sys.utl_dbws.ANYDATA_LIST;
output_retx VARCHAR2(1000);
xml_string sys.xmltype;
retx sys.xmltype;
qname_list_     sys.utl_dbws.QNAME_LIST;
qname_list_string sys.utl_dbws.QNAME_LIST;
BEGIN
dbms_output.put_line('Step 1');
dbms_output.put_line('Step 1 : Set l_wsdl_url');
l_wsdl_url := 'https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession?wsdl';
dbms_output.put_line('Step 1 : Set l_namespace');
l_namespace := 'http://PlanonWebServices.ws';
dbms_output.put_line('Step 1 : Set service_');
service_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSession');
service_ := sys.utl_dbws.create_service (URIFACTORY.getURI(l_wsdl_url), service_qname);
dbms_output.put_line('Step 1 : Set port_qname_');
port_qname := sys.utl_dbws.to_qname(l_namespace,'PlanonSessionHttpEndpoint');
dbms_output.put_line('Step 1 : Set operation_qname');
operation_qname := sys.utl_dbws.to_qname(l_namespace, 'login');
dbms_output.put_line('Step 1 : Set call_');
call_ := sys.utl_dbws.create_call(service_,port_qname,operation_qname);
dbms_output.put_line('Step 2');
sys.utl_dbws.set_property(call_,'USERNAME', planon_username);
sys.utl_dbws.set_property(call_,'PASSWORD', planon_passwd);
sys.utl_dbws.set_property(call_,'SOAPACTION_USE','TRUE');
sys.utl_dbws.set_property(call_,'SOAPACTION_URI','https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services/PlanonSession');
sys.utl_dbws.set_property(call_,'ENCODINGSTYLE_URI', 'https://schemas.xmlsoap.org/soap/encoding/');
sys.utl_dbws.set_property(call_,'OPERATION_STYLE','document');
dbms_output.put_line('Step 3');
string_type_qname := sys.utl_dbws.to_qname('https://www.w3.org/2001/XMLSchema', 'string');
/* first return parameter in the WSDL should not be specified in the parameter list or errors occur
sys.utl_dbws.add_parameter(call_, 'loginResponse', string_type_qname, 'ParameterMode.OUT');
sys.utl_dbws.set_return_type(call_,string_type_qname);
xml_string := xmltype('<PlanonSession xmlns="https://wgfd-cafa02.uni.mdx.ac.uk:8443/nyx/services">'
|| '</PlanonSession>');
retx := sys.utl_dbws.invoke(call_,xml_string);
dbms_output.put_line('Step 6');
dbms_output.put_line('Step 7');
dbms_output.put_line('Call Web Service:services:PlanonSession: ' || retx.getStringVal());
dbms_output.put_line('Step 10');
sys.utl_dbws.release_call(call_);
sys.utl_dbws.release_service(service_);
dbms_output.put_line('Step 11');
EXCEPTION
when others then
dbms_output.put_line(SQLCODE || ' - ' || SQLERRM);
END;
The WSDL document is :
?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:ns="http://PlanonWebServices.ws" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://PlanonWebServices.ws">
<wsdl:documentation>PlanonSession</wsdl:documentation>
<wsdl:types>
<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://PlanonWebServices.ws">
<xs:complexType name="Exception">
<xs:sequence>
<xs:element minOccurs="0" name="Exception" nillable="true" type="xs:anyType"/>
</xs:sequence>
</xs:complexType>
<xs:element name="logout">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="logoutResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setReferenceDate">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:dateTime"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setReferenceDateResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setSessionDataSection">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="setSessionDataSectionResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="login">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="loginResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="logoutRequest">
<wsdl:part name="parameters" element="ns:logout"/>
</wsdl:message>
<wsdl:message name="logoutResponse">
<wsdl:part name="parameters" element="ns:logoutResponse"/>
</wsdl:message>
<wsdl:message name="loginRequest">
<wsdl:part name="parameters" element="ns:login"/>
</wsdl:message>
<wsdl:message name="loginResponse">
<wsdl:part name="parameters" element="ns:loginResponse"/>
</wsdl:message>
<wsdl:message name="setSessionDataSectionRequest">
<wsdl:part name="parameters" element="ns:setSessionDataSection"/>
</wsdl:message>
<wsdl:message name="setSessionDataSectionResponse">
<wsdl:part name="parameters" element="ns:setSessionDataSectionResponse"/>
</wsdl:message>
<wsdl:message name="setReferenceDateRequest">
<wsdl:part name="parameters" element="ns:setReferenceDate"/>
</wsdl:message>
<wsdl:message name="setReferenceDateResponse">
<wsdl:part name="parameters" element="ns:setReferenceDateResponse"/>
</wsdl:message>
<wsdl:portType name="PlanonSessionPortType">
<wsdl:operation name="logout">
<wsdl:input message="ns:logoutRequest" wsaw:Action="urn:logout"/>
<wsdl:output message="ns:logoutResponse" wsaw:Action="urn:logoutResponse"/>
</wsdl:operation>
<wsdl:operation name="login">
<wsdl:input message="ns:loginRequest" wsaw:Action="urn:login"/>
<wsdl:output message="ns:loginResponse" wsaw:Action="urn:loginResponse"/>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<wsdl:input message="ns:setSessionDataSectionRequest" wsaw:Action="urn:setSessionDataSection"/>
<wsdl:output message="ns:setSessionDataSectionResponse" wsaw:Action="urn:setSessionDataSectionResponse"/>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<wsdl:input message="ns:setReferenceDateRequest" wsaw:Action="urn:setReferenceDate"/>
<wsdl:output message="ns:setReferenceDateResponse" wsaw:Action="urn:setReferenceDateResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PlanonSessionSoap11Binding" type="ns:PlanonSessionPortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="logout">
<soap:operation soapAction="urn:logout" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<soap:operation soapAction="urn:login" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<soap:operation soapAction="urn:setSessionDataSection" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<soap:operation soapAction="urn:setReferenceDate" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PlanonSessionSoap12Binding" type="ns:PlanonSessionPortType">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="logout">
<soap12:operation soapAction="urn:logout" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<soap12:operation soapAction="urn:login" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<soap12:operation soapAction="urn:setSessionDataSection" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<soap12:operation soapAction="urn:setReferenceDate" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PlanonSessionHttpBinding" type="ns:PlanonSessionPortType">
<http:binding verb="POST"/>
<wsdl:operation name="logout">
<http:operation location="PlanonSession/logout"/>
<wsdl:input>
<mime:content type="text/xml" part="logout"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="logout"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="login">
<http:operation location="PlanonSession/login"/>
<wsdl:input>
<mime:content type="text/xml" part="login"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="login"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setSessionDataSection">
<http:operation location="PlanonSession/setSessionDataSection"/>
<wsdl:input>
<mime:content type="text/xml" part="setSessionDataSection"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="setSessionDataSection"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="setReferenceDate">
<http:operation location="PlanonSession/setReferenceDate"/>
<wsdl:input>
<mime:content type="text/xml" part="setReferenceDate"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="setReferenceDate"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="PlanonSession">
<wsdl:port name="PlanonSessionHttpSoap11Endpoint" binding="ns:PlanonSessionSoap11Binding">
<soap:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap11Endpoint/"/>
</wsdl:port>
<wsdl:port name="PlanonSessionHttpSoap12Endpoint" binding="ns:PlanonSessionSoap12Binding">
<soap12:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpSoap12Endpoint/"/>
</wsdl:port>
<wsdl:port name="PlanonSessionHttpEndpoint" binding="ns:PlanonSessionHttpBinding">
<http:address location="http://10.13.84.121:8080/nyx/services/PlanonSession.PlanonSessionHttpEndpoint/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Any help is greatly appreciated.
Thanks in advance

I got the same error... did you find a solution?
tks
Mário Cardia

IDOC Inbound processing - Port Error

Hi ,
I am working on Setting up a Standard IDOC Communication from Middle ware to SAP.
I have set-up Logical System, RFC Destinations for SAP And Middleware, Port for SAP and Middleware and Partner Profile.
I tested Middleware and SAP RFC destination Okay
I added Message types for Both SAP and Middleware.
I tried to create a IDOC In WE19 TCode, and i have error saying "EDI: Receiver port in control record is invalid"
The receiver is SAP as its Inbound.
Could you tell me what i need to Give in RFC destination for SAP ?
Do i need to enter Target host, System Number ? I didn't enter anything now.
I applicate any help.
Thanks

Hi, Thanks for the reply.
I did have this set-up
on SAP Partner profile, In Outbound, I have specified the Message Type.
In the reciver port, I have given SAP Port.
On Middleware Partner profile, In Inbound, I have specified the message type.
Any ideas?

BizTalk Send Port Error

We are getting error on send port after some changes in the map, but there is no change in the map which is throwing error -
Event Type: Error
Event Source: BizTalk Server 2009
Event Category: (1)
Event ID: 5754
Date:  11/26/2013
Time:  1:14:22 PM
User:  N/A
Computer: XXXX
Description:
A message sent to adapter "WCF-Custom" on send port "SndABCD" with URI "mssql://ABCDSQLDB/INSTANCE/ABCDReport?" is suspended.
Error details: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
MessageId: {A79F62AD-3C63-4543-9FEF-2682CF83106A}
InstanceID: {941EBEF7-7008-451C-AEBE-C7407462F943}
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I have checked below links already which suggest, gac the DLL, but did not work for me -->
http://social.msdn.microsoft.com/Forums/en-US/01791899-a0bf-451d-9004-fe8b696a9270/custom-functoid-the-system-cannot-find-the-file-specified?forum=biztalkediandas2
http://blogs.eliasen.dk/Technical/post/2010/01/17/TheSystemCannotFindTheFileSpecified.aspx
http://stevestechnotes.blogspot.com/2008_02_01_archive.html

Port error

Similar Messages

Maybe you are looking for