Skip to main content

HI All,

 

We received a error when testing the data connection at a client on C4C+ project.

The description of the error is as follows:

 

"Connection test failed, please check the Data Connection's configuration and ensure that the system is running: Error making capabilities request to extractor: Remote application on http://uplink/uplink/api/internal/proxy/90574be94ecede1912b66868c75ec3994e77111b3c097720be3e1e94a41b3865/connector-capabilitiesiPOST] responded with 500 : {"timestamp":1647536076176,"status":500,"error":"Internal Server Error","message":"Could not connect to middleware - client not connected. Client: 90574be94ecede1912b66868c75ec3994e77111b3c097720be3e1e94a41b3865, Channel: connector-capabilities","path":"/uplink/api/internal/proxy/90574be94ecede1912b66868c75ec3994e77111b3c097720be3e1e94a41b3865/connector-capabilities"} "

 

The data connection first worked but after the weekend(11-12 march) we received on monday this error by testing it.

@CelonisTechSupport​ We create two tickets (one at the beginning of the week number 00111694 and second-ticket 00112271 today). But till today we have not received a response from you and still the issue is not solved.

 

Hope you can help us soon as possible since the problem has become urgent!

 

Regards,

 

Debby

Hello,

 

Is your request solved? It seem I have similar problem.

 

Connection test failed, please check the Data Connection's configuration and ensure that the system is running: Error making capabilities request to extractor: Remote application on http://uplink/uplink/api/internal/proxy/<removed>/connector-capabilitiesePOST] responded with 500 : {"timestamp":1647949054086,"status":500,"error":"Internal Server Error","message":"Could not connect to middleware - client not connected. Client: <removed>, Channel: connector-capabilities","path":"/uplink/api/internal/proxy/<removed>/connector-capabilities"} "

 

Best Regards,

Mateusz Dudek


HI Mateusz,

 

No, unfortunately this issue is not resolved yet. We have been working on this for a week now. Have you solved it in the meantime?

 

Our expectation was that the TLS protocol version was to old or the security certificates were overwritten from the client server. but neither turned out to be the case. we are still stuck

 

Best, Debby


Hello Debby,

 

First - check if Celonis extractor service is starting, if no - it may be that the old Java version on the server stopped to be supported.

Updating it to java 11 maybe will solve the issue. Also check if extractor itself is up to date.

 

Also, after each update of the celonis related services, check if they are set to be started automatically after reboot of the server. Some time ago I've got a case (on-prem environment) where it set itself to manual. Because of that after reboot it didn't start, so the front-end was working, but we couldn't make any data loads.

 

Best Regards,

Mateusz Dudek


Reply