web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Error trying to create...
Power Apps
Answered

Error trying to create connection to custom connectors using on-premise data gateway

(0) ShareShare
ReportReport
Posted on by 20

Hi fellow community members,

 

I have an app that uses two custom connectors, both of which connect via the same on-premise data gateway. The app and connectors have been working without problems for months. However, when I tried to play the app in the test environment yesterday, my connections to the custom connectors had to be re-established. When I clicked 'Sign in', I got the error "Encountered internal server error. The correlation Id is '[...]". I then tried to add a new connection in the environment via make.powerapps.com. When I clicked the connector name, I could no longer fill in username and password in the pop up; I could only select the gateway. When I selected gateway and clicked 'Create', I got the same error as mentioned before. The issue persists today.

 

Some more information:

  • App and connectors exist in a solution
  • The issue occurs for both connectors across dev, test and prod environments
  • The data gateway is online and is running on the latest version
  • I have tried adding connections with my own user and through a different user, which is custom connector owner and gateway admin (my user is also gateway admin), but the issue occurs for both users
  • I have tried to re-import the solution to the test environment, but this did not solve the problem

 

Has any of you experienced this issue?

Categories:
I have the same question (0)
  • CU08100840-0 Profile Picture
    on at

     Had/having similar issues. It doesnt let us create new connections for custom connectors that are being used by power automate. 

    Our issue with custom connector was that the auth had reset itself to 'No auth' rather than the 'Windows Auth' we had set. Took a few goes to change back but eventually worked. 

    Errors have been changing over last few days so can only assume MS have introduced a bug and are trying to resolve. 

  • Verified answer
    mki1 Profile Picture
    20 on at

    I also figured out that my connectors had reset themselves to 'No auth' rather than the 'Windows Auth' I had set. I just couldn't change this back to 'Windows Auth' even though I tried multiple times.

    I ended up opening a ticket with Microsoft a few days ago, but I actually just closed the ticket as the issues I was experiencing are now resolved. Don't know if the resolution was part of Microsofts investigation of this specific issue or related to something else, but either way, my connectors and connections are working again.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
Haque Profile Picture

Haque 85

#2
WarrenBelz Profile Picture

WarrenBelz 76 Most Valuable Professional

#3
Kalathiya Profile Picture

Kalathiya 38 Super User 2026 Season 1

Last 30 days Overall leaderboard