Skip to content Skip to sidebar Skip to footer
Home / Relay Could Not Load Profile Refresh to Try Again

Relay Could Not Load Profile Refresh to Try Again

Post a Comment
Skip to chief content

Troubleshoot gateways - Power BI

  • Article
  • 12 minutes to read

This article discusses some common issues when you lot use the on-premises data gateway with Ability BI. If you encounter an issue that isn't listed hither, you tin use the Ability BI Community site. Or, you lot tin create a support ticket.

Configuration

Error: Ability BI service reported local gateway as unreachable. Restart the gateway and effort once more.

At the end of configuration, the Power BI service is called again to validate the gateway. The Ability BI service doesn't study the gateway every bit live. Restarting the Windows service might allow the communication to be successful. To become more than information, you can collect and review the logs as described in Collect logs from the on-bounds data gateway app.

Information sources

Annotation

Not all data sources have dedicated articles detailing their connection settings or configuration. For many data sources and not-Microsoft connectors, connection options may vary between Power BI Desktop, and Manage gateways > Data source settings configurations in the Power BI service. In such cases, the default settings provided are the currently supported scenarios for Power BI.

Error: Unable to Connect. Details: "Invalid connexion credentials"

Within Show details, the error message that was received from the information source is displayed. For SQL Server, you see a message like the post-obit:

              Login failed for user 'username'.

Verify that you have the correct username and password. As well, verify that those credentials can successfully connect to the data source. Make sure the account that's existence used matches the authentication method.

Error: Unable to Connect. Details: "Cannot connect to the database"

You lot were able to connect to the server simply not to the database that was supplied. Verify the name of the database and that the user credential has the proper permission to access that database.

Within Show details, the error bulletin that was received from the data source is displayed. For SQL Server, you meet something like the following:

              Cannot open database "AdventureWorks" requested by the login. The login failed. Login failed for user 'username'.

Error: Unable to Connect. Details: "Unknown error in data gateway"

This fault might occur for dissimilar reasons. Be sure to validate that you lot can connect to the information source from the machine that hosts the gateway. This situation could be the event of the server non beingness accessible.

Inside Prove details, yous can see an error code of DM_GWPipeline_UnknownError.

Yous can likewise look in Event Logs > Applications and Services Logs > On-premises data gateway Service for more information.

Error: We encountered an error while trying to connect to <server>. Details: "We reached the data gateway, merely the gateway tin't admission the on-bounds information source."

Y'all were unable to connect to the specified data source. Be sure to validate the information provided for that information source.

Within Evidence details, you can see an error lawmaking of DM_GWPipeline_Gateway_DataSourceAccessError.

If the underlying error bulletin is similar to the following, this means that the account y'all're using for the information source isn't a server admin for that Analysis Services instance. For more than information, see Grant server admin rights to an Assay Services case.

              The 'CONTOSO\account' value of the 'EffectiveUserName' XML for Assay property is not valid.

If the underlying error bulletin is similar to the post-obit, information technology could mean that the service business relationship for Analysis Services might be missing the token-groups-global-and-universal (TGGAU) directory attribute.

              The username or password is incorrect.

Domains with pre-Windows 2000 compatibility admission have the TGGAU attribute enabled. Most newly created domains don't enable this attribute by default. For more information, see Some applications and APIs crave admission to authorization information on account objects.

To confirm whether the aspect is enabled, follow these steps.

  1. Connect to the Analysis Services motorcar within SQL Server Management Studio. Within the Advanced connectedness properties, include EffectiveUserName for the user in question and see if this addition reproduces the error.

  2. You can use the dsacls Agile Directory tool to validate whether the attribute is listed. This tool is found on a domain controller. Y'all need to know what the distinguished domain name is for the business relationship and pass that proper name to the tool.

                      dsacls "CN=John Doe,CN=UserAccounts,DC=contoso,DC=com"

    Yous want to encounter something like to the following in the results:

                      Allow BUILTIN\Windows Authorization Admission Grouping                                 SPECIAL ACCESS for tokenGroupsGlobalAndUniversal                                 READ Holding

To right this outcome, y'all must enable TGGAU on the account used for the Analysis Services Windows service.

Another possibility for "The username or countersign is wrong."

This error could as well exist caused if the Analysis Services server is in a different domain than the users and at that place isn't a two-way trust established.

Piece of work with your domain administrators to verify the trust relationship between domains.

Unable to see the information gateway data sources in the Get Information feel for Assay Services from the Power BI service

Make certain that your account is listed in the Users tab of the data source within the gateway configuration. If you don't accept access to the gateway, check with the administrator of the gateway and ask them to verify. Merely accounts in the Users listing can see the data source listed in the Analysis Services listing.

Fault: You don't have any gateway installed or configured for the data sources in this dataset.

Ensure that you've added one or more information sources to the gateway, as described in Add a data source. If the gateway doesn't announced in the admin portal under Manage gateways, articulate your browser cache or sign out of the service and so sign back in.

Datasets

Fault: In that location is not enough space for this row.

This error occurs if you lot have a single row greater than 4 MB in size. Determine what the row is from your data source, and attempt to filter it out or reduce the size for that row.

Error: The server name provided doesn't match the server name on the SQL Server SSL document.

This fault tin occur when the certificate mutual name is for the server's fully qualified domain name (FQDN), just y'all supplied only the NetBIOS proper noun for the server. This state of affairs causes a mismatch for the certificate. To resolve this issue, brand the server proper noun within the gateway data source and the PBIX file use the FQDN of the server.

Error: You don't see the on-premises data gateway present when you configure scheduled refresh.

A few different scenarios could be responsible for this error:

  • The server and database proper name don't match what was entered in Power BI Desktop and the information source configured for the gateway. These names must be the aforementioned. They aren't case sensitive.
  • Your account isn't listed in the Users tab of the data source within the gateway configuration. Y'all need to be added to that list by the ambassador of the gateway.
  • Your Power BI Desktop file has multiple information sources inside it, and not all of those data sources are configured with the gateway. You demand to have each data source defined with the gateway for the gateway to show up within scheduled refresh.

Error: The received uncompressed data on the gateway customer has exceeded the limit.

The exact limitation is 10 GB of uncompressed data per tabular array. If y'all're hitting this event, there are adept options to optimize and avoid it. In particular, reduce the use of highly constant, long cord values and instead use a normalized fundamental. Or, removing the column if it'due south not in use helps.

Mistake: DM_GWPipeline_Gateway_SpooledOperationMissing

A few different scenarios could be responsible for this error

  • Gateway procedure may have restarted when the dataset refresh was in progress.
  • The gateway machine is cloned where gateway is running. We should not clone gateway motorcar.

Reports

Error: Report could not admission the data source because you exercise non take access to our data source via an on-premises data gateway.

This error is commonly caused past one of the following:

  • The data source information doesn't match what's in the underlying dataset. The server and database proper noun need to match betwixt the data source defined for the on-premises data gateway and what you supply within Ability BI Desktop. If yous use an IP address in Power BI Desktop, the data source for the on-premises information gateway needs to employ an IP address as well.
  • There's no data source available on whatever gateway inside your organisation. You can configure the data source on a new or existing on-premises data gateway.

Error: Data source admission mistake. Please contact the gateway administrator.

If this report makes use of a live Analysis Services connectedness, you could run across an issue with a value being passed to EffectiveUserName that either isn't valid or doesn't have permissions on the Analysis Services machine. Typically, an authentication issue is due to the fact that the value existence passed for EffectiveUserName doesn't match a local user principal name (UPN).

To confirm the constructive username, follow these steps.

  1. Discover the effective username within the gateway logs.

  2. Subsequently you have the value being passed, validate that it's correct. If it's your user, you tin can apply the post-obit command from a command prompt to see the UPN. The UPN looks like an email address.

                      whoami /upn

Optionally, you tin see what Power BI gets from Azure Active Directory.

  1. Browse to https://developer.microsoft.com/graph/graph-explorer.

  2. Select Sign in in the upper-right corner.

  3. Run the post-obit query. You see a rather large JSON response.

                      https://graph.windows.net/me?api-version=i.v

  4. Wait for userPrincipalName.

If your Azure Active Directory UPN doesn't match your local Active Directory UPN, you can employ the Map user names characteristic to supplant information technology with a valid value. Or, you can work with either your Power BI admin or local Active Directory admin to become your UPN inverse.

Kerberos

If the underlying database server and on-premises data gateway aren't accordingly configured for Kerberos constrained delegation, enable verbose logging on the gateway. Then, investigate based on the errors or traces in the gateway's log files equally a starting indicate for troubleshooting. To collect the gateway logs for viewing, run into Collect logs from the on-premises data gateway app.

ImpersonationLevel

The ImpersonationLevel is related to the SPN setup or the local policy setting.

              [DataMovement.PipeLine.GatewayDataAccess] About to impersonate user DOMAIN\User (IsAuthenticated: True, ImpersonationLevel: Identification)

Solution

Follow these steps to solve the issue.

  1. Set up an SPN for the on-premises gateway.
  2. Gear up constrained delegation in your Agile Directory.

FailedToImpersonateUserException: Failed to create Windows identity for user userid

The FailedToImpersonateUserException happens if you lot're unable to impersonate on behalf of another user. This fault could likewise happen if the account you're trying to impersonate is from another domain than the 1 the gateway service domain is on. This is a limitation.

Solution

  • Verify that the configuration is correct as per the steps in the previous "ImpersonationLevel" section.
  • Ensure that the user ID it'south trying to impersonate is a valid Agile Directory account.

General mistake: 1033 error while yous parse the protocol

You get the 1033 error when your external ID that's configured in SAP HANA doesn't match the sign-in if the user is impersonated by using the UPN (alias@domain.com). In the logs, you lot encounter "Original UPN 'alias@domain.com' replaced with a new UPN 'alias@domain.com'" at the height of the fault logs, as seen here:

              [DM.GatewayCore] SingleSignOn Required. Original UPN 'alias@domain.com' replaced with new UPN 'alias@domain.com.'

Solution

  • SAP HANA requires the impersonated user to utilise the sAMAccountName attribute in Active Directory (user allonym). If this attribute isn't correct, you see the 1033 error.

    Attribute editor

  • In the logs, you see the sAMAccountName (alias) and not the UPN, which is the allonym followed by the domain (allonym@doimain.com).

    Account info in logs 

                              <setting name="ADUserNameReplacementProperty" serializeAs="String">         <value>sAMAccount</value>       </setting>       <setting proper noun="ADServerPath" serializeAs="String">         <value />       </setting>       <setting name="CustomASDataSource" serializeAs="String">         <value />       </setting>       <setting name="ADUserNameLookupProperty" serializeAs="String">         <value>AADEmail</value>

You get the "-10709 Connection failed" mistake message if your delegation isn't configured correctly in Active Directory.

Solution

  • Make sure that you have the SAP Hana server on the delegation tab in Active Directory for the gateway service business relationship.

    Delegation tab

Export logs for a support ticket

Gateway logs are required for troubleshooting and creating a support ticket. Use the following steps for extracting these logs.

  1. Identify the gateway cluster.

    If you're a dataset owner, first bank check the gateway cluster name associated with your dataset. In the following image, IgniteGateway is the gateway cluster.

    Gateway cluster

  2. Check the gateway properties.

    The gateway admin should so bank check the number of gateway members in the cluster and if load balancing is enabled.

    If load balancing is enabled, then step 3 should exist repeated for all gateway members. If it's not enabled, then exporting logs on the primary gateway is sufficient.

  3. Retrieve and export the gateway logs.

    Side by side, the gateway admin, who is also the ambassador of the gateway system, should do the following steps:

    a. Sign in to the gateway car, and then launch the on-bounds data gateway app to sign in to the gateway.

    b. Enable boosted logging.

    c. Optionally, you can enable the performance monitoring features and include performance logs to provide additional details for troubleshooting.

    d. Run the scenario for which you're trying to capture gateway logs.

    e. Export the gateway logs.

Refresh history

When you use the gateway for a scheduled refresh, Refresh history can help you see what errors occurred. It tin can as well provide useful data if you need to create a support request. You tin view scheduled and on-demand refreshes. The post-obit steps show how you tin can get to the refresh history.

  1. In the Power BI nav pane, in Datasets, select a dataset. Open up the menu, and select Schedule refresh.

    How to select schedule refresh

  2. In Settings for..., select Refresh history.

    Select refresh history

    Refresh history display

For more information most troubleshooting refresh scenarios, see Troubleshoot refresh scenarios.

Fiddler trace

Fiddler is a complimentary tool from Telerik that monitors HTTP traffic. You can see the dorsum and forth with the Power BI service from the client machine. This traffic list might evidence errors and other related information.

Using the Fiddler trace

Next steps

  • Troubleshoot the on-premises data gateway
  • Configure proxy settings for the on-premises information gateway
  • Manage your information source - Assay Services
  • Manage your data source - SAP HANA
  • Manage your information source - SQL Server
  • Manage your data source - Import/scheduled refresh

More questions? Try the Power BI Community.

bresciasteat1977.blogspot.com

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

Post a Comment for "Relay Could Not Load Profile Refresh to Try Again"