https://raw.githubusercontent.com/ajmaradiaga/feeds/main/scmt/topics/SAP-Connectivity-service-qa.xmlSAP Community - SAP Connectivity service2024-05-20T11:12:37.168470+00:00python-feedgenSAP Connectivity service Q&A in SAP Communityhttps://community.sap.com/t5/technology-q-a/send-mails-using-on-premise-mail-server-sap-cloud-sdk-java/qaq-p/12780733Send mails using On-premise mail server SAP CLOUD SDK JAVA2023-08-24T14:15:10+02:00alex_aguilerahttps://community.sap.com/t5/user/viewprofilepage/user-id/875007<P>Hello, </P>
<P>I'm trying to use a on-premise mail server using SAP CLOUD SDK JAVA. I didn't find any example of how to do it. I know that in case of javascript there's "email-client" (https://sap.github.io/cloud-sdk/docs/js/features/mail-client#on-premise-destination), but for <STRONG>java</STRONG>? </P>
<P>I found this guide: <A href="https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/using-tcp-protocol-for-cloud-applications?locale=en-US" target="test_blank" rel="noopener noreferrer">https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/using-tcp-protocol-for-cloud-applications?locale=en-US</A></P>
<P>But it's not a full example, and it's not very clear. Right now, I have a working code that uses Java Mail to send mails using a mail destination (getting destination properties and creating the mail session), but i don't have very clear how to do it with an on-premise destination and use the configured cloud connector. </P>
<P>Could someone share some code example? </P>
<P>Thanks.</P>2023-08-24T14:15:10+02:00https://community.sap.com/t5/technology-q-a/approuter-consuming-btp-destination-with-client-certificate-authentication/qaq-p/12784787Approuter consuming BTP Destination with Client certificate authentication2023-08-24T22:44:32+02:00SAPSupporthttps://community.sap.com/t5/user/viewprofilepage/user-id/121003<P>Hi SAP Team,<BR /><BR />We are trying to consume API service with SAP BTP Destination service destination type Private link. URL mentioned in Private link destination type only supports client certificate based authentication. <BR /><BR />Source UI5 App Router application is deployed on BTP. We would like to know if there is any way UI5 App Router can consume Private link destination endpoint with client certificate based authentication. Can you please help with mentioned use case ?<BR /><BR />Thanks,</P><BR />------------------------------------------------------------------------------------------------------------------------------------------------<BR /><B>Learn more about the SAP Support user and program <A href="https://blogs.sap.com/2021/09/20/maximizing-the-power-of-sap-community-at-product-support/" target="_blank" rel="noopener noreferrer">here</A>.</B>2023-08-24T22:44:32+02:00https://community.sap.com/t5/technology-q-a/auto-renew-for-btp-generated-certificates/qaq-p/12732244Auto-Renew for BTP Generated Certificates2023-09-01T12:52:34+02:00SAPSupporthttps://community.sap.com/t5/user/viewprofilepage/user-id/121003<P>We are using the feature 'Generate Certificate' on the Destination Service.</P>
<P>Is it possible through the UI or API or some other self service option to verify if a certificate is set to auto renew? This way we can double check after creation that the certificate was set to auto-renew. <BR /><BR />Additionally, if a certificate was not set to auto-renew, is it possible to after the creation set it to auto renew?<BR /><BR /></P><BR />------------------------------------------------------------------------------------------------------------------------------------------------<BR /><B>Learn more about the SAP Support user and program <A href="https://blogs.sap.com/2021/09/20/maximizing-the-power-of-sap-community-at-product-support/" target="_blank" rel="noopener noreferrer">here</A>.</B>2023-09-01T12:52:34+02:00https://community.sap.com/t5/technology-q-a/best-practice-for-app-to-app-communication-within-portal-service/qaq-p/12799933Best practice for App to App communication within Portal Service2023-10-10T22:32:31+02:00mihailebhttps://community.sap.com/t5/user/viewprofilepage/user-id/131995<P> I am trying to sort our the best solution for our customer to implement the way to refer to a UI5 application from a different UI5 application.</P>As of now, there is one UI5 application called “ app1”, which refers to functionality that is included in other UI5 applications. To do so, the applications builds the destination UI5 application url using the “Destination GUID” property, which is automatically generated for each applications when it is deployed into BTP .
<BR /> So, for example to refer to the “common” application, “ app1” application uses the following url which includes the “Destination GUID”:
<BR /> dev:
<CODE> </CODE>"/0ffaea24-4c93-4b0d-8601-36d0f7ab62ed.common-1.0.0". Is this best practice to refer to an app by it's destination GUID. Is there another way? Thank you2023-10-10T22:32:31+02:00https://community.sap.com/t5/technology-q-a/how-to-change-password-using-bapi-user-change-in-pyrfc/qaq-p/12731947How to change password using BAPI_USER_CHANGE in pyrfc?2023-10-13T12:20:55+02:00jeiehttps://community.sap.com/t5/user/viewprofilepage/user-id/882406<PRE><CODE>from pyrfc import Connection
...
conn = Connection(**conn_params)
PASSWORD = {"PASSWORD":'123456'}
PASSWORDX = {"PASSWORD":'X'}
result = conn.call("BAPI_USER_CHANGE",USERNAME='RPA123456',PASSWORD = PASSWORD,PASSWORDX = PASSWORDX)
...</CODE></PRE> Report an error:pyrfc._exception.ExternalRuntimeError: 20 (rc=20): key=RFC_INVALID_PARAMETER, message=field 'PASSWORD' not found [MSG: class=, type=, number=, v1-4:=;;;]
<P>Can anyone help get the correct syntax for BAPI_USER_CHANGE to run in Python?</P>2023-10-13T12:20:55+02:00https://community.sap.com/t5/technology-q-a/sap-cloud-integration-connectivity-with-on-premise-mysql-database/qaq-p/12767976SAP CLOUD INTEGRATION CONNECTIVITY WITH On-Premise MYSQL database2023-10-24T07:35:43+02:00Dhinesh_kumar27https://community.sap.com/t5/user/viewprofilepage/user-id/166515<P>Hello Experts,<BR /><BR />I have an integration scenario to integrate MYSQL on-premise Database using SAP Integration suite.<BR />I understand JDBC adapter currently don't support MYSQL connectivity . The option is to use 'Open Connectors'.<BR />But, the challenge here is it's an on-premise Database. So, trying to understand if opening ports of on-premise MYSQL to internet would allow us to use Open Connectors?<BR /><BR />If a white listing required , does open connectors also uses the IP range mentioned in <A href="https://help.sap.com/docs/btp/sap-business-technology-platform/regions-and-api-endpoints-available-for-cloud-foundry-environment" target="test_blank" rel="noopener noreferrer">https://help.sap.com/docs/btp/sap-business-technology-platform/regions-and-api-endpoints-available-for-cloud-foundry-environment</A></P>2023-10-24T07:35:43+02:00https://community.sap.com/t5/technology-q-a/sac-live-data-tunnel-connection-ina-role-issue-seeking-assistance-from/qaq-p/12742656SAC Live Data Tunnel Connection - InA Role Issue (Seeking Assistance from Experts)2023-11-10T07:22:44+01:00Colthttps://community.sap.com/t5/user/viewprofilepage/user-id/59375<P>Hello Community,</P>
<P>I have a question for SAP Analytics Cloud experts regarding SAC Live Data Tunnel Connections in conjunction with the Cloud Connector (CC) and Principal Propagation (PP) for a S/4HANA on-prem system (Embedded BW). We are currently in the process of migrating a customer from Live Data Direct Connection (CORS) to Tunnel. </P>
<P>For configuration, we have followed the steps outlined in these two sources: [<A href="https://blogs.sap.com/2021/05/18/live-data-connection-to-sap-bw-or-sap-bw-4hana-using-a-tunnel-connection/" rel="noopener noreferrer">Link 1</A>] and [<A href="https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/aa97e36b36624eaa9029b02bdb779b13.html?q=Tunnel" rel="noopener noreferrer">Link 2</A>]</P>
<P>In essence, all preliminary work on the S/4HANA system (Embedded BW) is completed, the CC reaches the system, and is also connected to the SAC Tenant (BTP subaccount). Trust is established between CC<>SAC/BTP and CC<>S/4HANA. PP is configured. Auth Node was already configured for the previous CORS setup that worked fine. Access to the GetServerInfo node is also functioning correctly using SAML based on the same IdP as the SAC Tenant login, which is SAML-SSO enabled. Everything looks good.</P>
<P>However, when configuring the connection in SAC, we currently receive the following message: "You do not have permissions to send queries to the remote system. Please ask your administrator to assign you the InA role."</P>
<P>We have already searched through several SAP Notes and haven't found much helpful information. I would be interested to know if anyone might be familiar with the error and can narrow down the cause.</P>
<P>Thanks for any helpful hints.</P>
<P>Cheers Carsten</P>2023-11-10T07:22:44+01:00https://community.sap.com/t5/technology-q-a/cloud-identity-services-connectivity-plan/qaq-p/12779383Cloud Identity Services - connectivity plan2023-11-21T06:10:45+01:00SushantShindehttps://community.sap.com/t5/user/viewprofilepage/user-id/11208<P>Dear Experts,</P>
<P>Can you please help me understand that by default we only have one Connectivity plan for Cloud Identity Services.</P>
<P>But, we have 2 IAS(Test, Prod) tenants allocated to the customer, So especially, when I have to read users from Abap WAS I need a Connectivity plan and as I have already used it for my Test tenant, how can I manage to read users for my Prod Tenant.</P>
<P>If, I have used it for my Test sub account, So is it so that for reading users for my Prod IAS tenant I will have to read it through my Test sub account. If this is true, it morally sounds incorrect or else is there any other way please leave a comment. </P>
<P>Please don’t suggest purchasing a new Connectivity plan as that incurs a cost. I am looking for any cost effective way for the customer.</P>
<P>Regards,</P>
<P>Sushant</P>2023-11-21T06:10:45+01:00https://community.sap.com/t5/technology-q-a/cap-node-js-application-calls-s-4-on-premise-service-via-cloud-connector/qaq-p/12738476CAP Node.js application calls S/4 on-premise service via cloud connector2023-11-30T17:30:14+01:00former_member634428https://community.sap.com/t5/user/viewprofilepage/user-id/634428<P>Hi all,</P>
<P>I have a CAP node.js application which calls a S/4 on-premise service via cloud connector. I have the following destination set up:</P>
<P><IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2229297-image.png" /></P>
<P>As you can see, I used "NoAuthentication" however I received the following error when my CAP application is trying to communication with the destination:</P>
<P><IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2229298-image.png" /></P>
<P>I was really confused by this error because I did not even choose Principal Propagation so I do not know why I got this error. Can you please help with this?</P>
<P>Thanks in advance</P>
<P>Dan</P>2023-11-30T17:30:14+01:00https://community.sap.com/t5/technology-q-a/which-type-of-service-can-i-connect-for-on-premise-to-cloud-on-sap-cloud/qaq-p/12817498Which type of service can I connect for On-Premise to Cloud on SAP Cloud Connector?2024-01-04T03:19:46+01:00khangtangtuonghttps://community.sap.com/t5/user/viewprofilepage/user-id/1118195<P>I have read some documents about the Connectivity of SAP BTP, it usually shows that On-Premise to Cloud is a connection that connects Apps, DB Tools, Dev Tools and Replication Tools to SAP HANA Cloud. I'd want to ask, "Aside from SAP HANA Cloud, are there any other services to which the On-Premise can connect?"</P>
<P><IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2232305-image.png" /></P>2024-01-04T03:19:46+01:00https://community.sap.com/t5/technology-q-a/sap-btp-to-sftp-connectvity/qaq-p/12817767SAP btp to sftp connectvity2024-01-08T12:23:15+01:00vijaygn1990https://community.sap.com/t5/user/viewprofilepage/user-id/892077<P>Hi Team,<BR />I am trying to achive a use case of reading a simple file placed in an sftp server. Below are the steps followed. Please help to advise as am not able to achieve the connection succesfuly.</P>
<P>1. Created Cloud connector with backend SFTP server. When pinged, says connectivity established.</P>
<P>2. Created a destination pointing to the cloud connector and the connectivty works in the console.<BR /><BR />But I wrote my nodejs code where i first connect to connector proxy and from there to sftp server. But its says timeout. Can help to point the right way to do it.I followed this blog but of no luck</P>
<P><A href="https://stackoverflow.com/questions/70715068/sftp-through-http-proxy-using-ssh2-sftp-client-library-in-node-js" target="test_blank" rel="nofollow noopener noreferrer">https://stackoverflow.com/questions/70715068/sftp-through-http-proxy-using-ssh2-sftp-client-library-in-node-js</A></P>
<P>Any help or sample will be greatly appreciated.</P>2024-01-08T12:23:15+01:00https://community.sap.com/t5/technology-q-a/soaprequest-get-removed-how-to-call-soap-service-now/qaq-p/12820133SoapRequest get removed, how to call SOAP service now2024-01-15T10:45:39+01:00former_member802816https://community.sap.com/t5/user/viewprofilepage/user-id/802816<P>Hi Experts,</P>
<P>We are planning to upgrade to SAP Cloud SDK version 5, and we have noticed that the <CODE>SoapRequest</CODE> has been removed in this version. I would like to inquire about the best practices for proceeding with SOAP calls.</P>
<PRE><CODE>HttpDestination destination = DestinationUtil.getHttpDestination(destinationName);<BR />SoapRequest<ProjectWorkBStub> soapReq = new SoapRequest<>(ProjectWorkBStub.class, destination);<BR />ProjectWorkBreakdownStructureElementsByWorkBreakdownStructureElementIDResponse_sync response = soapReq.execute(service -> {<BR /> String host = destination.getUri().toString();<BR /> String path = getProjectWorkBPath(sapMachine);<BR /> String url = host + path;<BR /> log.info("destination host:{}, path:{},url:{}", host, path, url);<BR /> service._getServiceClient().getOptions().getTo().setAddress(url);<BR /> ProjectWorkBreakdownStructureElementsByWorkBreakdownStructureElementIDQuery_sync prCreateRequest = getCreateRequest(wbsElement);<BR /> return service.projectWorkBreakdownStructureElementByWorkBreakdownStructureElementIDQueryResponse_In(prCreateRequest);<BR />});<BR />ProjWBSElmntByWBSElmntIDRsp_sProj proj = response.getProjectWorkBreakdownStructureElementsByWorkBreakdownStructureElementIDResponse_sync().getProject();</CODE></PRE>2024-01-15T10:45:39+01:00https://community.sap.com/t5/technology-q-a/unable-to-add-subaccount-to-cloud-connector/qaq-p/13583228Unable to add subaccount to cloud connector2024-01-27T12:32:27.781000+01:00Swetha1https://community.sap.com/t5/user/viewprofilepage/user-id/1383444<P>Dear Experts,</P><P>I am trying to add my subaccount details to cloud connector. While saving the details, I got the below error.</P><P> </P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Swetha1_0-1706320433415.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/53468i56D31BFE545C2682/image-size/medium?v=v2&px=400" role="button" title="Swetha1_0-1706320433415.png" alt="Swetha1_0-1706320433415.png" /></span></P><P> </P><DIV> </DIV><DIV>I have attached the error file.</DIV><P> </P><P> </P><pre class="lia-code-sample language-abap"><code>FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
FILE_ID:1706230650425
ENCODING:[UTF8|NWCJS:ASCII]
RECORD_SEPARATOR:124
COLUMN_SEPARATOR:35
ESC_CHARACTER:92
COLUMNS:Time|Severity|Logger|Thread|Text|
SEVERITY_MAP:FINEST|Information|FINER|Information|FINE|Information|CONFIG|Information|DEBUG|Information|PATH|Information|INFO|Information|WARNING|Warning|ERROR|Error|SEVERE|Error|FATAL|Error
HEADER_END
2024-01-26 11:57:34,726 +1100#INFO#com.sap.scc.tomcat#localhost-startStop-1# #PropertyDigester.getProperty(catalina.base)
2024-01-26 11:57:53,789 +1100#INFO#com.sap.scc.rt#localhost-startStop-1# #Register shutdown tunnel hook.
2024-01-26 11:57:53,789 +1100#INFO#com.sap.scc.rt#localhost-startStop-1# #Register shutdown SNC hook.
2024-01-26 11:57:53,821 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #Native library sapscc20jni.dll has already been loaded before
2024-01-26 11:57:53,821 +1100#INFO#com.sap.scc.config#SccInstanceChecker# #Start SCC in D:\sap107\sapcc-2.16.1-windows-x64
2024-01-26 11:57:54,493 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #Property networkaddress.cache.ttl is not provided. Use default 86400
2024-01-26 11:57:54,493 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #Property ni.dnscache.ttl is not provided. Use default 86400
2024-01-26 11:57:54,508 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #Read "10" for property networkaddress.cache.negative.ttl
2024-01-26 11:57:54,508 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #Property ni.dnscache.negative.ttl is not provided. Use default 10
2024-01-26 11:57:54,508 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #Init class CpicConnection
2024-01-26 11:57:54,555 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #Own hostname: ACCESSCLIENT4.DEMO4.COM
2024-01-26 11:57:54,555 +1100#INFO#com.sap.scc.jni#SccInstanceChecker# #CpicConnections are ready to use
2024-01-26 11:57:54,742 +1100#INFO#com.sap.scc.config#OtherActiveSccInstanceChecker# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\scc_config.ini
2024-01-26 11:57:54,852 +1100#INFO#com.sap.scc.startup#OtherActiveSccInstanceChecker# #Starting Cloud Connector runtime - check for active instances
2024-01-26 11:57:55,742 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Using keystore D:\sap107\sapcc-2.16.1-windows-x64\config\ks.p12
2024-01-26 11:57:55,742 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\scc_config.ini
2024-01-26 11:57:55,758 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Initialize SCC runtime configuration
2024-01-26 11:57:56,164 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: creating instance took 1281ms
2024-01-26 11:58:04,855 +1100#INFO#com.sap.scc.security#localhost-startStop-1# #New RSA key pair was generated with key size 4096 in 8675 ms
2024-01-26 11:58:05,030 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: registering services took 8866ms
2024-01-26 11:58:05,030 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: checking HA status took 0ms
2024-01-26 11:58:05,032 +1100#ERROR#com.sap.scc.config#localhost-startStop-1# #SCC keystore is not available - D:\sap107\sapcc-2.16.1-windows-x64\scc_config\scc.p12. Create an empy keystore.
2024-01-26 11:58:14,937 +1100#INFO#com.sap.scc.security#localhost-startStop-1# #New RSA key pair was generated with key size 4096 in 9905 ms
2024-01-26 11:58:16,140 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Created a new key with certificate for audit log with serial 1706230694968
2024-01-26 11:58:16,625 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading common data took 11594ms
2024-01-26 11:58:16,625 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Loaded 0 from 0 configured subaccounts
2024-01-26 11:58:16,625 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading accounts took 0ms
2024-01-26 11:58:16,640 +1100#INFO#com.sap.scc.monitor#localhost-startStop-1# #Scheduling history value collector scc-historic-values-collector-1 with period 15000ms
2024-01-26 11:58:16,656 +1100#INFO#com.sap.scc.alerts#localhost-startStop-1# #Scheduling system observer with period 30000ms
2024-01-26 11:58:16,656 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Cleanup timer started -- cleanup starting in one hour from now and then is executed at that time every day
2024-01-26 11:58:16,656 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: initializing services took 31ms
2024-01-26 11:58:16,656 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: restoring account states took 0ms
2024-01-26 11:58:16,656 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading HA state took 0ms
2024-01-26 11:58:16,671 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading LMDB took 0ms
2024-01-26 11:58:16,671 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading changeable JVM properties took 0ms
2024-01-26 11:58:16,671 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: finishing startup took 0ms
2024-01-26 11:58:16,671 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: salvaging custom regions took 0ms
2024-01-26 11:58:16,671 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total subaccount creation time is 0ms
2024-01-26 11:58:16,671 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total audit key generation time is 0ms
2024-01-26 11:58:16,687 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total subaccount initialization time is 0ms
2024-01-26 11:58:16,687 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total time is 21804ms
2024-01-26 11:58:18,203 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Using Tomcat truststore D:\sap107\sapcc-2.16.1-windows-x64\config\ks.p12
2024-01-26 11:58:18,203 +1100#INFO#com.sap.scc.ui#localhost-startStop-1# #Cloud Connector 2.16.1 started on https://accessclient4.demo4.com:8443 (instance role is undefined)
2024-01-26 11:58:18,203 +1100#INFO#com.sap.scc.ui#localhost-startStop-1# #SAP Cloud Connector 2.16.1
JavaWeb: 3.190.4
Tomcat: 8.5.95.0
Tunnel: 2.428.2
Netty: 4.1.100.Final
SCC JNI Lib: 1.3.1
JRE: 1.8.0_241 (Oracle Corporation, C:\Program Files\Java\jdk1.8.0_241\jre)
JVM: Java HotSpot(TM) 64-Bit Server VM (Oracle Corporation, 25.241-b07, mixed mode)
OS: Windows Server 2019 (10.0)
User: ACCESSCLIENT4\SAP107 (SAP107)
Dir: D:\sap107\sapcc-2.16.1-windows-x64
Installation: portable
HA Info: Role undefined
Recent Start: 2024-01-26 11:57:53 +1100
2024-01-26 11:58:18,421 +1100#INFO#org.apache.coyote.http11.Http11Nio2Protocol#CloudConnectorMainThread# #Starting ProtocolHandler ["https-jsse-nio2-8443"]
2024-01-26 11:58:18,437 +1100#INFO#org.apache.catalina.startup.Catalina#CloudConnectorMainThread# #Server startup in 44199 ms
2024-01-26 11:58:40,202 +1100#INFO#com.sap.scc.startup#OtherActiveSccInstanceChecker# #port check succeeded after 0 ms
2024-01-26 12:10:38,139 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Password for user Administrator was changed
2024-01-26 12:10:38,291 +1100#INFO#com.sap.scc.monitor#https-jsse-nio2-8443-exec-5# #Stopping history value collector scc-historic-values-collector-1 with period 15000ms
2024-01-26 12:10:38,291 +1100#INFO#com.sap.scc.alerts#https-jsse-nio2-8443-exec-5# #Stopping system observer with period 30000ms
2024-01-26 12:10:38,547 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-5# #Using keystore D:\sap107\sapcc-2.16.1-windows-x64\config\ks.p12
2024-01-26 12:10:38,610 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-5# #Initialize SCC runtime configuration
2024-01-26 12:10:39,206 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-5# #Loaded 0 from 0 configured subaccounts
2024-01-26 12:10:39,215 +1100#INFO#com.sap.scc.monitor#https-jsse-nio2-8443-exec-5# #Scheduling history value collector scc-historic-values-collector-2 with period 15000ms
2024-01-26 12:10:39,254 +1100#INFO#com.sap.scc.alerts#https-jsse-nio2-8443-exec-5# #Scheduling system observer with period 30000ms
2024-01-26 12:10:41,103 +1100#WARN#com.sap.scc.util.JvmUtils#https-jsse-nio2-8443-exec-4# #SAP JVM monitor classes are not available, run without extended monitoring. Root cause: java.lang.ClassNotFoundException: com.sap.jvm.monitor.vm.ThreadAnnotationKey
2024-01-26 12:10:41,103 +1100#INFO#com.sap.scc.rt#https-jsse-nio2-8443-exec-4# #JVM (without monitor classes) is loaded
2024-01-26 12:19:41,795 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Try to create subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:19:41,966 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\scc_config.ini
2024-01-26 12:19:42,168 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\backends.xml
2024-01-26 12:19:42,435 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-3# #2024-01-26 12:19:42,435 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:19:43,581 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-3# #2024-01-26 12:19:43,581 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:19:43,591 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Creating an sslContextProvider for account d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-26 12:19:43,744 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #TLSSocketFactory: enabled are TLSv1, TLSv1.1, TLSv1.2
2024-01-26 12:19:43,816 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-26 12:19:43,816 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #Executing Http Get request to https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f
2024-01-26 12:19:44,948 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f Returned Http Response with code 401
2024-01-26 12:19:44,955 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Stopping enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:19:44,955 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Stopped enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:19:44,963 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-3# #Successfully deleted IDP configuration for tunnel id 'account:///d7533843-005d-406d-8ac9-c4bc666b6e1f'
2024-01-26 12:19:44,991 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-3# #An authorization problem occurred when downloading the configuration. Check the spelling of the subaccount name, user, and password. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:19:44,986 +1100. Consult SAP note 2461997 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: An authorization problem occurred when downloading the configuration. Check the spelling of the subaccount name, user, and password. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:19:44,986 +1100. Consult SAP note 2461997 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 401
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-26 12:22:15,790 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-7# #Try to create subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:22:15,881 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-7# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\scc_config.ini
2024-01-26 12:22:15,896 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-7# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\backends.xml
2024-01-26 12:22:15,896 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-7# #2024-01-26 12:22:15,896 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:22:15,896 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-7# #2024-01-26 12:22:15,896 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:22:15,896 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-7# #Creating an sslContextProvider for account d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-26 12:22:15,896 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-7# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-26 12:22:15,896 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-7# #Executing Http Get request to https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f
2024-01-26 12:22:16,713 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-7# #https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f Returned Http Response with code 401
2024-01-26 12:22:16,715 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-7# #Stopping enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:22:16,715 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-7# #Stopped enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:22:16,717 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-7# #Successfully deleted IDP configuration for tunnel id 'account:///d7533843-005d-406d-8ac9-c4bc666b6e1f'
2024-01-26 12:22:16,726 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-7# #An authorization problem occurred when downloading the configuration. Check the spelling of the subaccount name, user, and password. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:22:16,725 +1100. Consult SAP note 2461997 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: An authorization problem occurred when downloading the configuration. Check the spelling of the subaccount name, user, and password. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:22:16,725 +1100. Consult SAP note 2461997 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 401
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-26 12:35:24,004 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-2# #Invalid or missing input
com.sap.scc.servlets.RequestFailureExecution$InvalidRequest: Invalid or missing input
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1425)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
2024-01-26 12:35:32,204 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Proxy changed: null->accessclient4.demo4.com:8443#Administrator/*****. All connected subacounts will be reconnected!
2024-01-26 12:35:32,965 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Try to create subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:35:33,061 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\scc_config.ini
2024-01-26 12:35:33,070 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\backends.xml
2024-01-26 12:35:33,078 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-10# #2024-01-26 12:35:33,078 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:35:33,079 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-10# #2024-01-26 12:35:33,079 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:35:33,079 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Creating an sslContextProvider for account d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-26 12:35:33,124 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-10# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-26 12:35:33,124 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-10# #Executing Http Get request to https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f
2024-01-26 12:35:33,132 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-10# #https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f Returned Http Response with code 400
2024-01-26 12:35:33,132 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Stopping enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:35:33,132 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Stopped enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:35:33,138 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-10# #Successfully deleted IDP configuration for tunnel id 'account:///d7533843-005d-406d-8ac9-c4bc666b6e1f'
2024-01-26 12:35:33,147 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-10# #Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:35:33,146 +1100. Consult SAP note 2460641 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:35:33,146 +1100. Consult SAP note 2460641 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-26 12:40:06,235 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Proxy update not required - no changes detected
2024-01-26 12:40:06,235 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Try to create subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:40:06,338 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\scc_config.ini
2024-01-26 12:40:06,349 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\backends.xml
2024-01-26 12:40:06,349 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-10# #2024-01-26 12:40:06,349 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:40:06,349 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-10# #2024-01-26 12:40:06,349 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:40:06,349 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Creating an sslContextProvider for account d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-26 12:40:06,349 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-10# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-26 12:40:06,349 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-10# #Executing Http Get request to https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f
2024-01-26 12:40:06,349 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-10# #https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f Returned Http Response with code 400
2024-01-26 12:40:06,349 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Stopping enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:40:06,349 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-10# #Stopped enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:40:06,365 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-10# #Successfully deleted IDP configuration for tunnel id 'account:///d7533843-005d-406d-8ac9-c4bc666b6e1f'
2024-01-26 12:40:06,365 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-10# #Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:40:06,365 +1100. Consult SAP note 2460641 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:40:06,365 +1100. Consult SAP note 2460641 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-26 12:40:22,568 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Proxy update not required - no changes detected
2024-01-26 12:40:22,568 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Try to create subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:40:22,651 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\scc_config.ini
2024-01-26 12:40:22,667 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\ap1.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\backends.xml
2024-01-26 12:40:22,667 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-3# #2024-01-26 12:40:22,667 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:40:22,667 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-3# #2024-01-26 12:40:22,667 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_ap1.hana.ondemand.com
2024-01-26 12:40:22,667 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Creating an sslContextProvider for account d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-26 12:40:22,667 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-26 12:40:22,667 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #Executing Http Get request to https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f
2024-01-26 12:40:22,683 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #https://connectivitycertsigning.ap1.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f Returned Http Response with code 400
2024-01-26 12:40:22,683 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Stopping enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:40:22,683 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Stopped enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com
2024-01-26 12:40:22,683 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-3# #Successfully deleted IDP configuration for tunnel id 'account:///d7533843-005d-406d-8ac9-c4bc666b6e1f'
2024-01-26 12:40:22,698 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-3# #Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:40:22,698 +1100. Consult SAP note 2460641 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-26 12:40:22,698 +1100. Consult SAP note 2460641 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7533843-005d-406d-8ac9-c4bc666b6e1f@ap1.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-26 12:58:16,710 +1100#INFO#com.sap.scc.config#Cleanup# #File compression summary: files checked: 1, files compressed: 0, failures: 0
FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
FILE_ID:1706315676725
ENCODING:[UTF8|NWCJS:ASCII]
RECORD_SEPARATOR:124
COLUMN_SEPARATOR:35
ESC_CHARACTER:92
COLUMNS:Time|Severity|Logger|Thread|Text|
SEVERITY_MAP:FINEST|Information|FINER|Information|FINE|Information|CONFIG|Information|DEBUG|Information|PATH|Information|INFO|Information|WARNING|Warning|ERROR|Error|SEVERE|Error|FATAL|Error
HEADER_END
2024-01-27 11:34:41,115 +1100#INFO#com.sap.scc.tomcat#localhost-startStop-1# #PropertyDigester.getProperty(catalina.base)
2024-01-27 11:34:51,814 +1100#INFO#com.sap.scc.rt#localhost-startStop-1# #Register shutdown tunnel hook.
2024-01-27 11:34:51,817 +1100#INFO#com.sap.scc.rt#localhost-startStop-1# #Register shutdown SNC hook.
2024-01-27 11:34:51,855 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #Native library sapscc20jni.dll has already been loaded before
2024-01-27 11:34:51,855 +1100#INFO#com.sap.scc.config#OtherActiveSccInstanceChecker# #Start SCC in D:\sap107\sapcc-2.16.1-windows-x64
2024-01-27 11:34:52,562 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #Property networkaddress.cache.ttl is not provided. Use default 86400
2024-01-27 11:34:52,563 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #Property ni.dnscache.ttl is not provided. Use default 86400
2024-01-27 11:34:52,565 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #Read "10" for property networkaddress.cache.negative.ttl
2024-01-27 11:34:52,566 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #Property ni.dnscache.negative.ttl is not provided. Use default 10
2024-01-27 11:34:52,566 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #Init class CpicConnection
2024-01-27 11:34:52,621 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #Own hostname: ACCESSCLIENT4.DEMO4.COM
2024-01-27 11:34:52,621 +1100#INFO#com.sap.scc.jni#OtherActiveSccInstanceChecker# #CpicConnections are ready to use
2024-01-27 11:34:53,527 +1100#INFO#com.sap.scc.startup#OtherActiveSccInstanceChecker# #Starting Cloud Connector runtime - check for active instances
2024-01-27 11:34:53,647 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Using keystore D:\sap107\sapcc-2.16.1-windows-x64\config\ks.p12
2024-01-27 11:34:53,723 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Initialize SCC runtime configuration
2024-01-27 11:34:53,915 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: creating instance took 1062ms
2024-01-27 11:35:02,719 +1100#INFO#com.sap.scc.security#localhost-startStop-1# #New RSA key pair was generated with key size 4096 in 8793 ms
2024-01-27 11:35:02,889 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: registering services took 8973ms
2024-01-27 11:35:02,889 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: checking HA status took 0ms
2024-01-27 11:35:04,028 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading common data took 1139ms
2024-01-27 11:35:04,030 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Loaded 0 from 0 configured subaccounts
2024-01-27 11:35:04,030 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading accounts took 1ms
2024-01-27 11:35:04,105 +1100#INFO#com.sap.scc.monitor#localhost-startStop-1# #Scheduling history value collector scc-historic-values-collector-1 with period 15000ms
2024-01-27 11:35:04,143 +1100#INFO#com.sap.scc.alerts#localhost-startStop-1# #Scheduling system observer with period 30000ms
2024-01-27 11:35:04,145 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Cleanup timer started -- cleanup starting in one hour from now and then is executed at that time every day
2024-01-27 11:35:04,145 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: initializing services took 115ms
2024-01-27 11:35:04,145 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: restoring account states took 0ms
2024-01-27 11:35:04,147 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading HA state took 2ms
2024-01-27 11:35:04,149 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading LMDB took 2ms
2024-01-27 11:35:04,150 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: loading changeable JVM properties took 1ms
2024-01-27 11:35:04,159 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: finishing startup took 9ms
2024-01-27 11:35:04,159 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: salvaging custom regions took 0ms
2024-01-27 11:35:04,160 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total subaccount creation time is 0ms
2024-01-27 11:35:04,160 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total audit key generation time is 0ms
2024-01-27 11:35:04,160 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total subaccount initialization time is 0ms
2024-01-27 11:35:04,160 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #SccConfig initialization: total time is 11307ms
2024-01-27 11:35:05,687 +1100#INFO#com.sap.scc.config#localhost-startStop-1# #Using Tomcat truststore D:\sap107\sapcc-2.16.1-windows-x64\config\ks.p12
2024-01-27 11:35:05,688 +1100#INFO#com.sap.scc.ui#localhost-startStop-1# #Cloud Connector 2.16.1 started on https://accessclient4.demo4.com:8443 (master)
2024-01-27 11:35:05,689 +1100#INFO#com.sap.scc.ui#localhost-startStop-1# #SAP Cloud Connector 2.16.1
JavaWeb: 3.190.4
Tomcat: 8.5.95.0
Tunnel: 2.428.2
Netty: 4.1.100.Final
SCC JNI Lib: 1.3.1
JRE: 1.8.0_241 (Oracle Corporation, C:\Program Files\Java\jdk1.8.0_241\jre)
JVM: Java HotSpot(TM) 64-Bit Server VM (Oracle Corporation, 25.241-b07, mixed mode)
OS: Windows Server 2019 (10.0)
User: ACCESSCLIENT4\SAP107 (SAP107)
Dir: D:\sap107\sapcc-2.16.1-windows-x64
Installation: portable
HA Info: Master (HA disabled)
Recent Start: 2024-01-27 11:34:51 +1100
2024-01-27 11:35:05,860 +1100#INFO#org.apache.coyote.http11.Http11Nio2Protocol#CloudConnectorMainThread# #Starting ProtocolHandler ["https-jsse-nio2-8443"]
2024-01-27 11:35:05,865 +1100#INFO#org.apache.catalina.startup.Catalina#CloudConnectorMainThread# #Server startup in 25306 ms
2024-01-27 11:35:40,259 +1100#WARN#com.sap.scc.util.JvmUtils#https-jsse-nio2-8443-exec-3# #SAP JVM monitor classes are not available, run without extended monitoring. Root cause: java.lang.ClassNotFoundException: com.sap.jvm.monitor.vm.ThreadAnnotationKey
2024-01-27 11:35:40,259 +1100#INFO#com.sap.scc.rt#https-jsse-nio2-8443-exec-3# #JVM (without monitor classes) is loaded
2024-01-27 11:35:47,316 +1100#INFO#com.sap.scc.startup#OtherActiveSccInstanceChecker# #port check succeeded after 16 ms
2024-01-27 11:41:37,181 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Proxy update not required - no changes detected
2024-01-27 11:41:37,246 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Try to create subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com
2024-01-27 11:41:37,401 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\cf.ap21.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\scc_config.ini
2024-01-27 11:41:37,673 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\cf.ap21.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\backends.xml
2024-01-27 11:41:37,931 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-3# #2024-01-27 11:41:37,931 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_cf.ap21.hana.ondemand.com
2024-01-27 11:41:39,014 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-3# #2024-01-27 11:41:39,014 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_cf.ap21.hana.ondemand.com
2024-01-27 11:41:39,027 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Creating an sslContextProvider for account d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-27 11:41:39,181 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #TLSSocketFactory: enabled are TLSv1, TLSv1.1, TLSv1.2
2024-01-27 11:41:39,253 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-27 11:41:39,254 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #Executing Http Get request to https://connectivitycertsigning.cf.ap21.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f
2024-01-27 11:41:39,378 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-3# #https://connectivitycertsigning.cf.ap21.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f Returned Http Response with code 400
2024-01-27 11:41:39,379 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Stopping enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com
2024-01-27 11:41:39,379 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-3# #Stopped enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com
2024-01-27 11:41:39,390 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-3# #Successfully deleted IDP configuration for tunnel id 'account:///d7533843-005d-406d-8ac9-c4bc666b6e1f'
2024-01-27 11:41:39,412 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-3# #Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-27 11:41:39,409 +1100. Consult SAP note 2460641 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-27 11:41:39,409 +1100. Consult SAP note 2460641 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-27 11:45:57,311 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-9# #Proxy update not required - no changes detected
2024-01-27 11:45:57,311 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-9# #Try to create subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com
2024-01-27 11:45:57,408 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-9# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\cf.ap21.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\scc_config.ini
2024-01-27 11:45:57,424 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-9# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\cf.ap21.hana.ondemand.com\d7533843-005d-406d-8ac9-c4bc666b6e1f\backends.xml
2024-01-27 11:45:57,424 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-9# #2024-01-27 11:45:57,424 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_cf.ap21.hana.ondemand.com
2024-01-27 11:45:57,424 +1100#INFO#tracing.payload.d7533843-005d-406d-8ac9-c4bc666b6e1f#https-jsse-nio2-8443-exec-9# #2024-01-27 11:45:57,424 +1100 << Closing trace file for subaccount d7533843-005d-406d-8ac9-c4bc666b6e1f_on_cf.ap21.hana.ondemand.com
2024-01-27 11:45:57,424 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-9# #Creating an sslContextProvider for account d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-27 11:45:57,424 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-9# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-27 11:45:57,424 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-9# #Executing Http Get request to https://connectivitycertsigning.cf.ap21.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f
2024-01-27 11:45:57,440 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-9# #https://connectivitycertsigning.cf.ap21.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7533843-005d-406d-8ac9-c4bc666b6e1f Returned Http Response with code 400
2024-01-27 11:45:57,440 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-9# #Stopping enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com
2024-01-27 11:45:57,440 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-9# #Stopped enabled service channels on d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com
2024-01-27 11:45:57,440 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-9# #Successfully deleted IDP configuration for tunnel id 'account:///d7533843-005d-406d-8ac9-c4bc666b6e1f'
2024-01-27 11:45:57,455 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-9# #Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-27 11:45:57,455 +1100. Consult SAP note 2460641 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-27 11:45:57,455 +1100. Consult SAP note 2460641 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7533843-005d-406d-8ac9-c4bc666b6e1f@cf.ap21.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-27 11:51:59,430 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Proxy update not required - no changes detected
2024-01-27 11:51:59,431 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Try to create subaccount d7f02e2a-b0d3-475a-92e4-0a240f7be82e@cf.us10.hana.ondemand.com
2024-01-27 11:51:59,545 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Configuration file not found: D:\sap107\sapcc-2.16.1-windows-x64\scc_config\cf.us10.hana.ondemand.com\d7f02e2a-b0d3-475a-92e4-0a240f7be82e\scc_config.ini
2024-01-27 11:51:59,560 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Cannot find host mapping configuration file D:\sap107\sapcc-2.16.1-windows-x64\scc_config\cf.us10.hana.ondemand.com\d7f02e2a-b0d3-475a-92e4-0a240f7be82e\backends.xml
2024-01-27 11:51:59,768 +1100#INFO#tracing.payload.d7f02e2a-b0d3-475a-92e4-0a240f7be82e#https-jsse-nio2-8443-exec-4# #2024-01-27 11:51:59,768 +1100 << Closing trace file for subaccount d7f02e2a-b0d3-475a-92e4-0a240f7be82e_on_cf.us10.hana.ondemand.com
2024-01-27 11:51:59,768 +1100#INFO#tracing.payload.d7f02e2a-b0d3-475a-92e4-0a240f7be82e#https-jsse-nio2-8443-exec-4# #2024-01-27 11:51:59,768 +1100 << Closing trace file for subaccount d7f02e2a-b0d3-475a-92e4-0a240f7be82e_on_cf.us10.hana.ondemand.com
2024-01-27 11:51:59,768 +1100#WARN#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Creating an sslContextProvider for account d7f02e2a-b0d3-475a-92e4-0a240f7be82e@cf.us10.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.
2024-01-27 11:51:59,768 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-4# #Will retrieve Connectivity CA certificate from SAP Business Technology Platform
2024-01-27 11:51:59,768 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-4# #Executing Http Get request to https://connectivitycertsigning.cf.us10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7f02e2a-b0d3-475a-92e4-0a240f7be82e
2024-01-27 11:51:59,783 +1100#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-4# #https://connectivitycertsigning.cf.us10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/d7f02e2a-b0d3-475a-92e4-0a240f7be82e Returned Http Response with code 400
2024-01-27 11:51:59,783 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Stopping enabled service channels on d7f02e2a-b0d3-475a-92e4-0a240f7be82e@cf.us10.hana.ondemand.com
2024-01-27 11:51:59,783 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-4# #Stopped enabled service channels on d7f02e2a-b0d3-475a-92e4-0a240f7be82e@cf.us10.hana.ondemand.com
2024-01-27 11:51:59,783 +1100#INFO#com.sap.core.connectivity.tunnel.client.sso.TrustConfigurationServiceImpl#https-jsse-nio2-8443-exec-4# #Successfully deleted IDP configuration for tunnel id 'account:///d7f02e2a-b0d3-475a-92e4-0a240f7be82e'
2024-01-27 11:51:59,799 +1100#INFO#com.sap.scc#https-jsse-nio2-8443-exec-4# #Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-27 11:51:59,799 +1100. Consult SAP note 2460641 for possible remedies.
com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: Could not download configuration file. See 'Log And Trace Files' and in particular ljs_trace.log for details. Associated entries were logged on or around 2024-01-27 11:51:59,799 +1100. Consult SAP note 2460641 for possible remedies.
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:120)
at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1430)
at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:229)
at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:583)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:679)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1739)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1283)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:646)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:622)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:1008)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:936)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for d7f02e2a-b0d3-475a-92e4-0a240f7be82e@cf.us10.hana.ondemand.com account failed due to unknown exception.
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:225)
at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:115)
... 40 common frames omitted
Caused by: com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400
at com.sap.scc.cert.HttpCertificateManagementService.processRequest(HttpCertificateManagementService.java:143)
at com.sap.scc.cert.HttpCertificateManagementService.executeGetRequest(HttpCertificateManagementService.java:95)
at com.sap.scc.cert.HttpCertificateManagementService.getConnectivityAgentCA(HttpCertificateManagementService.java:66)
at com.sap.scc.ui.SubaccountControl.applyConfig(SubaccountControl.java:180)
... 41 common frames omitted
2024-01-27 11:54:57,224 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-1# #Using draft Tomcat truststore D:\sap107\sapcc-2.16.1-windows-x64\config\ks.p12.draft
2024-01-27 11:56:30,758 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-6# #Proxy update not required - no changes detected
2024-01-27 11:56:57,599 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-6# #Proxy update not required - no changes detected
2024-01-27 12:06:09,035 +1100#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-6# #Proxy update not required - no changes detected
2024-01-27 12:35:04,195 +1100#INFO#com.sap.scc.config#Cleanup# #File compression summary: files checked: 2, files compressed: 0, failures: 0
</code></pre><P> </P><P> </P><DIV><P> </P></DIV><P> </P>2024-01-27T12:32:27.781000+01:00https://community.sap.com/t5/technology-q-a/update-the-certificate-for-a-subaccount-sap-help-portal/qaq-p/13617574Update the Certificate for a Subaccount | SAP Help Portal2024-02-23T22:08:39.956000+01:00royalexahttps://community.sap.com/t5/user/viewprofilepage/user-id/436361<P>Hi Team, we want to update the certificate for the Cloud connector. And we are running into the error which says 'We couldn't find any global accounts associated with this user''</P>2024-02-23T22:08:39.956000+01:00https://community.sap.com/t5/enterprise-resource-planning-q-a/sap-basis-config-oss-comm-new-oss-create-https-connections-for-sap-services/qaq-p/13624540SAP_BASIS_CONFIG_OSS_COMM [New OSS: Create HTTPS Connections for SAP Services (SM59)] SOLMAN 7.22024-03-01T04:49:22.422000+01:00tan_michaelhttps://community.sap.com/t5/user/viewprofilepage/user-id/298091<P>Hi Experts,</P><P>I am trying to configure the SAP_BASIS_CONFIG_OSS_COMM. I am done with the other configuration and we already registered our sap router to SAP but I am stuck in this step New OSS: Create HTTPS Connections for SAP Services (SM59). Whenever I tried to test the connection in SM59 I get the error:<BR />NIECONN_REFUSED(-10). Can you help me with this? <BR />Here is my logs in dev_icm.</P><P><BR />[Thr 9452] Fri Mar 1 10:32:10:672 2024<BR />[Thr 9452] ***LOG Q0I=> NiBufIConnect: connection pending after 5000ms: connect (10035: WSAEWOULDBLOCK: Resource temporarily unavailable) [D:/depot/bas/753_REL/src/base/ni/nibuf.cpp 4593]<BR />[Thr 9452] *** ERROR => NiBufIConnect: non-buffered connect pending after 5000ms (hdl 114;:3299) [nibuf.cpp 4604]<BR />[Thr 9452] *** WARNING => Connect to /H/<public ip>/S/3299/H/169.145.197.110/S/3299/H/notesdownloads.sap.com:443 failed: NIECONN_REFUSED(-10) {0002855c} {root-id=001517DB29811EDEB5FD50E3381320B9} [icxxconn.c 2715]<BR />[Thr 9452] GUI T13_U1243_M0, 001, 2023-0044, CUB-051N, time=10:32:05, W1, program=STC_SCN_MAINTAIN, high priority, memory=0, tasks=1, appl info=, tcode=STC01<BR />[Thr 9452] role: Client, protocol: HTTPS</P>2024-03-01T04:49:22.422000+01:00https://community.sap.com/t5/technology-q-a/the-provided-authorization-grant-is-invalid/qaq-p/13627758The provided authorization grant is invalid2024-03-05T08:27:15.492000+01:00Jwan_https://community.sap.com/t5/user/viewprofilepage/user-id/175626<P>Hello everyone,</P><P>I am getting the error: The provided authorization grant is invalid. Exception was: There is no trust between entities and <A href="https://eu2.hana.ondemand.com/services" target="_blank" rel="nofollow noopener noreferrer">https://eu2.hana.ondemand.com/services</A> in client 027</P><P>when entering the following parameters in BTP destination:</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Jwan__0-1709622644105.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/75345iA49EF172FA91C267/image-size/medium?v=v2&px=400" role="button" title="Jwan__0-1709622644105.png" alt="Jwan__0-1709622644105.png" /></span></P><P> </P><P>followed this tutorial blog: <BR /><A href="https://community.sap.com/t5/customer-relationship-management-blogs-by-sap/configuring-oauth-2-0-between-sap-hybris-cloud-for-customer-and-sap-cloud/ba-p/13323502" target="_blank">https://community.sap.com/t5/customer-relationship-management-blogs-by-sap/configuring-oauth-2-0-between-sap-hybris-cloud-for-customer-and-sap-cloud/ba-p/13323502</A></P><P> </P>2024-03-05T08:27:15.492000+01:00https://community.sap.com/t5/technology-q-a/sap-dm-error-error-user-is-not-authorized-in-cloud-connector/qaq-p/13628405SAP DM error : ERROR_USER_IS_NOT_AUTHORIZED_IN_CLOUD_CONNECTOR2024-03-05T13:33:53.980000+01:00m_ehabhttps://community.sap.com/t5/user/viewprofilepage/user-id/882575<P>After the last SAP DM release, I got this error message while trying to read indicators through production process design:</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="m_ehab_0-1709641221672.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/75711iDD922DEADEEFDD71/image-size/medium?v=v2&px=400" role="button" title="m_ehab_0-1709641221672.png" alt="m_ehab_0-1709641221672.png" /></span></P><P>However, the user that runs the production process is maintained in the production connector user configuration tab and has all roles as follow:</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="m_ehab_1-1709641717340.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/75759i878BE42AC9E17CF4/image-size/medium?v=v2&px=400" role="button" title="m_ehab_1-1709641717340.png" alt="m_ehab_1-1709641717340.png" /></span></P><P>I checked the cloud connector logs and I found this messages :</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="m_ehab_2-1709641736150.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/75760i385FB9BE9E1F0A45/image-size/medium?v=v2&px=400" role="button" title="m_ehab_2-1709641736150.png" alt="m_ehab_2-1709641736150.png" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="m_ehab_3-1709641740932.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/75761i4CEF997CB2B86F1F/image-size/medium?v=v2&px=400" role="button" title="m_ehab_3-1709641740932.png" alt="m_ehab_3-1709641740932.png" /></span></P><P>Principal propagation subject pattern in cloud connector is maintained as follow :</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="m_ehab_4-1709641755985.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/75762iD9D70CD9EDD5E997/image-size/medium?v=v2&px=400" role="button" title="m_ehab_4-1709641755985.png" alt="m_ehab_4-1709641755985.png" /></span></P><P> </P><P> </P>2024-03-05T13:33:53.980000+01:00https://community.sap.com/t5/technology-q-a/abap-platform-trial-1909-error-in-license-check/qaq-p/13667851ABAP Platform Trial 1909 ( error in license check)2024-04-12T09:08:45.521000+02:00filaantohttps://community.sap.com/t5/user/viewprofilepage/user-id/1431543<P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SAP_2_3.png" style="width: 724px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/95496i456B89657EB23B06/image-size/large?v=v2&px=999" role="button" title="SAP_2_3.png" alt="SAP_2_3.png" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SAP_3_3.png" style="width: 999px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/95495i0DD2D4A99ECE263B/image-size/large?v=v2&px=999" role="button" title="SAP_3_3.png" alt="SAP_3_3.png" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SAP_1_3 .png" style="width: 0px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/95494i81B5C42476FE9A16/image-size/small?v=v2&px=200" width="0" height="0" role="button" title="SAP_1_3 .png" alt="SAP_1_3 .png" /></span></P><P>I am new in SAP environment and I got SAP Universal ID</P><P>I referred post <A class="" href="https://community.sap.com/t5/application-development-blog-posts/abap-platform-trial-1909-available-now/ba-p/13567855" target="_blank">ABAP Platform Trial 1909 Available Now</A></P><P>I just pull the docker image and launch command</P><P>docker run --stop-timeout 3600<BR />-i --name a4h -h vhcala4hci -p 3200:3200 -p 3300:3300 -p 8443:8443 -p 30213:30213 -p 50000:50000 -p 50001:50001 sapse/abap-platform-trial:1909_SP01<BR />-skip-limits-check -agree-to-sap-license</P><P>-container is running</P><P>I used SAP GUI to access to the the system set credentials : user: DEVELOPER and password:<EM>ABAPtr1909 </EM></P><P><EM>I got this message : Logon not possible ( error in licence check)</EM></P><P><EM>I lost some steps?</EM></P><P>Some help? Thanks in advance</P><P> </P><P> </P>2024-04-12T09:08:45.521000+02:00https://community.sap.com/t5/technology-q-a/post-payload-to-cpi-iflow-from-ui5-internal-server-error/qaq-p/13680685Post payload to CPI iFlow from UI5 - Internal Server Error2024-04-24T12:20:46.018000+02:00andreeavhttps://community.sap.com/t5/user/viewprofilepage/user-id/172085<P>I need to send a JSON payload to an iFlow, in <STRONG>Postman</STRONG><SPAN> </SPAN>the request is successful (with OAuth2 token retrieval and csrf in header), but the response in<SPAN> </SPAN><STRONG>UI</STRONG><SPAN> </SPAN>is<STRONG> Internal Server Error</STRONG> (the iFlow is also expecting JSON).</P><UL><LI>I am getting csrf token from GET request to CPI instance and pass it in the following POST request to CPI endpoint :</LI></UL><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="andreeav_0-1713953748556.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/101042i82B7E6155570761B/image-size/medium?v=v2&px=400" role="button" title="andreeav_0-1713953748556.png" alt="andreeav_0-1713953748556.png" /></span></P><P> </P><UL><LI>The destination configuration is the following and added in<SPAN> </SPAN><STRONG>xs-app.json</STRONG><SPAN> </SPAN>: <span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="andreeav_0-1713954109632.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/101058i646A7B240484BA33/image-size/medium?v=v2&px=400" role="button" title="andreeav_0-1713954109632.png" alt="andreeav_0-1713954109632.png" /></span><P> </P></LI></UL><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="andreeav_2-1713953748536.png" style="width: 400px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/101041i0D300D73A5B41612/image-size/medium?v=v2&px=400" role="button" title="andreeav_2-1713953748536.png" alt="andreeav_2-1713953748536.png" /></span></P><P>Also<STRONG> curl -v -i cpi.dest </STRONG>returns 500</P><P>* Cpi destination and UI5 app are in different subaccounts.</P><P>- What could be the cause of this?</P>2024-04-24T12:20:46.018000+02:00https://community.sap.com/t5/technology-q-a/denying-access-for-user-to-resource-sap-bc-adt-discovery-on-system/qaq-p/13700250Denying access for user **** to resource /sap/bc/adt/discovery on system ****2024-05-14T08:05:35.802000+02:00UzeyrOzcanhttps://community.sap.com/t5/user/viewprofilepage/user-id/1443256<P>If you encounter a connection error via a cloud connector, one possible reason could be that subpaths have not been granted access permissions. Below is a common error message you might see:</P><DIV class=""><DIV class="">Denying access for user <SPAN class="">****</SPAN> to resource /sap/bc/adt/discovery on system <SPAN class="">****</SPAN></DIV></DIV><P>To resolve this issue, consider the following steps in your configuration:</P><OL><LI><P><STRONG>Update Your Destination Configuration</STRONG>: Ensure that your destination configuration includes "dev_abap" and "ui5_execute_abap" as values in the WebIDEUsage additional property.</P></LI><LI><P><STRONG>Enable the Necessary Service</STRONG>: Verify that the service /sap/bc/adt/ is enabled in your backend system. This can typically be done via the transaction SICF.</P></LI><LI><P><STRONG>Adjust Access Control Settings</STRONG>: Navigate to the 'Cloud To On-Premise' menu and select the 'Access Control' tab. Here, make sure to grant access to the necessary subpaths. Configure your settings as shown in the screenshot below to ensure the problem is resolved.</P></LI></OL><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="UzeyrOzcan_0-1715666606290.png" style="width: 999px;"><img src="https://community.sap.com/t5/image/serverpage/image-id/109949i2EBB8F97383F829C/image-size/large?v=v2&px=999" role="button" title="UzeyrOzcan_0-1715666606290.png" alt="UzeyrOzcan_0-1715666606290.png" /></span></P><P>By following these steps, you should be able to address most connection issues related to cloud connectors effectively.</P><P> </P><P> </P>2024-05-14T08:05:35.802000+02:00