SharePoint Conversations webpart not working

%3CLINGO-SUB%20id%3D%22lingo-sub-1538221%22%20slang%3D%22en-US%22%3ESharePoint%20Conversations%20webpart%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1538221%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20organisation%20has%20raised%20a%20ticket%20with%20Microsoft%20Support%20-%2020584998%20-%20but%20are%20not%20getting%20any%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20%3CSTRONG%3EConversations%20web%20part%3C%2FSTRONG%3E%20is%20not%20functioning%2C%20the%20ability%20to%20configure%20the%20web%20part%20does%20not%20resolve%20-%20nor%20does%20the%20web%20part%20render%20in%20the%20page.%26nbsp%3B%20See%20images.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20initial%20response%20we%20got%20was%20that%20vanity%20domain%20names%20can%20not%20work%20for%20new%20web%20parts%20including%20both%20%3CSTRONG%3Econversations%3C%2FSTRONG%3E%20or%20%3CSTRONG%3Ehighlights%3C%2FSTRONG%3E%20-%20until%20we%20demonstrated%20that%20%3CSTRONG%3Ehighlights%20does%20in%20fact%20work%3C%2FSTRONG%3E.%26nbsp%3B%20Now%20the%20answer%20is%20%22I%20have%20no%20answer%20to%20this%20as%20any%20issue%20pertaining%20to%20conversation%20and%20highlight%20webparts%2C%20when%20associated%20with%20vanity%20domain%20is%20not%20supported%20for%20troubleshooting%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20not%20very%20helpful%20and%20is%20creating%20a%20major%20barrier%20for%20adoption%20of%20this%20product%20within%20the%20organisation.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anybody%20please%20offer%20some%20advice%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20others%20experienced%20this%20problem%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1538221%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1539577%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Conversations%20webpart%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1539577%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F679287%22%20target%3D%22_blank%22%3E%40Anthony_Ciavarella%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20are%20you%20using%26nbsp%3B%20to%20apply%20the%20vanity%20domain%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20have%20to%20agree%20with%20support%2C%20vanity%20domains%20are%20not%20supported%20so%20you%20are%20trying%20to%20do%20something%20outside%20of%20the%20service%20agreement.%20That%20may%20not%20be%20the%20issue%20but%20the%20fact%20that%20you%20have%20a%20vanity%20domain%20stops%20Microsoft%20supporting%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheck%20fiddler%20logs%20for%20any%20errors%20as%20that%20may%20indicate%20a%20bit%20more%20what%20the%20issue%20is%2C%20usually%20support%20ask%20you%20to%20do%20this%20when%20logging%20a%20ticket%20so%20you%20may%20already%20have%20done%20that.%20Check%20developer%20tools%20in%20the%20browser%20as%20that%20may%20also%20give%20you%20some%20leads%20on%20the%20errors%20occurring.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20added%20both%20those%20webparts%20to%20a%20page%20and%20they%20are%20working%20ok%20in%20my%20tenant%20at%20the%20moment.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1541591%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Conversations%20webpart%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1541591%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F214649%22%20target%3D%22_blank%22%3E%40Andrew%20Hodges%3C%2FA%3E%26nbsp%3B-%20good%20suggestion%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20mention%20that%20it%20works%20for%20you%20-%20were%20you%20saying%20this%20in%20the%20context%20of%20vanity%20domains%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1542307%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Conversations%20webpart%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1542307%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F679287%22%20target%3D%22_blank%22%3E%40Anthony_Ciavarella%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%2C%20in%20the%20context%20of%20not%20using%20a%20vanity%20domain.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1548217%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Conversations%20webpart%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1548217%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F214649%22%20target%3D%22_blank%22%3E%40Andrew%20Hodges%3C%2FA%3E%26nbsp%3BOK%2C%2C..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20a%20vanity%20domain%20name%20hardly%20seems%20a%20reason%20for%20the%20vendor%20to%20not%20support%20through%20troubleshooting%20-%20especially%20given%20this%20issue%20will%20not%20be%20mutually%20exclusive%20to%20us%20as%20a%20single%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20Highlights%20does%20work%20-%20so%20would%20be%20surprised%20if%20it%20is%20vanity%20related.%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-1729055%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Conversations%20webpart%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1729055%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20still%20unresolved%20with%20no%20clear%20definitive%20statement%20on%20why%20Highlights%20works%20and%20Conversations%20does%20not%20-%20nor%20with%20a%20timeline%20on%20those%20customers%20who%20use%20vanity%20domains.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1729135%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Conversations%20webpart%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1729135%22%20slang%3D%22en-US%22%3EThis%20is%20the%20Yammer%20issue%20you%20can%20find%20this%20issue%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fyammer%2Fpicture-in-conversations-yammer-webpart-showing-blurry%2Fm-p%2F864106%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fyammer%2Fpicture-in-conversations-yammer-webpart-showing-blurry%2Fm-p%2F864106%3C%2FA%3E%20Even%20submit%20a%20technical%20support%20case%20can't%20resolve%20the%20case%2C%20unfortunately%20Microsoft%20doesn't%20have%20a%20good%20support%20in%20Yammer%3C%2FLINGO-BODY%3E
Occasional Contributor

My organisation has raised a ticket with Microsoft Support - 20584998 - but are not getting any support.

 

The Conversations web part is not functioning, the ability to configure the web part does not resolve - nor does the web part render in the page.  See images.

 

The initial response we got was that vanity domain names can not work for new web parts including both conversations or highlights - until we demonstrated that highlights does in fact work.  Now the answer is "I have no answer to this as any issue pertaining to conversation and highlight webparts, when associated with vanity domain is not supported for troubleshooting"

 

This is not very helpful and is creating a major barrier for adoption of this product within the organisation.  

 

Can anybody please offer some advice?

 

Have others experienced this problem?

6 Replies

@Anthony_Ciavarella 

 

What are you using  to apply the vanity domain? 

 

I would have to agree with support, vanity domains are not supported so you are trying to do something outside of the service agreement. That may not be the issue but the fact that you have a vanity domain stops Microsoft supporting this issue.

 

Check fiddler logs for any errors as that may indicate a bit more what the issue is, usually support ask you to do this when logging a ticket so you may already have done that. Check developer tools in the browser as that may also give you some leads on the errors occurring. 

 

I have added both those webparts to a page and they are working ok in my tenant at the moment. 

Thanks @Andrew Hodges - good suggestion

 

You mention that it works for you - were you saying this in the context of vanity domains?

@Anthony_Ciavarella 

 

No, in the context of not using a vanity domain. 

@Andrew Hodges OK,,..

 

Using a vanity domain name hardly seems a reason for the vendor to not support through troubleshooting - especially given this issue will not be mutually exclusive to us as a single client.

 

Also Highlights does work - so would be surprised if it is vanity related.

 

 

This is still unresolved with no clear definitive statement on why Highlights works and Conversations does not - nor with a timeline on those customers who use vanity domains.

This is the Yammer issue you can find this issue here: https://techcommunity.microsoft.com/t5/yammer/picture-in-conversations-yammer-webpart-showing-blurry... Even submit a technical support case can't resolve the case, unfortunately Microsoft doesn't have a good support in Yammer