microsoft / vscode-azureAutomation

MIT License
17 stars 4 forks source link

New Error: There is no data provider registered that can provide view data. #59

Open FlightXCaptain opened 9 months ago

FlightXCaptain commented 9 months ago

I use this extension daily and normally it is great but as of today i am no longer able to use it.

Error message: There is no data provider registered that can provide view data. And it just loads and loads and loads for hours achieving nothing. The other azure extensions i have installed like azure resources work fine still.

image

Things i have tried:

My colleague's seems to still be working. but i noticed the last updated date on this extension is different for him.

Mine: image

His: image

Please advise on what else I can try as I'm out of ideas.

Shruti-MS commented 9 months ago

It is weird, we have not published /updated the version for extension. By mistake iIthink you have pasted the same screenshot for extension info. One thing you can try if your VSCode version is upgraded recently, try to downgrade it.

Question:- Does sign in to Azure comes up or from start it shows the same message?

FlightXCaptain commented 8 months ago

Appologies yes this is his image (1)

No popup to login to azure. other azure extensions load and work fine straight away.

I was version 1.2.4 Downgraded to 1.2.2 same issue.

Do not believe it is version related.

Snorrason commented 4 months ago

Have the same issue, have two computers using the same login, One Computer works the other don't. have tried to completely uninstall VSCode - remove the two folders .vscode and code - and then reinstall code and only install the Automation module. no luck image

Snorrason commented 4 months ago

It seems to be an Edge browser plugin issue, I spined up a Win11 computer in Azure, installed VSCode, Azure Automation plugin, logged on the Automation account, no issue whatsoever. on the computer where I can't login into AzureAutomation, I have several profiles, and i also noticed that the MFA steps were missing one step, - we have very tight security.

So, now I just start my Virtual PC in Azure, and RDP into it.