Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrospectives Link failed to load #380

Open
cynthia1463 opened this issue Jul 7, 2022 · 29 comments
Open

Retrospectives Link failed to load #380

cynthia1463 opened this issue Jul 7, 2022 · 29 comments
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists usage: on-prem A category for issues arising on on-premises instances of the tool.
Milestone

Comments

@cynthia1463
Copy link

We are running TFS 2019 and since the new version 1.8.x installation that began Sun 4 July 2022, the link fails to load the retrospective page. The most recent patch was 1.8.0.4 installed yesterday and the same thing continues to happen. Bad timing since our retrospective is today!

@ka-kalee
Copy link

ka-kalee commented Jul 8, 2022

Same issue as well. I am running ADO 2019 local installation and 1.8.0.4 is still broken

@marcuslopes
Copy link

marcuslopes commented Jul 8, 2022

same issue in our environment and I confirm it started recently, probably due to the patches from the 4th

@denitajc
Copy link

denitajc commented Jul 8, 2022

Same issue in our environment. It started with the most recent update. We are running TFS 2018

@FChapeau
Copy link

FChapeau commented Jul 8, 2022

Same problem here. ADO 2019.0.1 and the link just loads indefinitely. When I check the chrome debugger, there's a bunch of errors, including CORS, fetch and Signalr errors.

@lwong072022
Copy link

Same issue in our ADO 2019 on-premises. Last time it worked was 6/29/22

@BennyBrowns
Copy link

Hi all, this is also discussed in issue #371 and #376

@dstoddar dstoddar added the bug Something isn't working label Jul 11, 2022
@dstoddar dstoddar added this to the In Review milestone Jul 11, 2022
@dstoddar dstoddar pinned this issue Jul 11, 2022
@dstoddar
Copy link
Contributor

dstoddar commented Jul 11, 2022

We will elevate this. Stay tuned. @polatengin

@dstoddar dstoddar added the duplicate This issue or pull request already exists label Jul 11, 2022
@pollpbl
Copy link

pollpbl commented Jul 12, 2022

Hello, I have the same issue:
image

Do you need more information about the issue? Maybe we can somehow support you?

@rpalbrecht
Copy link

We are seeing the same issues as everyone else since 1.8.1 release and we are running ADO 2019 latest. I hope a fix is coming soon I have a lot of teams wanting to do Retrospectives.

@polatengin
Copy link
Collaborator

hey @cynthia1463 , @ka-kalee , @rpalbrecht , @pollpbl @BennyBrowns , @FChapeau , @denitajc , @lwong072022 , @marcuslopes , can we have a troubleshooting session, so I can take a look at the network activity and repro the issue on my end. 30 mins will be more than enough, I think. please reach me from polatengin [at] hotmail.com , so I can arrange a meeting 👍

@BennyBrowns
Copy link

@polatengin we just did an upgrade to server 2020 (update 1.1) and the Retrospective plugin works fine now. That's good news! So maybe a specific issue with the 2019 server version?

Thanks for the support and hope you can help others with a fix for 2019 server.

@ka-kalee
Copy link

It's good news that the extension works on server 2020 (update 1.1). @BennyBrowns can I ask you for the procedures on upgrading. I read the document from Microsoft, but it's kinda unclear. Thanks in advance

@dstoddar
Copy link
Contributor

@polatengin we just did an upgrade to server 2020 (update 1.1) and the Retrospective plugin works fine now. That's good news! So maybe a specific issue with the 2019 server version?

Thanks for the support and hope you can help others with a fix for 2019 server.

@ka-kalee , @cynthia1463 , @rpalbrecht , @pollpbl , @BennyBrowns , @FChapeau , @denitajc , @lwong072022 , @marcuslopes. Looks like @BennyBrowns was able to resolve the issue by upgrading from 2019 to 2020 (update 1.1). @BennyBrowns , can you provide the documentation to help people update whilst we are evaluating the source issue?

@BennyBrowns
Copy link

Upgrade depends on your specific landscape.

  1. read into the official documentation: https://docs.microsoft.com/en-us/azure/devops/server/upgrade/get-started?view=azure-devops-2020
  2. Optional (we skipped this step): Do a dry run of your upgrade in a pre-production environment: https://docs.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-2020
  3. Backup your server environment for easy roll-back (we use Veeam for the Virtual Machines)
  4. Install depends on your specific deployment type (single, dual, multiple): https://docs.microsoft.com/en-us/previous-versions/azure/devops/server/install/get-started?view=tfs-2015
  5. Download the intallation for your specific deployment type
  6. Run the installation steps (this really can take a while depending on the size of your environment)
  7. Optional: upgrade your other servers (e.g. database)
  8. Test the upgrade (build, basic stuff on azure devops, power automate flows, power bi reports if you have some)

Hope this helps.

@rpalbrecht
Copy link

rpalbrecht commented Jul 15, 2022

For us doing an upgrade is not an option at this time. Company policy requires review process and testing to ensure nothing gets broken with current projects and systems first. Is they no fix for ADO 2019 users?

@lwong072022
Copy link

For us doing an upgrade is not an option at this time. Company policy requires review process and testing to ensure nothing gets broken with current projects and systems first. Is they no fix for ADO 2019 users?

We are in the same boat and would like to have a fix for AD 2019 soon. We did a retrospective a couple of weeks back and I didn't get a chance to export out the results before it stopped working.

@pollpbl
Copy link

pollpbl commented Jul 19, 2022

For us doing an upgrade is not an option at this time. Company policy requires review process and testing to ensure nothing gets broken with current projects and systems first. Is they no fix for ADO 2019 users?

We are in the same boat and would like to have a fix for AD 2019 soon. We did a retrospective a couple of weeks back and I didn't get a chance to export out the results before it stopped working.

You can try to install the older version from the topic https://github.com/microsoft/vsts-extension-retrospectives/issues/371 and save your tasks. The version works for me (TFS2018 U3) but only till the server is restarted, after it, the Retrospective extension is magically updated ...

@dstoddar
Copy link
Contributor

Please accept our sincerest apologies for the inconvenience this issue has caused, and thank you for raising visibility and helping us identify the root cause. We have successfully reproduced the issue on our end and @polatengin us focused on isolating the root cause and coming up with a fix. We are hopeful that this fix will be in place in the next few days but can't be certain of the timeframe until we fully identify the root cause. Thank you again for raising the issue and helping us debug it to this point.

@dstoddar
Copy link
Contributor

We believe we have isolated and resolved this issue. If you continue to have any issues related to this bug please contact @polatengin directly. Thank you for your patience.

@dstoddar dstoddar modified the milestones: In Review, Released Jul 20, 2022
@lwong072022
Copy link

Hi @polatengin
We did get the latest update 1.80.6 yesterday evening but the problem still persists where the Retrospective Board is just continuously Loading. We are still on ADO 2019.

@ssullivan23
Copy link

Good morning @polatengin and @dstoddar. I see 1.80.10 in our 2019 on-premise instance and it has resolved our issue with the Retrospective Boards loading. Thank you for your persistence in resolving the issue and thanks for the extension. It is a popular one with our teams.

@pollpbl
Copy link

pollpbl commented Jul 21, 2022

Hello @polatengin and @dstoddar.
We are using TFS2018 U3 and the fix that was done with version 1.80.10 still doesn't work for us. Is it any possibility that the fix will be adjusted also for TFS2018?

@rpalbrecht
Copy link

Our 2019 on-premise is still at 1.80.4 and the market place is showing only that version for us. When will the fix be available to everyone?

@polatengin
Copy link
Collaborator

Hi @lwong072022 , latest release is v1.80.10 .

can I kindly ask you to update the extension to the latest version and test the extension, please?

with the fixes that the latest version brings, the extension should work 👍

@polatengin
Copy link
Collaborator

Hello @polatengin and @dstoddar. We are using TFS2018 U3 and the fix that was done with version 1.80.10 still doesn't work for us. Is it any possibility that the fix will be adjusted also for TFS2018?

Hi @pollpbl , let me take a look. first I need to get TFS2018U3 environment to repro the problem, so I can work on a fix.

In the meantime, is there any chance for you to upgrade your environment to AzDO 2019 , or 2022 better?

@polatengin
Copy link
Collaborator

Our 2019 on-premise is still at 1.80.4 and the market place is showing only that version for us. When will the fix be available to everyone?

Hi @rpalbrecht , I just checked the marketplace page for the extension (https://marketplace.visualstudio.com/items?itemName=ms-devlabs.team-retrospectives) and I can see the latest version (v1.80.10) is released to everyone.

can I kindly ask you to double check if you can see the latest version, too, or not, please?

if not, can you uninstall and re-install the extension? it should install the latest version.

@OttoKriedeman
Copy link

My issue was closed but we are still having the same issue with TFS 2018 U3 and are on the latest version 1.80.10. We are in the process of upgrading but our business has not had retrospectives working for almost 2 weeks now.

@nashda
Copy link

nashda commented Jul 27, 2022

We are seeing the same error using TFS Update 2 (16.131.28507.4) and Retrospectives version 1.80.11. The following error is seen in the console, if relevant. Tried uninstalling and reinstalling multiple times. No joy.

DevTools failed to load source map: Could not load content for https://[redacted]/tfs/_apis/public/gallery/publisher/ms-devlabs/extension/team-retrospectives/1.80.11/assetbyname/dist/reflect-bundle.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

DevTools failed to load source map: Could not load content for https://[redacted]/tfs/_apis/public/gallery/publisher/ms-devlabs/extension/team-retrospectives/1.80.11/assetbyname/node_modules/applicationinsights-js/dist/ai.0.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

@dstoddar
Copy link
Contributor

dstoddar commented Aug 9, 2022

@polatengin , please advise.

@mindlessroman mindlessroman added the usage: on-prem A category for issues arising on on-premises instances of the tool. label Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists usage: on-prem A category for issues arising on on-premises instances of the tool.
Projects
None yet
Development

No branches or pull requests