Unanswered

Custom Connector Import Solution - : Connector import: FAILURE: The API call failed with http status code 'InternalServerError' and response content '

(0) Share

Report

Posted on by Lloyd22

When importing a solution containing a custom connector and several environment variables (Azure Key Vault type) I'm experiencing the following error:

failed to import: Connector import: FAILURE: The API call failed with http status code 'InternalServerError' and response content '{"error":{"code":"ApiHubsServerError","message":"Encountered internal server error.

The error has been surfacing both during manual imports and deployments via Azure DevOps power platform build tools. This issue started appearing from November 6, 2023, even though the same solution package was successfully imported without any problems in the preceding week.

Is anyone else experiencing similar issues importing custom connectors? Any help would be much appreciated. Thanks

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Ads87 13 on at

Like (0)

Report
Copy link

Link copied!

Yes, I encountered the exact same issue yesterday importing an update to a previously fine Canvas App Solution with a Custom Connector to an API hosted in Azure.
I use the UK Region normally, but after reading this article ([ALM Accelerator - BUG]: Connector Import Failure : The API call failed with http status code 'InternalServerError' · Issue #4351 · microsoft/coe-starter-kit (github.com)) i tested in a non-EU region (United States) and the same package imported without error.

In investigating the files in the package i have found some config on the package that states US connectivity - so i'm going to have a look there to see if there is a conflict due to that.

Try changing to a different region (create another) in an environment to see if it can be imported there - if so, at least the package itself is ok - and it could be related to the artefact config.

Was this reply helpful? Yes No
Ads87 13 on at

Like (0)

Report
Copy link

Link copied!

Interestingly, the same package now imports this morning without issue.

Was this reply helpful? Yes No
Lloyd22 7 on at

Like (1)

Report
Copy link

Link copied!

Thanks for your reply. The issue seems be intermittent on my end (uk region) - I tested 3 manual imports that all failed then a few hours earlier the package deployed with no issues. Also seeing the error across a few environments.

Oddly, this morning the error was still returned but the solution actually deployed okay whereas yesterday it cancelled the import! Very unpredictable. I've logged a support case with MS so they're aware.

Was this reply helpful? Yes No