Answered

On-Premise Data Gateway with Custom REST API Connector

Like (1) Share

Report

Posted on 4 Jul 2024 16:50:54 by thxmike

I have a Custom REST API Connector which connects to an on-premise API and works fine with our test system via our On-Premise Gateway. However, when I setup the connector to connect to a production system, I get an error from the On-premise Gateway as follows:

response header:

{
"cache-control": "no-cache,no-store",
"content-length": "447",
"content-type": "application/json; charset=utf-8",
"date": "Thu, 04 Jul 2024 16:44:52 GMT",
"expires": "-1",
"pragma": "no-cache",
"strict-transport-security": "max-age=31536000; includeSubDomains",
"x-content-type-options": "nosniff",
"x-frame-options": "DENY",
"x-ms-apihub-cached-response": "true",
"x-ms-apihub-obo": "false",
"x-ms-connection-gateway-object-id": "c6f54a1c-892a-492e-9b48-cafa5bf15933",
"x-ms-request-id": "074f39c0-4925-4cbb-bea4-81bc7bbf8697"
}

response body

{
"status": 500,
"message": "Received error payload from gateway service with ID 2601503: <ccon>An error occurred while sending the request.</ccon>.\r\nclientRequestId: 074f39c0-4925-4cbb-bea4-81bc7bbf8697",
"error": {
"message": "Received error payload from gateway service with ID 2601503: <ccon>An error occurred while sending the request.</ccon>."
},
"source": "gatewayconnector-scus.azconn-scus-001.p.azurewebsites.net"
}

The API works fine if you connect to it directly from on-premise.
I have tried search for this error and nothing.

How do you troubleshoot something like this? Where would I get logs for this type of error? Is there a way to trace the request?

Any assistance would be appreciated?

Categories:

Connectors

Connecting to Data

All responses (2)

Answers (1)

Michael E. Gernaey 42,405 Super User 2025 Season 1 on 04 Jul 2024 at 17:29:09

Like (0)

Report

Re: On-Premise Data Gateway with Custom REST API Connector

HI @thxmike

A couple of things

1. You mentioned that it works from Onpremis, but did you say it also works from the Cloud (in Dev/Test) Correct?

2. Does your API do any logging? I ask because the first thing would be to look there. Assume its getting there and look at what the API is doing with it

3. Do you by chance have any VM's in the cloud? Ones that you could use PostMan on to do some testing? Or is this API important enough to get approval for a small VM for a few days time (wouldn't cost much)

4. When in Test, is the API Cert protected??? SSL??? If so is there any chance in Production you don't have the certs?

5. What user account is this running as in Production? Is it different than Dev/Test?

6. You should be able to run the Gateway install service and go to Diagnostics and export the logs as well as look at the status.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey
Verified answer

thxmike 23 on 04 Jul 2024 at 17:25:54

Like (0)

Report

Re: On-Premise Data Gateway with Custom REST API Connector

After digging into this, I found out that there was a typo. Doh. I wish the error was a little more clear