Check Tool Result - Some Issues

[Former Member]

Dear experts

After we ran the wizard and completed all steps, we checked the configuration with "check tool for SharePoint Integration" and have found some issues, whis are listed below:

________________________________________________

ISSUE 1

-

---

Starter Services:

........-> Connectivity

...............-> Web Service Configuration

........................-> Logical Port is not maintained for the Service /IWCNT/CO_BPC_CONT_BYID_QR_OB and Service G

........................-> Logical Port is not maintained for the Service /IWCNT/CO_BPC_CONT_CNC_RC_OB and Service Gr

........................-> Logical Port is not maintained for the Service /IWCNT/CO_BPC_CONT_CRT_RC_OB and Service Gr

........................-> Logical Port is not maintained for the Service /IWCNT/CO_BPC_CUSTOM_CHG_RC_OB and Service

........................-> Logical Port is not maintained for the Service /IWCNT/CO_BPC_CONT_CHG_RC_OB and Service Gr

........................-> Logical Port is not maintained for the Service /IWCNT/CO_BPC_CUST_BYID_QR_OB and Service G

........................-> Logical Port is not maintained for the Service /IWCNT/CO_BPC_CUSTD_BYID_QR_OB and Service

........................-> Service Group Configuration is missing for /IWCNT/CODELIST_SERVICE_GROUP

........................-> Logical Port is not maintained for the Service /IWCNT/CO_CST_BOM_BYMAT_QR_OB and Service G

........................-> Logical Port is not maintained for the Service /IWCNT/CO_MAT_ERP_BYID_QR_OB and Service Gr

........................-> Logical Port is not maintained for the Service /IWCNT/CO_CST_BOM_BYVAR_QR_OB and Service G

-

---

We are aware of the notes 1500721 and 1480794 - we implemented both notes before we had ran the wizard.

________________________________________________

ISSUE 2

-

---

Workflow

........-> SharePoint Certificate

........................-> Mismatch found between STRUST and SCL view table /IWFND/V_C_ISSUR

........................-> Failed to read any Role Synchronization data

........................-> No user subscription was detected

-

---

We have several times tried to recreate the certificates between SharePoint and SCL - but the error persists.

________________________________________________

ISSUE 3

-

---

Common

........-> SCL activated

........................-> SCL was not activated as required

-

---

You expert advise is needed to solve these issues - thanks

Regarda

Tariq

[Former Member]

Hi Tariq,

from the list that you pasted it looks to me like all the errors are not real errors.

Unfortunately the Checktool itself does contain errors right now which return these missleadings results.

ISSUE 1:

Go to SOAMANAGER and from Service Administration -> Business Scenario Configuration check that a "DUET_STARTER_SERVICES_ALL" scenario configuration exists and is active.

Then go back and open "SOA Configuration Request Queue Management". Click on "Check for Updates" and make sure that you do not see any Failed items.

(maybe here you will see one failed item for CODELIST. In this case check [Note 1500721 - Matching Interface for QueryCodeList Service|https://service.sap.com/sap/support/notes/1500721])

ISSUE 2:

Open table /IWFND/V_C_ISSUR (or go to SIMGH -> Service Consumption Layer Administration -> User Settings -> Connection Settings -> SCL to Consumer -> Define Consumer Issuer Certificate) and make sure that the entries look exactly like this:

Consumer Type: SHAREPOINT_INT

Issuer Name: SharePoint

Issuer Certificate: CN=SharePoint Security Token Service, OU=SharePoint, O=Microsoft, C=US

ISSUE 3:

Go to SIMGH -> Service Consumption Layer Administration -> General Settings -> Activate or Deactivate SCL and make sure that the SCL is active.

Regards,

Holger.

[Former Member]

Dear Holger

Thanks a lot for your answer and time...

I went through all these steps before I created the message and yes I had that note in mind and followed all the recommendations written in that.

The error I am getting in SOAMANAGER is following:

Configuration of service group '/IWCNT/CODELIST_SERVICE_GROUP' failed

.... Configuration of proxy '/IWCNT/CO_ESI_CODE_BYELQR_OB' failed

.........Failed to create a logical port using Service Registry

...............Failed to create a logical port for inbound interface 'QueryCodeList' 'http://sap.com/xi/BASIS'

........................ UDDI error: No Primary Services Registry maintained in this System

........................ Could not determine service using UDDI query

...............Failed to create a logical port for inbound interface 'QueryCodeList' 'urn:sap-com:document:sap:soap:esr'

........................ UDDI error: No Primary Services Registry maintained in this System

........................ Could not determine service using UDDI query

...............Failed to create a logical port for inbound interface 'QueryCodeList_Out' 'http://sap.com/xi/IWCNT/PI/BASIS'

........................ UDDI error: No Primary Services Registry maintained in this System

........................ Could not determine service using UDDI query

......... Failed to create a logical port using WSIL

...............Failed to create a logical port for inbound interface 'QueryCodeList' 'http://sap.com/xi/BASIS'

.........................Could not determine service using WSIL query

...............Failed to create a logical port for inbound interface 'QueryCodeList' 'urn:sap-com:document:sap:soap:esr'

.........................WSDL http://NNNNNNNN.VVVV.XXXXXXX.com:8001/sap/bc/srt/wsdl/bndg_E056C5E26D7C84F1AC6AA6F30C6BA0F1/wsdl11/b... contains different profile name

...............Failed to create a logical port for inbound interface 'QueryCodeList_Out' 'http://sap.com/xi/IWCNT/PI/BASIS'

.........................Could not determine service using WSIL query

All other setting are exactly as you mentioned

Regards

Tariq

[Former Member]

Hi Tariq,

the problem with the error "... contains different profile name" is explained in the [Troubleshooting Guide|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/603ab5a0-184b-2e10-98a7-fa7e7e9da7a1] in Chapter "18. When opening a Workspace in the Start Services scenario you get an unexpected error occurred" (check page 51 onwards...).

The problem is that the services in the backend were released with a differnt profile (name) than the profile that you are using on the SCL to retrieve/connect to the services in the backend system.

Regards,

Holger.

[Former Member]

Excellent Holger - this solved my problem with activating. Thanks.