Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Anonymous
Not applicable

Account restrictions are preventing this user from signing in - Underlying error code: -2147467259

From last week, I suddenly have the following error message when trying to refresh via on premises data gateway:

 

Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: Items sold.
Underlying error message: AnalysisServices: The following system error occurred: Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind: AnalysisServices
Microsoft.Data.Mashup.ValueError.DataSourcePath: srv-a-36\ssasinst1;Enterprise Intelligence
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: WABI-EUROPE-NORTH-B-redirect.analysis.windows.net
Activity ID: 28ab7b8b-c77d-48bc-985a-7d43020bc0f4
Request ID: 7f270b8c-f208-0e81-e734-39315e7549ef
Time: 2019-07-29 09:06:08Z

 

I tried the following:

- Connected through Excel with exact same credentials to the same source, no problems

- My gateway connections are all checked, no problems

- updated the gateway to the latest version, done, still have the same problem

Only when I refresh via on premises gateway, the problem occurs

- problem only occurs in the reports containing tables/views from the mentioned datasource path

 

Anyone any idea what this can be and how I can solve it? Does this have anything to do with MS updates to the service?

 

Thank you very much in advance!

1 ACCEPTED SOLUTION
Anonymous
Not applicable

In the end the solution was very simple; The effective username in the username mapping for Analysis Services source was set to a personal account. So when we deactivated the personal account, the effective username used in the mapping was no longer valid and the gateway connection was refused. 

Then we created a dedicated user for the gateway in the AD and used this account as the effective username in the user name mapping. 

This username mapping and choosing and effective username is only necessary for connecting to Analysis Services (cubes)

You can read more here: https://docs.microsoft.com/en-us/power-bi/service-gateway-enterprise-manage-ssas#map-user-names-for-...

View solution in original post

3 REPLIES 3
v-xicai
Community Support
Community Support

Hi @Anonymous ,

 

This error message can be caused in different scenarios, however, the following things seem to be the cause most often :

  • Windows Group Policy: Windows policies are responsible for some of the actions that your system performs. The error message is, sometimes, due to a particular Windows Group Policy which stops the Remote Desktop Client to expose sign-in credentials to the remote host. Disabling the policy seems to fix the issue.
  • No Password: In some cases, the error message can also occur if the user account that you are using to establish a remote connection doesn’t have a password. In such a case, you will have to either set a password or just disable this policy as well.

 

For the solutions, you can refer to the links:

https://appuals.com/fix-account-restrictions-are-preventing-this-user-from-signing-in/,

http://windowsbulletin.com/how-to-fix-account-restrictions-are-preventing-this-user-from-signing-in/.

 

You may resolve the issue via the troubleshooting links :

https://docs.microsoft.com/en-us/power-bi/refresh-troubleshooting-refresh-scenarios,

https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot .

 

Best Regards,

Amy

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Anonymous
Not applicable

Thank you for your reply Amy.

Our IT department has investigated the problem with the help of the links you send, but it seems to be a different problem with an external user account (I think it involves credentials for the Analysis Services) that has been disabled lately, which is affecting the gateway identification process.

 

So, still under investigation what exactly is the problem. As soon as I know more, I will update this post.

Anonymous
Not applicable

In the end the solution was very simple; The effective username in the username mapping for Analysis Services source was set to a personal account. So when we deactivated the personal account, the effective username used in the mapping was no longer valid and the gateway connection was refused. 

Then we created a dedicated user for the gateway in the AD and used this account as the effective username in the user name mapping. 

This username mapping and choosing and effective username is only necessary for connecting to Analysis Services (cubes)

You can read more here: https://docs.microsoft.com/en-us/power-bi/service-gateway-enterprise-manage-ssas#map-user-names-for-...

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors