Open SEMoslaw opened 8 months ago
I have experienced this issue on several machines on several accounts and its sadly blocking me from using this awesome extension.
The issue manifests across multiple machines, suggesting a systemic problem rather than an isolated configuration error. It also aligns with previously reported issues:
In both instances, the proposed solutions were:
There I eventually identified that the pac executable was not getting installed on my system. (I have no idea why!) Luckily, I had a backup from a previous system that I was able to grab the old extension install and copy it to my new system.
If the bug cant be fixed, would it be possible to provide the missing code, i tried comparing the repo code and the installed code, but couldnt find differences or the pac file mentioned.
Despite applying these solutions—verifying the absence of obscured windows and confirming the installation of the required .NET versions—the problem persists.
Here are the outputs from the system showing the installed .NET versions and the successful creation of authentication profiles:
PS H:\Backup\Besper - RAG> dotnet --list-sdks
6.0.421 [C:\Program Files\dotnet\sdk]
7.0.403 [C:\Program Files\dotnet\sdk]
PS H:\Backup\Besper - RAG> pac auth create --environment c83f2d2a-574f-eda2-afd5-fac4ef2d564b
'WolfgangSperger@nornet-ai.com' authenticated successfully.
Validating connection...
Connected to... Dev
Default organization: Dev
Authentication profile created
* UNIVERSAL: WolfgangSperger@[Redacted] Public https://[Redacted].crm16.dynamics.com/
PS H:\Backup\Besper - RAG> pac auth list
Index Active Kind Name User Cloud Type Environment Environment Url
[1] UNIVERSAL WolfgangSperger@[Redacted] Public User BesperAi (default) https://[Redacted].crm16.dynamics.com/
[2] * DATAVERSE [Redacted] WolfgangSperger@[Redacted] Public User Development https://[Redacted].crm.dynamics.com/
[3] * UNIVERSAL WolfgangSperger@[Redacted] Public User Dev https://[Redacted].crm16.dynamics.com/
The systems used were all windows 11.
In the image you can see the loading screen which despite the auth profiles does not show anything:
Update: After restarting visual studio again after creating the auth profiles via the command line, the profiles all showed up.
So the solution is to run the commands listed above and then restart.
But still, might be cool to fix this :)
I'm trying this in my VS Code on my PC and Laptop both having the same issue. Not sure what might be the problem. I've reinstalled .net and this extension like some people suggested and also made sure that window is not hidden anywhere but had no luck.