SOLVED
Home

SharePoint modern conversation webpart issues-First time user can't see the webpart

%3CLINGO-SUB%20id%3D%22lingo-sub-565217%22%20slang%3D%22en-US%22%3ESharePoint%20modern%20conversation%20webpart%20issues-First%20time%20user%20can't%20see%20the%20webpart%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-565217%22%20slang%3D%22en-US%22%3Ein%20SharePoint%2C%20new%20Yammer%20webpart%3A%20Conversation%20is%20not%20working%20for%20the%20users%20that%20trying%20to%20activate%20their%20account%20fo%20the%20first%20time%20in%20SharePoint%2C%20it%20was%20working%20last%20week%20but%20now%20getting%3A%20%22Oops%20something%20went%20wrong.%20Can't%20load%20conversations.%20Refresh%20the%20page%20or%20try%20again%20later.%22%20on%20all%20browsers.%20Any%20idea%3F%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-565217%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-654015%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20modern%20conversation%20webpart%20issues-First%20time%20user%20can't%20see%20the%20webpart%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-654015%22%20slang%3D%22en-US%22%3EAfter%20having%20a%20ticket%20with%20Support%20it's%20fixed%20and%20working%20now.%20Looks%20like%20something%20in%20the%20backend%20needs%20to%20be%20changed.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-654123%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20modern%20conversation%20webpart%20issues-First%20time%20user%20can't%20see%20the%20webpart%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-654123%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20still%20issue%20-%20Yammer%20Conversation%20Web%20Part%20is%20not%20working%20with%20a%20message%20%22Oops%20something%20went%20wrong.%20Can't%20load%20conversations.%20Refresh%20the%20page%20or%20try%20again%20later%22.%26nbsp%3B%20When%20I%20try%20to%20enter%20a%20name%20of%20Yammer%20group%20in%20setting%20pane%2C%20a%20message%20like%20%22Search%20is%20not%20working%20now.%20Please%20try%20again%20later%22%20is%20showing.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-655610%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20modern%20conversation%20webpart%20issues-First%20time%20user%20can't%20see%20the%20webpart%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-655610%22%20slang%3D%22en-US%22%3EI%20would%20recommend%20submitting%20a%20ticket%20for%20the%20Support%20since%20they%20told%20me%20they%20did%20something%20in%20a%20backend%20to%20fix%20the%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-814162%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20modern%20conversation%20webpart%20issues-First%20time%20user%20can't%20see%20the%20webpart%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-814162%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70455%22%20target%3D%22_blank%22%3E%40Alireza%20Rahimifarid%3C%2FA%3E%26nbsp%3Bthanks%20for%20this%2C%20did%20you%20have%20the%20Microsoft%20Suppoer%20ticket%20number%20by%20any%20chance%3F%20I%20have%20spent%201%20hour%20on%20the%20phone%20with%20Microsoft%20about%20this%20issue%20and%20they've%20run%20fiddler%20tests%20and%20tried%20allowing%20several%20sites%20related%20to%20yammer%20URLs%2C%20and%20they%20are%20stumped.%20If%20you%20can%20provide%20the%20ticket%20number%2C%20perhaps%20they%20can%20take%20a%20look%20at%20your%20solution%20and%20apply%20it%20for%20us!%20Thanks!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-815405%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20modern%20conversation%20webpart%20issues-First%20time%20user%20can't%20see%20the%20webpart%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-815405%22%20slang%3D%22en-US%22%3EUnfortunately%2C%20I%20don't%2C%20but%20it%20takes%2010%20days%20to%20resolve%2C%20I%20would%20recommend%20try%20this%20on%20a%20different%20browser%2C%20different%20computer%20and%20send%20the%20fiddler%20to%20them.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-822157%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20modern%20conversation%20webpart%20issues-First%20time%20user%20can't%20see%20the%20webpart%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-822157%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70455%22%20target%3D%22_blank%22%3E%40Alireza%20Rahimifarid%3C%2FA%3E%26nbsp%3BThank%20you%20for%20the%20tips!%20They%20still%20seem%20stumped%20even%20with%20the%20fiddler%20reports%2C%20but%20I%20have%20come%20up%20with%20a%20pattern%20of%20the%20issue%20so%20far.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20pattern%20seems%20to%20be%20that%20it%20is%20affecting%20all%20staff%20reporting%20to%20one%20particular%20manager%2C%20and%20that%20manager%20happens%20to%20have%20a%20different%20username%20with%20a%20period%20in%20the%20middle%20of%20his%20username%2C%20eg%20firstname.lastname%40company.com%20whilst%20we%20everyone%20else%20has%20firstinitiallastname%40company.com.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%20we'll%20keep%20it%20going%20and%20will%20try%20your%20tips%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Alireza Rahimifarid
Contributor
in SharePoint, new Yammer webpart: Conversation is not working for the users that trying to activate their account fo the first time in SharePoint, it was working last week but now getting: "Oops something went wrong. Can't load conversations. Refresh the page or try again later." on all browsers. Any idea?
6 Replies
Solution
After having a ticket with Support it's fixed and working now. Looks like something in the backend needs to be changed.

We have still issue - Yammer Conversation Web Part is not working with a message "Oops something went wrong. Can't load conversations. Refresh the page or try again later".  When I try to enter a name of Yammer group in setting pane, a message like "Search is not working now. Please try again later" is showing.



 

I would recommend submitting a ticket for the Support since they told me they did something in a backend to fix the issue.

@Alireza Rahimifarid thanks for this, did you have the Microsoft Suppoer ticket number by any chance? I have spent 1 hour on the phone with Microsoft about this issue and they've run fiddler tests and tried allowing several sites related to yammer URLs, and they are stumped. If you can provide the ticket number, perhaps they can take a look at your solution and apply it for us! Thanks!!

Unfortunately, I don't, but it takes 10 days to resolve, I would recommend try this on a different browser, different computer and send the fiddler to them.

@Alireza Rahimifarid Thank you for the tips! They still seem stumped even with the fiddler reports, but I have come up with a pattern of the issue so far.

 

The pattern seems to be that it is affecting all staff reporting to one particular manager, and that manager happens to have a different username with a period in the middle of his username, eg firstname.lastname@company.com whilst we everyone else has firstinitiallastname@company.com.

 

Anyway we'll keep it going and will try your tips as well.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies