User account not found in MSAL cache, please add linked account or refresh account credentials. #24104
Comments
|
Asure data studio |
|
Please provide more info:
|
cheenamalhotra
added
Bug
Needs More Info
Triage: Needed
Area - Azure
Triage: Done
and removed
Triage: Needed
labels
|
Hi, started having this issue on:
Version: 1.46.0-insider Have followed steps in linked old issues :) |
|
We need more info to debug your Azure Active Directory issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.
|
|
HI @kinglis-ttq Please ensure you also remove accounts, and restart ADS after clearing token cache. If you continue to face error on a clean restart, please gather and upload logs for the session. |
github-project-automation
bot
moved this to Needs triage
in ADS Core Committer and Fundamentals
|
Hi @cheenamalhotra , I have followed all the steps you suggested, and attach the requested logfiles. I have removed the tenant information for my company for security. |
|
[Verbose]: Initialized Azure account extension storage. - [] |
cheenamalhotra
moved this from Needs triage
to Waiting
in ADS Core Committer and Fundamentals
|
I had the same problem, clear cache several times and delete and reinstall DataStudio and DataStudioInsiders. Finally the solution was to log out of the browser and log back in when DataStudio requires it. |
|
I can intermittently reproduce the error and can see the below log entry when this occurs:
I've found some issues logged in MSAL.js that are related here, @cssuh can you take a look at the client app in case something is missing? Also need to investigate why this is more prominent in Linux than other OSes... 🤔 |
cheenamalhotra
moved this from Waiting
to Needs investigation
in ADS Core Committer and Fundamentals
|
another nightmare in the making. A systemic problem with security on Azure where it only works for those internal to MS. |
cheenamalhotra
moved this from Needs investigation
to In Progress
in ADS Core Committer and Fundamentals
That's not accurate, we have thousands of customers outside of Microsoft that do not have this issue. We recognize the frustration you are experiencing and are working to resolve this problem. We can sporadically recreate the problem and are working to track down the root cause. We will provide an update when we have a solution. |
|
Any updates on this yet? Running into problem on my end as well running on Mac M1 Pro Sonoma 14.0 I pay for MS support and they directed me here. Any guidance on the timeline for this fix and where MS is current state so we can know if it's best to pivot to something else would be much appreciated. |
|
Previous comment hidden as it is not relevant to the topic of this issue, nor constructive. |
|
I encountered this issue using Windows Sandbox in which certain cryptographic algorithms and protocols where restricted & had to restore access to those algorithms and protocols in order to proceed with using azure data studio. Version: 1.46.1 (system setup) I'm happy to report using Insider build resolved this issue and I am able to use azure data studio with no issues with the restrictions back in place within Windows Sandbox. Good job to the team 👍 Version: 1.48.0-insider (system setup) |
This worked for me |
|
I just deleted everything Azure and am back to Google. I can't provide a
powerBI solution to my client at this point so we are looking for
something else until this problem is resolved. Also has stopped
development of our PowerApps.
…On Fri, Dec 8, 2023 at 3:45 AM Rob Bowman ***@***.***> wrote:
disabling the *Mssql: Enable Sql Authentication Provider*
This worked for me
—
Reply to this email directly, view it on GitHub
<#24104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3JYLOFJVG2GSLEMEKL63Z3YIL4WJAVCNFSM6AAAAAA3JHNXCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGAZTSNZTG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Edmund Landgraf
***@***.***
***@***.***
415.425.8655 (m/w)
866.209.7487 (vm/fax)
|
|
Edmund,
When you get a second, i would like to chat with you about your decision to leave Azure. I'm finding it a convoluted mess with documentation that has more rabbit holes than a river has rocks.
Have a nice day.
Kevin
https://rb.gy/syiuf
…________________________________
From: edmund-landgraf ***@***.***>
Sent: Saturday, December 9, 2023 9:38 AM
To: microsoft/azuredatastudio ***@***.***>
Cc: Kevin Cabral ***@***.***>; Comment ***@***.***>
Subject: Re: [microsoft/azuredatastudio] User account not found in MSAL cache, please add linked account or refresh account credentials. (Issue #24104)
I just deleted everything Azure and am back to Google. I can't provide a
powerBI solution to my client at this point so we are looking for
something else until this problem is resolved. Also has stopped
development of our PowerApps.
On Fri, Dec 8, 2023 at 3:45 AM Rob Bowman ***@***.***> wrote:
disabling the *Mssql: Enable Sql Authentication Provider*
This worked for me
—
Reply to this email directly, view it on GitHub
<#24104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3JYLOFJVG2GSLEMEKL63Z3YIL4WJAVCNFSM6AAAAAA3JHNXCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGAZTSNZTG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Edmund Landgraf
***@***.***
***@***.***
415.425.8655 (m/w)
866.209.7487 (vm/fax)
—
Reply to this email directly, view it on GitHub<#24104 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGJTVDRHSQW27OYY4UUAGPDYIRZYDAVCNFSM6AAAAAA3JHNXCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYGQZDOMZSGY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
@edmund-landgraf Are you not able to provide a solution because of this specific issue with Azure Data Studio, or for a different reason? |
|
I'll revisit Azure when the bug is solved for everyone. Thank you for
continuing to work on recreation and resolution
|
|
Same problem here |
I encountered the same error at the first time connecting to my Azure SQL, but clear azure account token cache is helpful. Just press |
|
Closing as we haven't been able to reproduce the issue recently and mitigation options are available as discussed in the thread above. |
github-project-automation
bot
moved this from In Progress
to Done
in ADS Core Committer and Fundamentals
|
I've tried the recommendations to resolve the issue, but I'm encountering the same error. I recently today downloaded the latest .exe ran the commands no luck. User account not found in MSAL cache, please add linked account or refresh account credentials. |
|
I have been living with this issue for a long time and finally decided to look again for a fix. This led me to install the insiders build, which has made the problem worse. Version: 1.49.0-insider Connecting to Azure SQL Databases I constantly clear the token cache on the standard build, and get it to work, but with insiders, I seem caught in a loop… Either way, is there a fix for this? ADS is such an awesome tool but this is really a bummer, especially because we are using Azure and Microsoft Entra, which you would think would be highly compatible. |
@peteot Did you test also in the February stable release, build 1.48? If so, and the problem still occurs, then reply back and we will also need logs for the issue. @ericmdsh - and to confirm, you still see this in 1.48 also? @cheenamalhotra - if it's still occurring in 1.48, can you please advise on opening a new issue, or re-opening this one? Thanks! |
|
I would request you to gather Azure account logs and MSSQL Logs as well and upload them in a new issue for investigation if you're experiencing regressed behavior. |
|
I was using 1.48 prior to trying 1.49-insider. I just tried it again on 1.48, and I can get it work, but of course I have to clear the token cache every time, often multiple times, to connecttointo a database. The log is attached, with some subscription details or other IDs I was unsure about, redacted. (You’ll see the string "”.) |
|
@cheenamalhotra here is the mssql log: 24-03-25 16:45:06.8014430 pid:27739 tid:11 sqltools Critical: 0 : False MSAL 4.56.0.0 MSAL.NetCore .NET 7.0.11 Darwin 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:57 PDT 2023; root:xnu-10002.1.13 |
This one worked for me in Azure Data Studio. |
This comment has been minimized.
This comment has been minimized.
Worked for me(For mac cmd+shift+p) |
|
Just updated to 1.48.1 and suddenly I'm getting the same error. |
@Moonwilles Thank you for making aware of this issue. Can you capture Azure account logs (steps below) and MSSQL logs (https://github.com/microsoft/azuredatastudio/wiki/Debug-Trace-Logging#mssql) and upload them to a new issue so that we can investigate further? Thank you. // @kburtram for awareness. Azure account logs capture (ensure no private data is in them): In the settings menu, find the setting titled Azure: Logging Level and select the Verbose option |
|
This is a secure message. Click here https://securemail.dsh.ca.gov/formpostdir/securereader?id=VSDHiLlDkVctjZ683m68s8L-5rDRotms&brand=5039a2d3 by 2025-01-08 19:03 UTC to read your message. After that, open the attachment.
|
|
There appear to be a few related, but different problems being discussed in this issue. If there is a bug in the current build that is impacting anyone, could you please open a new issue with the description of the repro steps, environment details, and observed product behavior? Thanks! |
|
Upon restarting the program, the issue resolved itself. I apologise for not trying this basic troubleshooting step earlier. |
|
I still get this error every day in both Azure Data Studio standard and insiders build on Mac. Extremely frustrating. Every time I attempt to access an Azure SQL Database, I get the error. It usually takes 2-3 attempts to refresh credentials before gaining access. Version: 1.49.1 Insiders: |
and others
Seems common, solution does not seem common
The text was updated successfully, but these errors were encountered: