404 error when opening TeamSite

%3CLINGO-SUB%20id%3D%22lingo-sub-276355%22%20slang%3D%22en-US%22%3E404%20error%20when%20opening%20TeamSite%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276355%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20of%20our%20clients%20raised%20an%20issue%20with%20us%20last%20week%20that%20when%20they%20open%20their%20browser%20(%20IE%2011)%20which%20is%20set%20to%20open%20their%20Office%20365%20TeamSite%20as%20their%20homepage%2C%20they%20experience%20%22Page%20not%20Found%22%20error.%26nbsp%3B%20If%20they%20hit%20F5%20or%20close%20the%20browser%20and%20open%20again%2C%20the%20TeamSite%20appears%20and%20functions%20perfectly%20for%20the%20rest%20of%20the%20day%2C%20but%20the%20issue%20occurs%20again%20at%20the%20start%20of%20each%20day%20when%20they%20first%20open%20the%20browser.%26nbsp%3B%20This%20has%20been%20an%20issue%20now%20for%20about%20a%20week.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20own%20TeamSite%20is%20of%20similar%20design%20to%20this%20client%20in%20that%20is%20of%20the%20classic%20(not%20modern)%20SharePoint%20TeamSite.%26nbsp%3B%20Over%20the%20last%20couple%20days%2C%20we%20too%20are%20experiencing%20this%20isue%2C%20with%20a%20variety%20of%20browsers%20(IE%2C%20Chrome%20(default%20browser)%2C%20Firefox%20and%20Edge.%26nbsp%3B%20Again%2C%20if%20we%20hit%20F5%20or%20refresh%20the%20browser%2C%20the%20TeamSite%20appears%20and%20functions%20as%20normal.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20tried%20clearing%20browsing%20cache%20and%20also%20flushing%20DNS%2C%20but%20this%20doesn't%20seem%20to%20resolve%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20issue%20isn't%20apparent%20for%20us%20or%20our%20client%20on%20any%20other%20URL%20than%20the%20Office%20365%20TeamSite.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20advice%20would%20be%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-276355%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287889%22%20slang%3D%22en-US%22%3ERe%3A%20404%20error%20when%20opening%20TeamSite%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287889%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20without%20making%20any%20changes%2C%20the%20issue%20hasn't%20been%20evident%20now%20for%20over%20a%20week.%26nbsp%3B%20All%20team%20members%20are%20accessing%20the%20TeamSite%20first%20time%2C%20every%20time%2C%20regardless%20of%20which%20site%20they%20are%20at.%26nbsp%3B%20So%20not%20sure%20where%20that%20issue%20was%2C%20but%20seems%20to%20be%20back%20to%20normal%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280988%22%20slang%3D%22en-US%22%3ERe%3A%20404%20error%20when%20opening%20TeamSite%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280988%22%20slang%3D%22en-US%22%3EI%20am%20seeing%20the%20exact%20same%20thing.%20But%20not%20only%20with%20chrome%2C%20but%20also%20with%20Edge%20and%20I%20am%20seeing%20this%20on%20multiple%20tenants%20with%20multiple%20Clients.%20Looks%20like%20it%20is%20an%20issue%20with%20SPO%20and%20not%20the%20clients.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280426%22%20slang%3D%22en-US%22%3ERe%3A%20404%20error%20when%20opening%20TeamSite%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280426%22%20slang%3D%22en-US%22%3E%3CP%3ESeems%20that%20the%20issue%20is%20isolated%20to%20Google's%20Chrome%20browser.%26nbsp%3B%20We%20can%20replicate%20the%20issue%20on%20several%20devices%20including%20laptops%20at%20different%20locations%20on%20differing%20ISP's%20using%20differing%20DNS%20servers.%26nbsp%3B%20We%20can't%20replicate%20it%20however%20on%20any%20other%20browser%20than%20Chrome.%26nbsp%3B%20Likewise%2C%20Chrome%20doesn't%20have%20this%20issue%20with%20any%20other%20site%20than%20our%20Office%20365%20Teamsite.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe'll%20see%20what%20the%20next%20update%20to%20that%20browser%20brings.%26nbsp%3B%20As%20it%20stands%2C%20Chrome%20only%20needs%20one%20refresh%20and%20the%20Teamsite%20loads.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276413%22%20slang%3D%22en-US%22%3ERe%3A%20404%20error%20when%20opening%20TeamSite%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276413%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20can%20reliably%20reproduce%20it%2C%20open%20a%20support%20case.%20Especially%20if%20it%20acts%20the%20same%20across%20different%20browsers.%20Just%20to%20be%20on%20the%20safe%20side%2C%20I'd%20recommend%20testing%20from%20outside%20of%20the%20company%20network%2C%20if%20possible.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

One of our clients raised an issue with us last week that when they open their browser ( IE 11) which is set to open their Office 365 TeamSite as their homepage, they experience "Page not Found" error.  If they hit F5 or close the browser and open again, the TeamSite appears and functions perfectly for the rest of the day, but the issue occurs again at the start of each day when they first open the browser.  This has been an issue now for about a week.

 

Our own TeamSite is of similar design to this client in that is of the classic (not modern) SharePoint TeamSite.  Over the last couple days, we too are experiencing this isue, with a variety of browsers (IE, Chrome (default browser), Firefox and Edge.  Again, if we hit F5 or refresh the browser, the TeamSite appears and functions as normal.

 

We tried clearing browsing cache and also flushing DNS, but this doesn't seem to resolve the issue.

 

This issue isn't apparent for us or our client on any other URL than the Office 365 TeamSite.

 

Any advice would be appreciated.

4 Replies
Highlighted

If you can reliably reproduce it, open a support case. Especially if it acts the same across different browsers. Just to be on the safe side, I'd recommend testing from outside of the company network, if possible.

Highlighted

Seems that the issue is isolated to Google's Chrome browser.  We can replicate the issue on several devices including laptops at different locations on differing ISP's using differing DNS servers.  We can't replicate it however on any other browser than Chrome.  Likewise, Chrome doesn't have this issue with any other site than our Office 365 Teamsite.

 

We'll see what the next update to that browser brings.  As it stands, Chrome only needs one refresh and the Teamsite loads.

Highlighted
I am seeing the exact same thing. But not only with chrome, but also with Edge and I am seeing this on multiple tenants with multiple Clients. Looks like it is an issue with SPO and not the clients.
Highlighted

Well, without making any changes, the issue hasn't been evident now for over a week.  All team members are accessing the TeamSite first time, every time, regardless of which site they are at.  So not sure where that issue was, but seems to be back to normal now.