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.

Similar Messages

Logical port creation error through SOAMANAGER

Hi,
When I try to create a logical port through SOAMANAGER I got the following error.
Error: 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
When I actually look into the class CL_SRT_WSP_CONFIG_SIDL I could'nt find the method CREATE_CLNT_CFG_FROM_WSDL_D in SAP 720 version.
I had seen some discussions in the forum on this error but I could'nt find a proper solution.
Can someone explain me on how to resolve this issue.
Do I need to apply a oss note ? Is it mandatory. Also in one thread they talked of SICF transaction usage which is also not clear. Is there any other way.
Thanks,
Shashi

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.

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 for Consumer proxy in SOAMANAGER

HI Experts,
While creating Logical port for Consumer proxy in SOAMANAGER I am facing problem
"SRT Framework exception: 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 ".
Kindly suggest.

Hi Milan,
this kind of error occurs when there is no service and end point description in the WSDL of provider who's service you are trying to consume using Consumer Proxy.
Just open the provider's WSDL URL that you have given while creating Logical port for the consumer proxy and check if service and end point exists there.
Thanks
Sunil Singh

Error generating logical port in SOAMANAGER

Hi,
When generating the logical port in SOAMANAGER transaction I get an error message 'SRT Framework exception: 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'.
Does anyone know what the problem might be?
Thanks in advance.
Fernando.

Hi,
go to SICF transaction under /sap/bc/srt/wsil path, test the service and look for service provider you want to consume.
you get 2 links then test for logical port.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/media/uuid/20eb3174-41ab-2a10-a383-907faf60eed3
The link is constructed in the following way:
http://<host_name>:<port>/sap/bc/srt/wsil?sap-client=<sy-mandt>
or you can use transaction SICF then navigate to node /sap/bc/srt/wsil
and press "Test service" from the context menu.
In case there is a Service Registry in your system landscape to which the provider system is connected the profile-based endpoints could be found in that Service Registry as well.
you can follow note 1330545
/people/franklin.herbas/blog/2007/12/11/service-modeling-with-the-esr
/people/peter.mcnulty/blog/2008/02/04/service-implementation-in-abap
regards
nag
Edited by: welcomenag on Jun 25, 2009 5:56 PM

Connection to ByDesign with a ODP Source system: Logical port creation on CO_RSDSPX_ODP_IN

Hello,
I am trying to connect my ByDesign Could server to the our BW Server by an ODP Source system.
I tried applying what SAP recommend:
http://help.sap.com/saphelp_nw73/helpdata/en/46/b9297716c94e509fcbe62d3c795e85/content.htm?frameset=/en/c6/afacb707764885a6fb62f511c24f34/frameset.htm
http://help.sap.com/saphelp_nw73/helpdata/en/ca/14c0899cb04f16929b5d88e147fc8f/content.htm
http://help.sap.com/saphelp_nw73/helpdata/en/9e/c7a3591dc74a679bbc9716354e42af/frameset.htm
When trying to create a Logical Port on CO_RSDSPX_ODP_IN from SOA Manager with a WSDL Based configuration (downloaded from a Webservice of our ByD), this error is thrown:
SRT Framework exception: The WSDL document is not compatible with proxy class "CO_RSDSPX_ODP_IN": "Unsupported Operation(s):GetList, CloseSubscription, CloseSubscription, CloseSubscription, CloseSubscription, CloseSubscripti
Do you have any idea ?
Also, i was unable to use any Consumer Service directly ... I am not a Basis and don't understand what configuration needs to be done.
Thank you very much.

Hi,
Did you create consumer proxy for the service you like to consume ?
It looks like your WSDL and Consumer proxy are not the same ?
Or you could create Logical Port Manually, but it will fail on provider side because the message you are sending and the provider of the service are not the same.
Manual Configuration
The system uses a user-specified binding URL to create a logical port. You need to specify a unique name for the logical port.
Thank You
Regards
Gov

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

Is logical port creation mandatory

Hi,
i am creting a service consumer in ABAP ..but it is giving me error :
no receiver could be determined....is it because i have not specified logical port while createing the object...
is it mandatory to create a logical port ?
Also when i create a logical port in soamanager i am getting the following error.
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'.

hi gourav,
thanks for a very helpful.. answer..
but i am still getting the error 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'.
while creating the logical port....i am using endpoint URL from the wsdl ...i also tried seleting the wsdl file while cerating port..
Also when i tried creting port for another consumer proxy it is working....so this is not a system issue
what could be the problem

Dynamical logical port creation

Hi
Is it possible to generate a logical port dynamically at runtime. I only need a logical port once for executing a web service, so I'm looking for a way to minimize administration work.
Regards, Mathias

hi gourav,
thanks for a very helpful.. answer..
but i am still getting the error 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'.
while creating the logical port....i am using endpoint URL from the wsdl ...i also tried seleting the wsdl file while cerating port..
Also when i tried creting port for another consumer proxy it is working....so this is not a system issue
what could be the problem

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

Edit Customer Problem and Logical Port

Hi Experts,
ISSUE 1
In Web Service Administration, when I look at /iwcnt/actionitemvi_document service in details, I can see one Endpoint only, that is Binding_T_HTTP_A_HTTP.
In the Troubleshooting Guide, in section 5. No Workflow / Reports reach the SCL from backend system, there are mentioned two endpoints: Binding_T_HTTPS_A_HTTP and Binding_T_HTTP_A_HTTP - all other setting, I have, are the same on my server as mentioned in the troubleshooting guide. So why there is diffrence in binding on that particular service?
The other thing I noticed, is, that when looking closer on the logical port creation on backend system in the Behind the scene video, it mentions, that the Path Suffix include binding_t_http_a_http whereas in the Troubleshooting Guide it is showing binding_t_https_a_http - why this?
What is the right path suffix for the logical ports at the backend system?
ISSUE 2
When we edit a customer from SharePoint, we get the following error:
Error
An unexpedted error has occured
Correlation ID: ea04d908.xxxxxxxxxxxxxx
Looking closer at the correlation at SCL, everything seems to be green and no error is reported, but in the ULS Viewer, following info are displayed:
Microsoft.BusinessData.Runtime.BackendNullReturnException: LobSystem (External System) returned a null structure which is incompatible with the associated metadata.
at Microsoft.SharePoint.BusinessData.Runtime.EntityRuntime.WrapAsEntities(IMethodInstance methodInstance, IEntity thisEntity, IParameter parameter, ITypeDescriptor entityInstanceRootTypeDescriptor, Object correspondingAdapterObject, IEntity targetEntity, ISystemUtility dataSystemUtility, ILobSystemInstance lobSystemInstance)
at Microsoft.SharePoint.BusinessData.Runtime.EntityRuntime.ExecuteInternal(IDataClass thisDataClass, ILobSystemInstance lobSystemInstance, ILobSystem lobSystem, IMethodInstance methodInstanceToExecute, IMethod methodToExecute, IParameterCollection nonReturnParameters, Object[]& overrideArgs, IFilterCollection filters)
at Microsoft.SharePoint.BusinessData.Runtime.EntityRuntime.FindSpecific(IEntity thisEntity, Identity entityInstanceIdentity, String specificFinderName, ILobSystemInstance lobSystemInstance)
regards
Tariq

Hi,
ISSUE 1:
This is very likely because SSL is not configured. First of all can you go to SOAMANAGER -> Business Scenario Configuration and deactivate and activate the DUET_ENTERPRISE_ALL. When activating check if you are getting errors for the Assertion profiles (my guess would be, that you are getting errors).
In this case check the SSL configuration from SMICM -> \[Menu] Goto -> Services
Here you should see an active service HTTPS. If that is not the case, check that the SSL certificate is created (STRUST) and make sure that the required profile parameters are set (see also Deployment Guide -> "To configure the use of SSL in the SCL host" on page 33 at http://www.service.sap.com/instguides -> Duet -> Duet Enterprise 1.0 -> Duet Enterprise SAP Deployment Guide)).
Regarding the backend configuration for the logical ports in LPCONFIG. Here it depends on how you have setup the configuration on the SCL. If you released the services with HTTPS then the URL in the backend has to be HTTPS binding, if you configured it via HTTP, then it has to be HTTP binding Did you perform the connection tests as described in the videos or in the checkpoint of the troubleshooting guide?
ISSUE 2:
Can you take a look also on the SAP side in SRTUTIL? Do you see any additional error information there? You might also want to check the errors from the log viewer /IWFND/VIEW_LOG
Regards,
Holger.

SOA Management - setting up logical port for WS

Hi
I'm trying to use the RepositoryFrameworkWS from abap.
During this i am setting up a logical pot for the webservice.
This is done through the SOA Management.
I find the consumer proxy CO_KMCWS_REPOSITORY_FRAMEWORK
I then try to create the logical port.
i use the wsdl
http://<server>:<java_port>/RepositoryFrameworkWS/Config1?wsdl&
when i apply the settings i get an error.
SRT Framework exception: The WSDL document is not compatible with proxy class "CO_KMCWS_REPOSITORY_FRAMEWORK": "Operation(s)Missing setGlobalConfig, resetSessionStatistic, resetGlobalStatistic, getSessionStatistic,
I know the operation i want to use(findResources). But I don't know how to set it up.
Can anyone help me ?
Best Regards,
Rasmus

Hi Rasmus,
Please check the Service definition in the WSDL URL given for Logical Port creation is same as the Service definition in the proxy CO_KMCWS_REPOSITORY_FRAMEWORK. It seems to me that some methods/ operations in th proxy could not be found in the Service definition in the WSDL URL.
Download the WSDL from the URL and open it using some tool and compare the Service definition with that of the proxy.
Regards,
Avishek.

WSDL version used for port creation in SOAMANAGER for Netweaver 7.01 SP-5.

Hi,
Does SOAMANAGER refer to a particular version of WSDL while creating the logical ports for consumer proxies. I'm asking this because after one of the upgrades in our ECC system we find that the authentication configurations of the port are automatically done based on the WSDL now, however this was not the case earlier.
Also logical ports created manually are giving runtime exception (Soap FAult Code : 1). Does logical ports creation necessarily have to be done from WSDL.
Please throw some light on the above, if any of you have faced this issue already.
Regards,
Avishek.

We got a reply from SAP that from NetWeaver 7.0 SP3, logical ports will be created based on Security policy mentioned in WSDL. We can however override this by creating the port manually and the SOAP fault code error can be resolved by manually entering the SOAP Action for each method of the Service in the 'Operation Specific' tab of the Logical Port details.

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: [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 in Logical Port Creation

Similar Messages

Maybe you are looking for