Buggish: MS Teams Unable to Login. We've run into an issue. Oops, something went wrong! (Part 3) With Workaround

As of 2024-12-09, I am still getting this error but after messing around a bit, I think I may have found a workaround.

Workaround

It seems like you cannot login when you get the error. This time I decided to click on the chat. Nothing loads but now the usual profile icon shows and a banner to login also shows. If the banner doesn't show, the profile options should have the option to sign in.

After signing in, some things may load. For me, it loaded three or four of maybe eighty or hundred of chats I should have. The profile icon doesn't show nor does the status.

As with the prior login issue, reloading the application after signing in with the issues will then finally load properly.

At least, I can use the app in the morning now. I am not sure why waiting several hours will also reach the same state.

Possible Alternate Workaround

May be able to skip a step above by trying to sign in before closing the app if the option is available. Also closing the app before calling it a day seems to also bypass the issue.

Now that I am writing this alternate workaround, I think there is a possibility that the issue may be with the login token not expiring properly. To make a guess, it may be that it is reusing the token that expires in 24 hours. The reason I have to wait for it open again is that I am waiting for the 24 hours to expire. Closing the app probably removes that token properly. Signing in also kind of removes the token but the app still may be continuing to load so therefor only loading parts of the configurations. And for some reason, closing the app after getting the error does not remove the token properly.

Buggish: MS Teams Unable to Login. We've run into an issue. Oops, something went wrong! (Part 2)

Seems like this issue only occurs in the morning.

Maybe waiting for something to load. If so, then it must be something that takes a long time to load as I am unable to log in for at least a couple hours.

Or maybe something to do with the system going into hibernation.

Update 2024-12-09

Buggish: MS Teams Unable to Login. We've run into an issue. Oops, something went wrong! (Part 3) With Workaround

https://douglastclee.blogspot.com/2024/12/buggish-ms-teams-unable-to-login-weve.html

Buggish: MS Teams Unable to Login. We've run into an issue. Oops, something went wrong! (Part 1)

 I've been getting this error. Reboot and app restart does not fix the issue.

We've run into an issue

Oops, something went wrong 

Sometimes later in the day, it'll work. Sometimes, it does not. I just use the web version.

Why can't Microsoft figure out how to log into their own application on their own operating system?

https://douglastclee.blogspot.com/2024/08/buggish-ms-teams-unable-to-login-device_30.html

https://douglastclee.blogspot.com/2024/08/buggish-ms-teams-unable-to-login-device.html

https://douglastclee.blogspot.com/2024/07/buggish-ms-teams-login-again.html

https://douglastclee.blogspot.com/2024/07/buggish-ms-teams-login-issue.html

Update 2024-12-09

Buggish: MS Teams Unable to Login. We've run into an issue. Oops, something went wrong! (Part 3) With Workaround

https://douglastclee.blogspot.com/2024/12/buggish-ms-teams-unable-to-login-weve.html

Buggish: MS Excel (Web Version) Copy/Paste Issue with message "Retrieving data. Wait a few seconds and try to cut or copy again."

Some days, several brain cells just hate Microsoft. Is it MS' fault? Probably just another underpaid and overworked engineer. But still... why something as simple as copy/paste breaks?

I copy cells then I paste and I get:

"Retrieving data. Wait a few seconds and try to cut or copy again."

Copy something else (not in spreadsheet), paste, correct. Copy same cells again, paste, error message. Paste, paste, paste, paste, paste, paste, paste, paste, paste.... all error messages. Wait... paste... error message.

Sheet has 4700+ records, 9 columns of data.

Reduced record count to 4000+ records.

Now suddenly works.

Unrelated

Copy a cell, select into a cell (ie so that cursor appears in the cell), paste. In the Excel app, this will copy the value into the cell (instead of the equation or type).

This will work on the first cell. Select a second cell and suddenly doesn't work. This happens every time.

Somehow selecting into 1 cell won't delete the clipboard but the second one does. Or probably what is happening is when selecting out being inside of a cell deletes the clipboard. Whatever the case, why is moving cells impacting the clipboard at all?

Buggish: MS Teams Unable to Login. Device must comply with your organization's compliance requirements. (Resolved? Two weeks and no issues)

Suddenly, I identified a pattern that was suspiciously correlated to my login issues with Microsoft Teams. I noticed that I was able to connect successfully when I connect to VPN to another network unrelated to the login that I use on Teams. I do not know why but I am able to replicate it by disabling my VPN.

Although I found the cause to my issue, I do not know why it is the cause to my issue. My login is to domain A. My system is on domain B. My VPN is to access B's Azure cloud solutions.

Maybe the compliance part requires access to Azure cloud? Shouldn't that be on the backend though? Any case, it has been two weeks and no issues as long as I wait for the VPN to connect first.

It still sucks that I have to restart Teams whenever my laptop is in sleep mode too long but at least it is not as irritating as the above issue. This is likely the end of this series of MS Teams bugs.

References

Part 3 - https://douglastclee.blogspot.com/2024/08/buggish-ms-teams-unable-to-login-device.html

Part 2 - https://douglastclee.blogspot.com/2024/07/buggish-ms-teams-login-again.html

Part 1 - https://douglastclee.blogspot.com/2024/07/buggish-ms-teams-login-issue.html

Buggish: Visual Studio 2022 Stuck in Rebase

I got stuck in Visual Studio 2022 under Git Changes where I only get the options to Skip or Abort.

Short Answer

Got to your .git folder and delete rebase-merge folder then restart Visual Studio. Restart is required as the screen does not update.

RCA

The complicated part is that I was troubleshooting a separate issue where we get ghost files appearing for apparently no reason but related to white-spaces. I have a potential solution but it only impacts the main branch. Everyone's current branches will continue to have this ghost file issue.

One of the biggest problem with the ghost file issue is that you cannot remove it from the staged or unstaged list. When executing the rebase, it will stash the change. The ghost changes will be stashed but will also not go away so the rebase will fail. VS buttons to continue or abort will also fail. In CLI, it is functioning as normal so this is primarily a VS-ish bug. The bug is probably also on git side where the folder is not removed when either the rebase fails or when aborted.

Buggish: MS Teams Unable to Login. Device must comply with your organization's compliance requirements. (3rd post on same bug)

I just rebooted after a Windows update that required a reboot and behold... my "Device must comply with your organization's compliance requirements" infinite loop is back. You can see my past issues...

https://douglastclee.blogspot.com/2024/07/buggish-ms-teams-login-again.html

https://douglastclee.blogspot.com/2024/07/buggish-ms-teams-login-issue.html

Besides that I have little add from my other posts.

Rebooting again doesn't help.

Restarting app multiple times doesn't help.

Our IT help support is useless.

So-called online MS certified support or actual MS support just points you to the IT help which I already mentioned are useless.

Signing in again and again doesn't help.

It clearly logs in because each time I attempt I get updates to my chats.

The browser version works.

My personal phone which is definitely not org compliant works.

Only Microsoft knows how to break their own apps while all other non-MS apps on a Microsoft OS seem to work completely fine. Their copy/paste do not work across different apps and messes with the global clipboard. Visual Studio is slow as molasses. It takes up 90% of my hard drive (237 GB). Making me have to deal with our useless IT support and cheap-ass infrastructure team that is so penny-pinching to not get a hard drive big enough for someone to work. I constantly have to delete and uninstall then reinstall when I need it again which all requires admin rights which I have to deal with our IT support (at least this one is our department IT which actually is not useless). Ok, this last one may not be Microsoft fault, but I still blame them for all their bloated apps and complicated licensing. I just want to focus on working not trying to train myself to be IT.

Buggish: MS Teams (Login again)

Still randomly having the same issue from last post, https://douglastclee.blogspot.com/2024/07/buggish-ms-teams-login-issue.html.

Today I also found that I can open the app. It'll (as always) take forever to "login", error that login doesn't work, then the error will disappear, my chats will refresh (fully? I have no clue). I sent a single message to respond to a chat. As I check other chats, I notice that I have the login error again. When did it happy? I do not know. Why does it happen? Also don't know. But my message was sent... so.......

Why is this so complicating? At least two years (maybe even four but my memory isn't serving me right now). Or is this a white-paper on barely functional is better than holding new features?

Update

I also just noticed that my status is now offline but I have been message people since I created this post. This is also seen on the other end as a couple people have asked how I am offline but responding.

Buggish: Microsoft Web Outlook Cannot Send Message Error

 To no one's surprise, Microsoft has probably one of the worst user experiences.

Trying to send an email. Takes forever and returns an error that says something like "There was an error, please click here for more details." And the more detail returns:  "This message can't be sent right now. Please try again later."

Great, Microsoft, great.

I eventually figured it out. The issue was that I was tagging a private group. It was a group set up in my outlook with a bunch of people that I send to normally. This is separate from Active Directory because I don't have access and I hate dealing with admin support.

Buggish: MS Teams (Login issue)

I just used MS Teams yesterday with no issues for work. I come back today and now I get an error "We weren't able to connect. Sign in and we'll try again." on MS Edge. On most days, refreshing if web or reloading if Windows app will resolve this issue... but today it is not letting me in. Usually one or two attempts will bypass this.

It is not the same error with the Windows app version where I get that my corporate device is not compliant with corporate compliance. Go figure... it was working yesterday and nothing has been installed. And like the web, usually reloading will resolve this in 1-3 attempts... but today a no go.

And now I get a "We've run into an issue. Oops, something went wrong! Restart" error. Seems to be flipping between this error and the one above today.

On top of all that, MS Teams works almost perfectly on Google Chrome. It is again quite amusing to see that I also get the "... weren't able to connect..." error on Chrome but I can just continue to message and receive messages.

After 30 minutes of just refreshing the page, Teams on Edge started working. Also I did in that time was messaging people on Google Chrome, repeatedly refreshing Edge and repeatedly restarting the Windows app.