Error in DUET Configuration at SSL

[Former Member]

Hi All,

As part of DUET Configuration, Iam facing an error at the SharePoint side

Error: "Could not establish trust relationship for the SSL/TLS secure channel with authority 'duetxyz:8001'"

Please look into this and provide me your valuable suggestions to solve.

Thanks & Regards,

Kris

[Former Member]

Hi all,

The SSL certificate error at Share Point sidehas been resolved.

But when I go for Customers tab in MOSS(Sharepoint), it is throwing an error

"Client 123 is not available in this system"..

My duet system client number is 123. Please look into it. When it is able to identify SSL certificate from client 123, I dont know why it is saying that client 123 not available.

Thanks & Regards,

Kris

[Former Member]

Hi Kris,

can you check the logs on the SCL / Gateway system?

Do you see any errors in transaction SRTUTIL or /n/IWFND/VIEW_LOG?

Regards,

Holger.

[Former Member]

Hi Holger,

Thanks for the reply.

Errors have been found when executing T.CODE SRTUTIL --> Error log

-ERROR_CONTEXT

--ERROR_INFO

---EXCEPTION_INFO

-

---

TYPE /IWTNG/CX_RS_SAP_GLOBAL_MSGS

-

---

ERROR_TEXT Application Error

-

---

CX_PROXY_INBOUND_APP_ERROR

-

---

ERROR_PART

-

---

>href #o244

-

---

ID APPLICATION_ERROR

-

---

RETRY_MODE M

-

---

ERROR_CLASS_NAME /IWTNG/CX_RS_SAP_GLOBAL_MSGS

--PROVIDER_INFO

---INTERFACE_NAME IWXRead_UserRoles_in

---INTERFACE_NAMESPACE http://xiTest.com/xi/IWCNT

---PROVIDER_INTERFACE /IWTNG/II_IWXREAD_USER_ROLES_I

---OPERATION_NAME employeeGetAll

---OPERATION_NAMESPACE http://xiTest.com/xi/IWCNT

---PROCESSING_UNIT Sector 4: WS-Provider

---PROCESSING_MODE Synchronous

---COMMUNICATION_TYPE Remote

---WORK_PROCESS_NUMBER 7

---WORK_PROCESS_PID 2340

--REQUEST_INFO

---PROTOCOL HTTP/1.1

---REQUEST_URI /sap/bc/srt/pm/iwtng/iwxread_userroles_in/400/duet_enterprise_saml/1/binding_t_https_a_wsse__-iwtng_-iwxread_userroles_in_duet_e

---REMOTE_ADDRESS 10.0.1.111

Thanks & Regards,

Kris

[Former Member]

Hi Kris,

it says "Application Error", so you should see addition information in the application log /n/iwfnd/view_log (maybe you can increase the logging first so that you see more information).

Maybe when creating your System alias and the RFC destination it points to, you have specified client 123 in your backend system which does not exist?

Regards,

Holger.