Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I'm attempting to login via Power BI Desktop to Google Query using a Service Account with a json p/w. I cannot log back in as I'm getting the below error.
Solved! Go to Solution.
It is either you have incompatible drivers, corrupted authentication files, or issues within the Power BI environment itself.
I have a doubt with the key is malformed, outdated, or if the connector is not properly configured.
Try to clear any stored credentials related to Google BigQuery under Data Source Settings, and consider switching to the ODBC connector by installing the official Google BigQuery ODBC driver and configuring a DSN with your service account JSON.
One last thing, try running Power BI as Administrator and temporarily disable antivirus software to rule out interference. If the problem persists, check the Power BI logs under %LOCALAPPDATA%\Microsoft\Power BI Desktop\ may provide more detail about the crash.
Hi @deeave ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Chaithanya.
I put the solution to a response last week in this thread. Hi Amirabedh - It ended up being an issue with the key. The key was created on a mac that displays several lines of code where you need it to be one single line of code for a windows machine.
Hi @deeave,
These are Some troubleshooting steps to overcome your issue:
1)Never open/edit the JSON key in default text editors like Notepad or TextEdit.
2)Use VS Code, Notepad++, or any structured JSON editor that preserves formatting.
3)Ensure the "private_key" field is Enclosed in double quotes.
One long string (even though it appears to be multiline in terminal, it should be escaped properly inside the JSON).
awk 'NF { printf "%s", $0 }' key.json > key_single_line.json (For Mac)
(Get-Content key.json -Raw).Replace("`r`n", "") | Set-Content key_clean.json (For Windows)
This command is used to convert a multi-line file (like a JSON key) into a single-line version — especially useful when dealing with improperly formatted private_key fields in Google service account files.
Regards,
Chaithanya.
It has been resolved, but thank you so much. The wrong key type was provided. (Mac vs Windows)
Hi @deeave ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Chaithanya.
It is either you have incompatible drivers, corrupted authentication files, or issues within the Power BI environment itself.
I have a doubt with the key is malformed, outdated, or if the connector is not properly configured.
Try to clear any stored credentials related to Google BigQuery under Data Source Settings, and consider switching to the ODBC connector by installing the official Google BigQuery ODBC driver and configuring a DSN with your service account JSON.
One last thing, try running Power BI as Administrator and temporarily disable antivirus software to rule out interference. If the problem persists, check the Power BI logs under %LOCALAPPDATA%\Microsoft\Power BI Desktop\ may provide more detail about the crash.
Hi Amirabedh - It ended up being an issue with the key. The key was created on a mac that displays several lines of code where you need it to be one single line of code for a windows machine. 🙂
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 40 | |
| 37 | |
| 33 | |
| 29 | |
| 27 |
| User | Count |
|---|---|
| 131 | |
| 104 | |
| 61 | |
| 57 | |
| 55 |