on 06-23-2022 10:48 AM
Hi,
we are not able to bind a nodejs application to the Cloud Extensibility service anymore (as of today).
This happens both for the deployment (via MTA) from SAP Business Application Studio, as well as when trying to manually bind the application to the service in our BTP subaccount.
The error we get while deploying is this one:
Error while binding service instance "JOB_BASIC" to application "salesorder-srv": Could not bind service "JOB_BASIC" to application "salesorder-srv": 502 Bad Gateway: CF-ServiceBrokerBadResponse(10001): Service broker error: Service broker s4-service-broker failed with: Internal server error
When trying it manually on BTP (go to the instance of the service > Bound Applications > Create), it fails as well, displaying the following error:
We came across this issue while trying to deploy an updated version of our nodejs application (the application is getting unbound from the service and rebound afterwards, which fails now).
The connection from BTP to our Cloud system is still working for other applications (also making calls with Postman works, using the same destination/connection).
The following note describes a similar problem. The difference to our issue is, that we already have our instance but binding applications to it fails:
https://launchpad.support.sap.com/#/notes/2802766
The issue must be quite new, since deployment of applications (binding the to the same instance as we are trying right now) worked the last few days without any problems.
Any help is appreciated.
Thanks
Daniel
Dear Daniel,
If you're still facing the issue I recommend you to open an incident to Product Support.
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi schneider.dnl
Could you please confirm if your cloud system is S/4HANA Cloud, Essential Edition?
Thanks and regards,
Marissa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marissa,
yes exactly, we are using S/4HANA Cloud (I think it was called "Public Cloud" or "Essential Edition" before, or now again - I'm not sure).
We have the issue on our Q system. On our P system it still works, but we would ofc need to be able to have it also running on Q.
Thank you
Daniel
User | Count |
---|---|
77 | |
9 | |
8 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.