Latest version 1.54.0.1 not working in 2 different visual studio instances

[marcoschneidertui]

Describe the bug When opening multiple instances of Visual Studio, only the first opened instance is able to use Amazon-Q. On the second instance, no feature is available.

To Reproduce Steps to reproduce the behavior

1. Open Visual Studio and load a solution
2. Amazon-Q is available, the icon shows up
3. Open second Visual Studio instance and load a solution
4. No Amazon-Q icon and no context menu is available and

Expected behavior Amazon-Q is available in all opened instances

Screenshots First openen instance has fully operational Amazon-Q

Second opened instance does not show Amazon-Q Icon and has missing context menu

Toolkit Logs Toolkit Log first instance: log_2024-07-04_08-08-42_6284.txt

Toolkit Log second instance: log_2024-07-04_08-31-58_13012.txt

Development System (please complete the following information):

• Windows Version: 10
• Visual Studio Version: latest
• AWS Toolkit for Visual Studio Version: latest

[marcoschneidertui]

Hi, this morning I had a slightly different behaviour. I opened one instance and Amazon-Q worked fine. I closed the instance and started a new one together with a solution. This seems to let Amazon-Q quit in total. I still have AWS Toolkit on the extensions dropdown, but it shows no longer to be installed.... 🤔

Here some logs: log_2024-07-05_07-30-51_16372.txt

[shruti0085]

Hi @marcoschneidertui, can you try the re-install instructions here: https://github.com/aws/aws-toolkit-visual-studio/issues/441#issuecomment-2207475901 and attempt to do a clean un-install and re-install of the toolkit? And if that doesn't make the extension show as installed in the Extensions Manager, can you try running a "Repair" from the Visual Studio Installer (available from the start menu)?

[marcoschneidertui]

Hi @shruti0085 , I followed your advice and reinstalled everything. I also repaired my visual studio installation, but everything without success. I am still not able to open two instances of visual studio and can use amazon-q in both of them. Only the first one will have Amazon-Q working. Left part of the image shows the first started visual studio, right hand side the second instance.

[shruti0085]

Hi @marcoschneidertui, Thanks for trying those steps. We are trying to rule out a few different odd behaviors, would you mind answering the following questions:

• After trying the above steps, does your Visual Studio extension manager now list the AWS Toolkit extension as being installed?
• Do you have any other versions of Visual Studio 2022 installed? for eg. Community/Professional/Preview
• If answer to the above question is yes, what version of them are installed?

[marcoschneidertui]

Hi @shruti0085 , I only have one version of visual studio installed.

This is what I get when I start an instance: `AWS Toolkit for Visual Studio Toolkit Version: 1.54.0.1 Visual Studio: VS Professional 2022, Version: 17.10.3

Some Toolkit components could not be initialized. Some functionality may not work during this IDE session.`

Interesting is, that on the Extensions Menu, I still see AWS Toolkit, but on installed extensions it does not show up:

Once deinstalled and reinstalled I get back to the same behaviour, that one instance is working with amazon-q. And this doesnt change unless I start a second instance in parallel.

[shruti0085]

Thanks for answering the questions. Apologies for sounding a little repetitive but can you try this or confirm if you have already attempted the following?

With the latest v1.54.0.1 of AWS Toolkit installed close all instances of VS2022. Navigate to Visual Studio Installer, run a Repair and let the process complete, restart/reboot your system and then launch Visual Studio again. Does the extension manager still not list AWS toolkit extension as being installed? Your answers have been very helpful as they provide us useful data to understand the issue better and to troubleshoot this further.

Extension Manager that lists AWS Toolkit

Repair

[marcoschneidertui]

Hi @shruti0085 , I already ran the repair. That changed nothing unfortunately. I ran repair ones when the toolkit was installed, but also one time where the toolkit was not installed. Both with an equal result, as soon as I start a second VS instance, everything becomes corrupted.

Maybe it is related to Kirks comment on this issue-chat. I always start my solutions by either selecting the sln file or by opening the solution from the last project list

Right now, ones I started two instances in parallel, I can run through the complete deinstall/install steps again.

[marcoschneidertui]

Hi @shruti0085 , I think it is working now. Microsoft released VS Version 17.10.4. After I upgraded I can run multiple instances with Amazon-Q and it seems nothing gets broken any longer.

[awschristou]

Hi @marcoschneidertui , thank you for sharing an update that the issue may be resolved with version 17.10.4 of Visual Studio. Can you please share another update after the next day or two of usage to confirm that things continue to remain stable?

[marcoschneidertui]

Hi @awschristou , sorry to tell, but this was just short term solution. Today I am back to the issues. I started visual studio (without loading a solution) and Amazon-Q worked fine. I closed that instance and started a new instance by selecting from the list of previously opened solution and Amazon-Q was no longer available, but Toolkit was still shown in the Extensions Menu.

I attach the logs of the "crashed" instance. log_2024-07-11_08-30-55_18144.txt

(Just a side-note: I am off after today for 3 weeks, so will not be able to support further until I am back at work....)

[awschristou]

Hi @marcoschneidertui , when you have an instance of Visual Studio that doesn't load Amazon Q, does #452 match the description of what you are seeing? If that is continuing to happen, we'd really appreciate if you can follow the steps listed in the "help us out" section. This will help us (and the Visual Studio team) get some more clues about this problem.

[marcoschneidertui]

Hi @awschristou , I had the issue again this morning. I deinstalled and reinstalled AWS Toolkit. Since this reinstall, the issue doesnt happen any more. I wanted to follow the help us out section and tried to force it, but until now without success. I will keep focus on that and give feedback if the issue is now gone.

[marcoschneidertui]

Hi @awschristou , unfortunately the issue is not solved. Today I receive this error again `Reloaded AWS Credential Profiles Profiles found: 7 The following credentials could not be loaded: AccountAdminDevelop. Check the Toolkit logs for more details. AWS Toolkit for Visual Studio Toolkit Version: 1.56.0.0 Visual Studio: VS Professional 2022, Version: 17.10.5

Some Toolkit components could not be initialized. Some functionality may not work during this IDE session. If this issue persists, please see guidance on https://github.com/aws/aws-toolkit-visual-studio/issues/452`

I did the requested traces and updated the Microsoft case.

[marcoschneidertui]

Hi @awschristou , unfortunately there is no real progress on the Microsoft tickets. Nevertheless I have a new finding. The issue I have described does not only happen on 2 Visual Studio instances. I had 1 Visual Studio instance open and Amazon Q was working. I opened a Visual Studio CODE instance having toolkit installed but not being signed in. Screenshot from the remark from visual studio code:

I closed both instances. After I opened Visual Studio again, AWS Toolkit was no longer working and showed me this again:

[shruti0085]

Hi @marcoschneidertui, Thank you for sharing your logs on the MSFT ticket. We do not believe VSCode toolkit plays a part into triggering the issue, it seems like it is an intermittent issue which we are trying to get to the bottom of. We really appreciate your help with this investigation so far. There's been a new comment specifying additional instructions to get a few more logs on the MSFT ticket and we'd appreciate it if you can take a look at that.

[marcoschneidertui]

Hi @shruti0085 , I followed the new advise from the MSFT ticket and it seems to work now. I will continue monitoring that.

[marcoschneidertui]

Hi all, I can inform, that I have no more issues now after applying the changes recommended in the MSFT ticket. So I will close this now