Unanswered

On-premises data gateway - SharePoint 2013 unauthorized 401

(0) Share

Report

Posted on by LukasNespor

I have installed and configured the on-premises data gateway on on of our SharePoint 2013 server (Windows 2008 R2). The gateway is visible in PowerApps and is working because I'm able to connect to on-prem SQL server. But connecting to on-prem SharePoint 2013 doesn't work and says 401 Unauthorized.

SharePoint site is using SSL and is path based. Login I'm using is correct and able to visit SharePoint site that returns 401 error.

Categories:

Building Power Apps

I have the same question (0)

All responses (23)

Answers (0)

v-micsh-msft on at

Like (0)

Report

Hi LukasNespor,

Could you please share more details about the error message, when did it pop out, under Add New Connection in Browser, or when Trying to New an App with the SharePoint connections?

Please make sure the User account used for the SharePoint Connection is authorized to the SharePoint site that you would like to connect, also make sure the proper gateway is selected:

A reference:

Support for on-premises SharePoint lists

For the SharePoint site that could be accessed through Browser, could you please confirm it again with the Account used to create the SharePoint connection?

If the error message occurred when trying to create a new App with SharePoint connection, then please make sure the user account has the proper permission to access the site level which specified under the site URL.

Add some additional reference:

On-premises data gateway in PowerApps

Regards

Was this reply helpful? Yes No
LukasNespor 14 on at

Like (0)

Report

Error message is just "401 UNAUTHORIZED" with correlation id. It pops out when I try to "Connect to a SharePoint site" (creating new App). Creating connection (where I can select proper gateway) is working but connecting to https://portal.domain.com/sites/somesite ends with error. The account I'm using has access to site and is also able to visit the site in browser. The account is farm admin and has Full control through User policy on web application.

Was this reply helpful? Yes No
v-micsh-msft on at

Like (0)

Report

Hi LukasNespor,

I saw your SharePoint input site URL is the following:

https://portal.domain.com/sites/workflows/mxxx

How about change the SharePoint URL to the following format?

https://portal.domain.com/sites/

See if this would make any difference.

Regards

Was this reply helpful? Yes No
LukasNespor 14 on at

Like (0)

Report

If you mean to add slash to the end of url then no, it doesn't help.

Was this reply helpful? Yes No
v-micsh-msft on at

Like (0)

Report

Hi LukasNespor,

What is your current situation?

Please take a try to modify the URL with the following format:

https://portal.domain.com/

This would list the available source under the top site, check to see if this would work.

If issue still insists, please reply back and I will try to involve others to take a further look.

Regards

Was this reply helpful? Yes No
LukasNespor 14 on at

Like (0)

Report

Hi,
I have found that the issue is with SharePoint itself. Different SharePoint farm and same Office 365 tenant works well. Firewall is turned off . Are there any prerequisities that the server does not meet?

Windows Server 2008 R2 Standard
SharePoint 2013 Ent CU February 2016 (15.0.4797.1000)

Was this reply helpful? Yes No
v-micsh-msft on at

Like (0)

Report

Hi LukasNespor,

Thanks for the update.

I will try to involve others who is familar with this to take a further investigation, there might be some time delay.

Appreciate your understanding and patience.

Regards

Was this reply helpful? Yes No
LukasNespor 14 on at

Like (0)

Report

Hi,
were you able to invole others? Still the same error:
401 UNAUTHORIZED
ID relace: 6acceb07-e92d-17b5-0d6f-1149765c65d6

Thanks

Was this reply helpful? Yes No
alejandrol 6 on at

Like (0)

Report

I'm having the same problem.
Any solution for this?

Was this reply helpful? Yes No
v-micsh-msft on at

Like (0)

Report

Hi @LukasNespor,

Apologizes.

I will forward this again to check the status.

Regards

Was this reply helpful? Yes No