Forum Discussion
Initialization of data source failed - Excel Power BI connection
What we have found is that the connection string to the model appears to have a setting/variable which Microsoft have potentially removed.
Below is the old connection string used across our various Excel files, which would output the above error. Removing the part in bold appears to fix the issue.
Provider=MSOLAP.8;Integrated Security=ClaimsToken;Persist Security Info=True;Initial Catalog=<redacted>;Data Source=pbiazure://api.powerbi.com;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error;Identity Provider=https://login.microsoftonline.com/common, https://analysis.windows.net/powerbi/api, <redacted>;Catalog Rebound=True;Update Isolation Level=2
Thought I'd post in case anybody was coming across the same issue, as I'm sure these connection strings were automatically generated when we set the files up.
What we have found is that the connection string to the model appears to have a setting/variable which Microsoft have potentially removed.
Below is the old connection string used across our various Excel files, which would output the above error. Removing the part in bold appears to fix the issue.
Provider=MSOLAP.8;Integrated Security=ClaimsToken;Persist Security Info=True;Initial Catalog=<redacted>;Data Source=pbiazure://api.powerbi.com;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error;Identity Provider=https://login.microsoftonline.com/common, https://analysis.windows.net/powerbi/api, <redacted>;Catalog Rebound=True;Update Isolation Level=2
Thought I'd post in case anybody was coming across the same issue, as I'm sure these connection strings were automatically generated when we set the files up.
I have just spent 5 hours trying to solve this! Including a phone call with Customer Support.
2 things worked for me:
1. Downgrading office to Version 2407 (Build 17830.20166)
(this post: Excel - Unable to sign into data connection - Microsoft Community)
2. Removing "Catalog Rebound=True" as proposed here by AnonymousThanks!
Thank you! Problem solved after hours of trying everything.
