Excel live connected error

[FrancescoSCP]

Hello, I have a client who uses a Power BI model with SQL Server in Import mode.
Once the semantic models are published on the service, they use Excel to connect live to the published model.
The Excel files have always worked, more or less quickly depending on the volume of data and complexity.
A few weeks ago, they changed domains, for example from [email protected] to [email protected].
Now the same Excel files often throw errors and fail to update. Any ideas?

[v-hashadapu]

Hi @FrancescoSCP , Hope your issue is solved. If it is, please consider marking the answer 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details.
Thank you.

[v-hashadapu]

Hi @FrancescoSCP , Hope your issue is solved. If it is, please consider marking the answer 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details.
Thank you.

[v-hashadapu]

Hi @FrancescoSCP , Hope your issue is solved. If it is, please consider marking it 'Accept as solution', so others with similar issues may find it easily. If it isn't, please share the details. Thank you.

[v-hashadapu · Accepted solution]

Hi @FrancescoSCP , thank you for reaching out to the Microsoft Fabric Community Forum.

Please try the following:

1. Ensure that the new domain has the necessary permissions to access the Power BI service and the data sources. Sometimes, domain changes can affect user permissions and access rights.
2. The domain change might have invalidated existing credentials. Update the credentials in Excel to ensure correct login information for the new domain is used.
3. Clear the cache in Excel and Power BI Service. Sometimes, cached credentials or settings can cause issues after a domain change.
4. Re-establish the live connection in Excel.
5. Verify that the data source settings in Power BI are correctly configured for the new domain. Ensure that there are no restrictions or configurations that might be causing the issue.

If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.

[FrancescoSCP]

Hi @v-hashadapu here are my answers:

1. If they create a new simple Excel file connected to the Power BI Service it works good, so they have permission to access with the new domain;
2. They are logged in in Excel with the new domain;
3. How can i clear cache of Excel/Power BI Service?
4. If they create a new Excel file it works, i think the connection works good.
5. Data source are configured through a SQL Server user. Do you mean permission to user to access to the data and workspace?

Thanks in advance

[v-hashadapu]

Hi @FrancescoSCP , thank you for reaching out to the Microsoft Fabric Community Forum.

A. Verifying data source settings in Power BI are correctly configured for the new domain:

Yes, please check user access to data and workspace

1. Ensure that the SQL Server user has the necessary permissions to access the required databases and tables. Permissions should be aligned with the new domain settings.
2. Make sure that the new domain users have the appropriate permissions to access the Power BI workspace where the datasets and reports are published. This includes ensuring that they are added as members or administrators of the workspace.
3. Confirm that the SQL Server user credentials are correctly configured and have the necessary permissions

B. Clearing Cache:

1. Clear Cache in Excel:
   a. Power query Cache = File -> Options -> Data -> Power query Options -> Clear Cache
   b. Excel Cache = In your PC -> %appdata%\Microsoft\Office\Recent

    2. Clear Cache in Power BI Service:

Clear Browser Cache by opening your browser and clearing the browsing data like Cache, Cookies etc.,

C. Re-establishing Connection:

1. Data -> Connections -> Remove the existing connection.
2. Reconnect to the Power BI service by selecting Get Data > From Power BI and enter the necessary credentials.

If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.