The 'CONTOSO\account' value of the 'EffectiveUserName' XML for Analysis property is not valid. For more information, see Grant server admin rights to an Analysis Services instance. If the underlying error message is similar to the following, this means that the account you're using for the data source isn't a server admin for that Analysis Services instance.
Mashup down code#
Within Show details, you can see an error code of DM_GWPipeline_Gateway_DataSourceAccessError. Be sure to validate the information provided for that data source. You were unable to connect to the specified data source. Details: "We reached the data gateway, but the gateway can't access the on-premises data source." Error: We encountered an error while trying to connect to. You can also look in Event Logs > Applications and Services Logs > On-premises data gateway Service for more information. Within Show details, you can see an error code of DM_GWPipeline_UnknownError. This situation could be the result of the server not being accessible. Be sure to validate that you can connect to the data source from the machine that hosts the gateway. This error might occur for different reasons. Login failed for user 'username'.Įrror: Unable to Connect. For SQL Server, you see something like the following: Cannot open database "AdventureWorks" requested by the login. Within Show details, the error message that was received from the data source is displayed. Verify the name of the database and that the user credential has the proper permission to access that database.
You were able to connect to the server but not to the database that was supplied. Details: "Cannot connect to the database" Make sure the account that's being used matches the authentication method. Also, verify that those credentials can successfully connect to the data source. Verify that you have the correct username and password. For SQL Server, you see a message like the following: Login failed for user 'username'. Details: "Invalid connection credentials" In such cases, the default settings provided are the currently supported scenarios for Power BI. For many data sources and non-Microsoft connectors, connection options may vary between Power BI Desktop, and Manage gateways > Data source settings configurations in the Power BI service. Not all data sources have dedicated articles detailing their connection settings or configuration. To get more information, you can collect and review the logs as described in Collect logs from the on-premises data gateway app.
Mashup down windows#
Restarting the Windows service might allow the communication to be successful. The Power BI service doesn't report the gateway as live. Restart the gateway and try again.Īt the end of configuration, the Power BI service is called again to validate the gateway. Configuration Error: Power BI service reported local gateway as unreachable. If you encounter an issue that isn't listed here, you can use the Power BI Community site. This article discusses some common issues when you use the on-premises data gateway with Power BI. To provide feedback on this article, or the overall gateway docs experience, scroll to the bottom of the article. You're currently in the Power BI content. We've split the on-premises data gateway docs into content that's specific to Power BI and general content that applies to all services that the gateway supports.
0 kommentar(er)
