Yikes! Looks like someone pulled the plug on the internet. What is the cause?

%3CLINGO-SUB%20id%3D%22lingo-sub-74788%22%20slang%3D%22en-US%22%3EYikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-74788%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Day%20to%20You%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20getting%20the%20message%20%22Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%22%20when%20Microsoft%20Teams%20starts.(Desktop%20application)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20logout%20and%20then%20login%2C%20it%20allows%20me%20to%20connect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20consisistency%20of%20this%20product%20is%20not%20very%20desirable.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20what%20causes%20this%20issue%3F%26nbsp%3B%20We%20have%20seen%20it%20occur%20when%20someone%20has%20been%20logged%20in%20for%20some%20time%20and%20then%20they%20get%20the%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-74788%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94206%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94206%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EI%20had%20a%20script%20run%20on%20each%20system%20to%20install%20Teams%20when%20a%20new%20person%20would%20log%20in%20(since%20this%20is%20installed%20in%20the%20user%20space).%20%26nbsp%3BThat%20worked%20until%20a%20new%20version%20was%20put%20out%20there.%20%26nbsp%3BThen%20I%20began%20to%20get%20the%20%22Yikes%22%20message.%20%26nbsp%3BNow%20I'm%20going%20back%20to%20remove%20that%20script.%20%26nbsp%3BI'll%20have%20to%20find%20another%20way%20to%20get%20this%20installed%20for%20new%20users.%20%26nbsp%3BWe%20have%20a%20group%20that%20has%20higher%20turnover%2C%20so%20having%20a%20user%20specific%20install%20takes%20extra%20time%20and%20effort.%20%26nbsp%3BOh%20well.%20%26nbsp%3BInstalling%20the%20newest%20version%20each%20time%20seems%20to%20work%20for%20now.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94074%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94074%22%20slang%3D%22en-US%22%3E%3CP%3EHaving%20uninstalled%20the%20current%20version%20(following%20the%20steps%20noted%20in%20the%20other%20posts)%20-%20the%20new%20version%20now%20lets%20my%20users%20log%20in%20without%20that%20error%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20this%20isn't%20a%20short%20term%20fix%20-%20I%20know%20in%20the%20past%2C%20these%20issues%20tend%20to%20come%20back%20-%20but%20at%20present%2C%20it's%20now%20working%20with%20the%20new%20versions%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94056%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94056%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20if%20this%20will%20help%2C%20but%20I've%20just%20noticed%20that%20there%20are%20some%20newer%20versions%20of%20the%20Teams%20app%20that%20differ%20to%20the%20ones%20I%20have%20used%20with%20my%20current%20installations.%3CBR%20%2F%3E%3CBR%20%2F%3EI'll%20try%20the%20steps%20above%20to%20uninstall%20my%20current%20ones%20and%20see%20if%20these%20updated%20version%20solve%20the%20issue..%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%2Fdownloads%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%2Fdownloads%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81648%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81648%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20this%20is%20fun.%20%26nbsp%3BI%20have%20two%20systems%20now%20that%20an%20uninstall%2Fremove%20folders%20and%20reinstall%20does%20not%20fix.%20%26nbsp%3BOne%20system%20is%20a%20new%20Windows%2010%20box%20and%20a%20fresh%20install.%20%26nbsp%3BAny%20thoughts%20from%20anyone%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76486%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76486%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Bob%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGlad%20you%20got%20that%20to%20work.%20I've%20been%20busy%20and%20meant%20to%20put%20in%20that%20I%20have%20(I%20hope)%20resolved%20it%20as%20well%20by%20downloading%20and%20reinstalling%20the%20application%20to%20the%20user's%20PCs%20from%20their%20O365%20accounts.%20I%20had%20originally%20deployed%20these%20as%20a%20package%20with%20some%20software%20we%20use%20(PDQ%20Deploy)%20but%2C%20out%20of%20the%2025%20deployments%20so%20far%2C%20these%20two%20seemed%20to%20have%20major%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20hoping%20that%20since%20this%20a%20brand%20new%20product%20and%20the%20Teams%20team%20is%20very%20active%20with%20feedback%20and%20development%20that%20they'll%20be%20able%20to%20track%20down%20the%20root%20cause%20and%20fix%20it%20in%20the%20future.%20There's%20no%20reason%20in%20such%20a%20brand%20new%20offering%20that%20one%20should%20have%20to%20do%20various%20hacks%20to%20get%20it%20to%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76326%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76326%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20I%20had%20to%20go%20a%20few%20steps%20further%20to%20%22fix%22%20the%20users%20that%20were%20having%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20renamed%20the%20Appdata%5CLocal%20folder%20to%20OLD_Teams%3C%2FP%3E%3CP%3EAttempted%20to%20open%20Teams%20%26gt%3B%20Same%20problem%26nbsp%3B*Did%20not%20fix%20the%20issue*%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUninstalled%20Teams%3C%2FP%3E%3CP%3ERenamed%20%22Appdata%5CLocal%5CMicrosoft%5CTeams%22%20to%20OLD_Teams%3C%2FP%3E%3CP%3ERenamed%20%22%3CSPAN%3EAppdata%5CRoaming%5CMicrosoft%5CTeams%22%20to%20OLD_Teams%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EInstalled%20Teams%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EUser%20was%20able%20to%20login%20okay%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20%22Appdata%5CRoaming%5CMicrosoft%5CTeams%22%20folder%20does%20not%20seem%20to%20be%20affected%20or%20cleaned%20up%20in%20any%20way%20during%20an%20uninstall.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAn%20hour%20later....SAME%20ISSUE%2C%20SAME%20USER.%20%26nbsp%3BInternet%20is%20fine.%20%26nbsp%3BNoticed%20in%20the%20logs%20that%20there%20was%20mention%20of%20unable%20to%20login.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20time%2C%20simply%20renamed%20%22Appdata%5CRoaming%5CMicrosoft%5CTeams%22%20to%20OLD_Teams%20and%20opened%20the%20Teams%20App.%20%26nbsp%3BThe%20folder%20was%20recreated%20and%20the%20app%20opened%20just%20fine!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76160%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76160%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20users%20do%20not%20use%20MS%20browsers.%20%26nbsp%3BBeyond%20that%2C%20we%20are%20using%20the%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20a%20possible%20work-around%20on%20another%20post%20for%20the%20same%20issue.%20%26nbsp%3BI%20am%20testing%20the%20theory%20now.%3C%2FP%3E%3CP%3EPress%3A%20Windows%20Key%20%2B%20R%3C%2FP%3E%3CP%3EType%3A%20%25appdata%25%3C%2FP%3E%3CP%3EDouble-click%20Microsoft%3C%2FP%3E%3CP%3ERename%20%22Teams%22%20to%20something%20different%20like%20%22Old_Teams%22%3C%2FP%3E%3CP%3ERestart%20Teams%20as%20usual%20and%20login%20when%20prompted.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76159%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76159%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F59850%22%20target%3D%22_blank%22%3E%40Will%20Perkinson%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20seen%20this%20happen%20a%20cumber%20of%20times.%20As%20consultant%20working%20for%20a%20Microsoft%20partner%20I%20work%20within%20many%20different%20tenants%20throughout%20the%20day.%20I've%20found%20that%20when%20I%20use%20the%20microsoft%20browsers%20(IE%20and%20Edge)%20with%20different%20tenants%20than%20my%20Microsoft%20teams%20is%20connected%20to%20that%20I%20sometimes%20run%20into%20issues%20like%20this.%20Closing%20the%20Microsoft%20browsers%20and%20restarting%20teams%20sorts%20out%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-76151%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76151%22%20slang%3D%22en-US%22%3E%3CP%3EHaving%20same%20issue%20as%20well.%20%26nbsp%3BTried%20a%20logout%2Flogon%20without%20success.%20%26nbsp%3BUninstall%2Freinstall%20worked.%20%26nbsp%3BOne%20received%20the%20error%20again%20after%20a%20few%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-75215%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-75215%22%20slang%3D%22en-US%22%3E%3CP%3EOut%20of%20our%20current%2025%20test%20deployments%2C%20we've%20had%20this%20with%20two%20so%20far%20so%20it's%20still%20an%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-74843%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-74843%22%20slang%3D%22en-US%22%3E%3CP%3EApparently%2C%20this%20is%20an%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F17407135-microsoft-teams-desktop-has-stopped-working-on-my%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Eintermittent%3C%2FA%3E%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FMS-Teams-Connection%2Ftd-p%2F28648%22%20target%3D%22_self%22%3Ebug%3C%2FA%3E%2C%20that's%20been%20around%20a%20while.%20Not%20seen%20a%20fix%20listed%2C%20just%20a%20workaround%20that%20you%20are%20using%20already%20with%20the%20logout%2Flogon.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20be%20interesting%20to%20hear%20if%20anyone%20else%20is%20still%20experiencing%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-406681%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-406681%22%20slang%3D%22en-US%22%3EDownload%20the%20new%20version%20of%20Teams%20from%20Microsoft%20and%20install%20after%20removing%20the%20existing%20version.%20This%20resolved%20my%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2118837%22%20slang%3D%22en-US%22%3ERe%3A%20Yikes!%20Looks%20like%20someone%20pulled%20the%20plug%20on%20the%20internet.%20What%20is%20the%20cause%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2118837%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F59850%22%20target%3D%22_blank%22%3E%40Will%20Perkinson%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Good Day to You,

 

We are getting the message "Yikes! Looks like someone pulled the plug on the internet." when Microsoft Teams starts.(Desktop application)

 

If I logout and then login, it allows me to connect.

 

The consisistency of this product is not very desirable. 

 

Does anyone know what causes this issue?  We have seen it occur when someone has been logged in for some time and then they get the message.

 

Regards,

 

Will

13 Replies

Apparently, this is an intermittent bug, that's been around a while. Not seen a fix listed, just a workaround that you are using already with the logout/logon.  

 

It would be interesting to hear if anyone else is still experiencing this issue.

Out of our current 25 test deployments, we've had this with two so far so it's still an issue.

Having same issue as well.  Tried a logout/logon without success.  Uninstall/reinstall worked.  One received the error again after a few days.

@Will Perkinson,

 

I've seen this happen a cumber of times. As consultant working for a Microsoft partner I work within many different tenants throughout the day. I've found that when I use the microsoft browsers (IE and Edge) with different tenants than my Microsoft teams is connected to that I sometimes run into issues like this. Closing the Microsoft browsers and restarting teams sorts out the issue.

My users do not use MS browsers.  Beyond that, we are using the client.

 

I found a possible work-around on another post for the same issue.  I am testing the theory now.

Press: Windows Key + R

Type: %appdata%

Double-click Microsoft

Rename "Teams" to something different like "Old_Teams"

Restart Teams as usual and login when prompted.

Well, I had to go a few steps further to "fix" the users that were having the issue.

 

I renamed the Appdata\Local folder to OLD_Teams

Attempted to open Teams > Same problem *Did not fix the issue*

 

Uninstalled Teams

Renamed "Appdata\Local\Microsoft\Teams" to OLD_Teams

Renamed "Appdata\Roaming\Microsoft\Teams" to OLD_Teams

Installed Teams

User was able to login okay

 

The "Appdata\Roaming\Microsoft\Teams" folder does not seem to be affected or cleaned up in any way during an uninstall.

 

An hour later....SAME ISSUE, SAME USER.  Internet is fine.  Noticed in the logs that there was mention of unable to login.

 

This time, simply renamed "Appdata\Roaming\Microsoft\Teams" to OLD_Teams and opened the Teams App.  The folder was recreated and the app opened just fine!

Hey Bob,

 

Glad you got that to work. I've been busy and meant to put in that I have (I hope) resolved it as well by downloading and reinstalling the application to the user's PCs from their O365 accounts. I had originally deployed these as a package with some software we use (PDQ Deploy) but, out of the 25 deployments so far, these two seemed to have major issues.

 

I'm hoping that since this a brand new product and the Teams team is very active with feedback and development that they'll be able to track down the root cause and fix it in the future. There's no reason in such a brand new offering that one should have to do various hacks to get it to work.

Well, this is fun.  I have two systems now that an uninstall/remove folders and reinstall does not fix.  One system is a new Windows 10 box and a fresh install.  Any thoughts from anyone?

Not sure if this will help, but I've just noticed that there are some newer versions of the Teams app that differ to the ones I have used with my current installations.

I'll try the steps above to uninstall my current ones and see if these updated version solve the issue..

https://teams.microsoft.com/downloads

 

 

Having uninstalled the current version (following the steps noted in the other posts) - the new version now lets my users log in without that error

 

I hope this isn't a short term fix - I know in the past, these issues tend to come back - but at present, it's now working with the new versions

I had a script run on each system to install Teams when a new person would log in (since this is installed in the user space).  That worked until a new version was put out there.  Then I began to get the "Yikes" message.  Now I'm going back to remove that script.  I'll have to find another way to get this installed for new users.  We have a group that has higher turnover, so having a user specific install takes extra time and effort.  Oh well.  Installing the newest version each time seems to work for now.

Download the new version of Teams from Microsoft and install after removing the existing version. This resolved my issue.