SOLVED
Home

SharePoint connector "sorry, something went wrong"

%3CLINGO-SUB%20id%3D%22lingo-sub-281354%22%20slang%3D%22en-US%22%3ESharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281354%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20noticed%20an%20issue%20with%201%20specific%20Microsoft%20Team%20about%202%2C5%20Months%20ago.%20The%20SharePoint%20connector%20for%20Teams%20wasn't%20working.%20It%20simply%20gave%20a%20404%20error%20or%20%22sorry%2C%20something%20went%20wrong%22.%20Have%20created%20a%20ticket%20right%20away%20and%20have%20spent%20a%20lot%20of%20time%20showing%20this%20to%20Microsoft%20Support%20during%20numerous%20remote%20sessions%2C%20have%20sent%20many%20Fiddler%20logs%20and%20have%20answered%20the%20same%20questions%20too%20many%20times%20(e%2Cg.%20have%20you%20tried%20using%20a%20different%20browser%3F).%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EJust%20a%20couple%20of%20days%20ago%2C%20the%20same%20issue%20started%20happening%20for%20all%20our%20Microsoft%20Teams%20environments.%20Is%20anyone%20else%20experiencing%20this%3F%20The%20SharePoint%20connector%20is%20now%20not%20working%20for%20us%20at%20all.%20Have%20been%20trying%20to%20get%20this%20ticket%20escalated%2C%20but%20it%20doesn't%20look%20like%20we're%20making%20any%20progress.%20Can%20someone%20from%20the%20PG%20please%20reach%20out%20to%20me%20via%20DM%20and%20look%20into%20this%20ticket%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-281354%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-391250%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-391250%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2144%22%20target%3D%22_blank%22%3E%40Pooya%20Obbohat%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWas%20testing%20that%20on%20a%20test%20tenant%2C%20and%20it%20worked%20only%20in%20Microsoft%20Edge.%20I%20was%20getting%20the%20same%20error%20in%20Chrome.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20for%20a%20prod%20tenant%20I'm%20getting%20a%20different%20error%20%22Something%20went%20wrong.%20Connectors%20have%20been%20disabled%20for%20client%20-%20SkypeSpaces.%20Please%20contact%20your%20administrator.%20%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20idea%3F%20SharePoint%20News%20app%20is%20enabled%20at%20the%20tenant%20level%20under%20Microsoft%20Teams%20settings%20in%20the%20admin%20center.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-307637%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307637%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20new%20issue%20on%20connectors%20should%20not%20be%20associated%20with%20the%20previous%20one.%20My%20advice%20is%20to%20open%20a%20support%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-307496%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307496%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20created%20a%20SharePoint%20via%20Microsoft%20Teams.%20I'm%20trying%20to%20add%20a%20facebook%20page%20to%20my%20sharepoint%20homepage%2C%20but%20continually%20get%20'%3A-(%20something%20went%20wrong'%20message%20like%20many%20others%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20there%20been%20a%20fix%20yet%3F%20Am%20I%20doing%20something%20wrong%20or%20do%20we%20just%20wait%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297787%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297787%22%20slang%3D%22en-US%22%3E%3CP%3EHappy%20to%20say%20that%20Microsoft%20fixed%20the%20issue%20with%20the%20SharePoint%20connector%20for%20us%20yesterday.%20To%20anyone%20else%20that%20faces%20the%20same%20issue%2C%20make%20sure%20to%20create%20a%20ticket%20and%20also%20add%20a%20reference%20to%20this%20thread.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-295248%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-295248%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20Indeed.%20That's%20the%20first%20thing%20I%20tried%20before%20creating%20a%20ticket%20with%20support.%20It's%20impacting%20all%20Microsoft%20Teams%20environments%20in%20all%20browsers%2C%20all%20machines%2C%20networks%20etc.%20When%20I%20created%20the%20ticket%20it%20only%20impacted%20one%20Microsoft%20Team.%20Have%20received%20another%20email%20from%20support%20mentioning%20something%20new%20and%20that%20they%20are%20still%20investigating%20it.%20Will%20share%20an%20update%20here%20when%20I%20have%20new%20information.%20Think%20it's%20safe%20to%20conclude%20that%20this%20isn't%20something%20my%20customer%20can%20fix%20as%20it's%20all%20happening%20on%20the%20backend.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-294196%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-294196%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20you%20have%20tried%26nbsp%3Bon%26nbsp%3B%20Teams%26nbsp%3BWeb%20%26amp%3B%20Desktop%3CSPAN%3E%26nbsp%3Bclients%2C%26nbsp%3B%20I%20have%20this%20issues%20only%20on%20desktop%20client.%20then%20the%20issues%20was%20diapered%20%2C%20reached%20out%20to%20an%20admin%20and%20they%20were%20talking%20about%26nbsp%3B%20it%26nbsp%3Bsetup%20rules%20for%20port%20forward%2C%20I%20am%20not%20sure%20what%20port%20but%20while%20searching%20for%20it%20I%20have%20got%20the%20below%20info%20..%20worth%20checking%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20Audio%3A%20UDP%2050000-50019%3C%2FP%3E%3CP%3ETeams%20Video%3A%20UDP%2050020-50039%3C%2FP%3E%3CP%3ETeams%20Sharing%3A%20UDP%2050040-50059%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-294138%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-294138%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20had%20another%20call%20with%20MSFT%20support%20and%20they%20asked%20for%20a%20screen%20sharing%20session%20and%20a%20new%20Fiddler%20log%20w.r.t.%20the%20SP%20connector%20issue.%20We%20talked%20a%20bit%20and%20then%20it%20was%20concluded%20that%20the%20correlation%20ID%20should%20be%20enough.%20Looking%20forward%20to%20the%20next%20screen%2Ffiddler%20log%20sharing%20session.%20Does%20anyone%20know%20the%20options%20when%20it%20has%20become%20clear%20that%20Microsoft%20can't%20fix%20a%20specific%20bug%3F%20It%20there%20any%20documentation%20on%20this%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292064%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292064%22%20slang%3D%22en-US%22%3E%3CP%3EGlad%20to%20confirm%20that%20the%20SharePoint%20News%20connector%20is%20working%20for%20us%20again%20now%20too.%20Thanks%20for%20the%20pretty%20speedy%20fix%20and%20publication%20Microsoft%20guys...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291134%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291134%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20confirm%20that%20it%20is%20now%20working%20in%20our%20environment%20as%20well.%26nbsp%3B%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291039%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291039%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20tip.%20Created%20this%20thread%20to%20see%20if%20anyone%20else%20is%20experiencing%20issues%20with%20the%20SharePoint%20connector%20and%20as%20you%20can%20see%20at%20the%20top%2C%20a%20ticket%20was%20created%20for%20that%20more%20than%203%20Months%20ago.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290671%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290671%22%20slang%3D%22en-US%22%3E%3CP%3Eif%20you%20are%20facing%20any%20other%20issues%20open%20a%20support%20incident.%20All%20my%20feedback%20below%20was%20related%20to%20the%20SP%20News%20one%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290644%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290644%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20confirm%20that%20the%20SP%20news%20connector%20is%20working%20in%20our%20environment.%20We're%20now%20just%20waiting%20for%20the%20SharePoint%20connector%20to%20be%20fixed...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290590%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290590%22%20slang%3D%22en-US%22%3E%3CP%3EFix%20is%20in%20prod.%20Please%20test.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290588%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290588%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20a%20call%20with%20MS%20yesterday%20and%20their%20Engineering%20team%20is%20still%20working%20on%20this-%20They%20were%20not%20able%20to%20provide%20any%20ETA.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-290576%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290576%22%20slang%3D%22en-US%22%3E%3CP%3Ea%20fix%20has%20been%20deployed%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-289759%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289759%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63424%22%20target%3D%22_blank%22%3E%40Bruno%20Aleixo%3C%2FA%3E%26nbsp%3BMany%20thanks%20for%20this%20precious%20information.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eis%20it%20something%20we%20could%20follow%20with%20our%20customers%20through%20the%20Message%20Center%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-289678%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289678%22%20slang%3D%22en-US%22%3E%3CP%3Ea%20fix%20is%20being%20made%20for%20this%20issue%20and%20should%20reach%20production%20soon%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-289239%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289239%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20been%20experiencing%20the%20same%20problem%20across%20all%20Teams%20on%20all%20platforms%20for%20a%20few%20weeks.%20I%20have%20created%20a%20support%20ticket%20with%20Office%20365%20support%20and%20I%20await%20their%20reply.%20We%20get%20the%20same%20%22something%20went%20wrong%22%20message%20with%20some%20text%20about%20lacking%20permissions%20when%20we%20try%20to%20modify%20the%20connector%2C%20add%20a%20new%20connector%20or%20remove%20an%20existing%20one.%20Very%20frustrating%2C%20I%20wish%20Microsoft%20could%20give%20us%20a%20concrete%20reply%20about%20it.%20Someone%20will%20know%20why%20it%20is%20no%20longer%20working%20and%20when%20the%20fix%20will%20be%20released.%20My%20guess%20is%20that%20it%20is%20related%20to%20SharePoint%20permissions.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-289168%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289168%22%20slang%3D%22en-US%22%3E%3CP%3EI%20confirm%20that%20it%20seems%20we%20are%20several%20in%20this%20situation%2C%20i%20face%20similar%20situation%20with%20a%20customer's%20tenant.%3C%2FP%3E%3CP%3EFor%20now%20MS%20support%20is%20still%20investigating%20logs%20captured%20with%20fiddler%20%26amp%3B%20correlation%20ID.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20updates%20for%20others%20with%20same%20situation%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-288865%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-288865%22%20slang%3D%22en-US%22%3EI%20tested%20the%20same%20feature%20with%20my%20tenant%2C%20and%20I%20could%20add%20the%20connector%20successfully.%20So%20the%20feature%20is%20available%20and%20working%20as%20expected.%20If%20a%20feature%20is%20not%20working%2C%20either%20it%20is%20not%20yet%20released%20for%20you%2C%20or%20it%20needs%20troubleshooting%20to%20see%20why%20it%20is%20not%20working.%20Kindly%20contact%20Microsoft%20support%20for%20more%20information%20on%20the%20issue%20that%20you%20are%20facing.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-288851%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-288851%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%2C%20it%20has%20nothing%20to%20do%20with%20standard%20and%20target%20release.%20The%20issues%20applies%20to%20both%20standard%20and%20target%20release%20users%20-%20not%20on%20a%20single%20tenant%20but%20multiple%20tenant.%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20been%20over%204%20months%20but%20issue%20is%26nbsp%3Bsill%20there%20-%20even%20after%20logging%20it%20via%20multiple%20client's%20tenant.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-288806%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-288806%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20sharing.%20Find%20it%20strange%20that%20users%20(not%20in%20targeted%20release)%20are%20seeing%20that%20connector%20and%20AFAIK%2C%20the%20SharePoint%20connector%20isn't%20in%20preview.%20They%20have%20to%20at%20least%20fix%20the%20issue%26nbsp%3Bmy%20customer%20is%26nbsp%3Bexperiencing%20with%20the%20normal%20SharePoint%20connector%20and%20they%20haven't%20made%20any%20progress%20in%20more%20than%203%26nbsp%3BMonths.%20TBH%2C%20I'm%20not%20so%20sure%20that%20they%20can%20actually%20fix%20it%20as%20I%20have%20seen%20multiple%20bugs%20not%20being%20addressed.%20Based%20on%20my%20experience%2C%20I%20would%20not%20recommend%20any%20organization%20to%20make%20use%20of%20Microsoft%20Teams.%20There%20are%20too%20many%20bugs%20and%20Microsoft%20support%20is%20clearly%20not%20ready%20to%20support%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283392%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283392%22%20slang%3D%22en-US%22%3EThanks%20Pooya.%20Just%20had%20a%20conversation%20with%20MS%20tech%20support.%20Here's%20the%20best%20resolution%20we%20could%20reach%20for%20now%20(in%20short%2C%20the%20connector%20is%20still%20in%20targeted%20release%20and%20should%20be%20ready%20for%20standard%20adoption%20by%20the%20end%20of%20the%20year).%3CBR%20%2F%3E%3CBR%20%2F%3EAssessment%20%2F%20Recommendations%3A%3CBR%20%2F%3ESome%20functionality%20is%20introduced%20gradually%20to%20organizations%20that%20have%20opted%20in%20to%20the%20Targeted%20Release%20program.%20This%20means%20that%20you%20may%20not%20yet%20see%20this%20feature%20or%20it%20may%20look%20different%20than%20what%20is%20described%20in%20the%20help%20articles.%3CBR%20%2F%3EMore%20Information%3A%3CBR%20%2F%3EWhile%20on%20call%20I%20mentioned%20that%20the%20feature%20might%20not%20working%20fine%20as%20of%20now.%20Some%20of%20the%20features%20are%20introduced%20slowly%20into%20all%20of%20the%20accounts.%20You%20can%20refer%20also%20to%20this%20Microsoft%20support%20article%20at%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fadd-team-site-news-in-a-teams-channel-743607c0-9510-414b-8aab-1ae9ef5d3f49%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fadd-team-site-news-in-a-teams-channel-743607c0-9510-414b-8aab-1ae9ef5d3f49%3C%2FA%3E%3CBR%20%2F%3EWhile%20on%20call%20we%20also%20checked%20if%20you%20are%20on%20a%20standard%20release%20program%20or%20a%20targeted%20release.%20Any%20new%20release%20is%20first%20tested%20and%20validated%20by%20the%20feature%20team%2C%20then%20by%20the%20entire%20Office%20365%20feature%20team%2C%20followed%20by%20entire%20Microsoft.%20After%20internal%20testing%20and%20validation%2C%20the%20next%20step%20is%20a%20Targeted%20release%20(formerly%20known%20as%20First%20release)%20to%20customers%20who%20opt%20in.%20At%20each%20release%20ring%2C%20Microsoft%20collects%20feedback%20and%20further%20validates%20quality%20by%20monitoring%20key%20usage%20metrics.%20This%20series%20of%20progressive%20validation%20is%20in%20place%20to%20make%20sure%20the%20worldwide-release%20is%20as%20robust%20as%20possible.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283383%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283383%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20confirm%20that%20the%20SharePoint%20News%20connector%20is%20also%20not%20working%20for%20us.%20Will%20send%20them%20an%20email%20to%20let%20them%20know%20and%20will%20ialso%20nclude%20a%20link%20to%20this%20thread.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283351%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283351%22%20slang%3D%22en-US%22%3EPooya%20-%20we're%20having%20a%20similar%20issue%20here.%20Just%20tried%20installing%20the%20SharePoint%20News%20connector%20within%20Teams%20(desktop%20client).%20From%20the%20app%20store%2C%20I%20can%20find%20SharePoint%20News.%20When%20prompted%20for%20the%20team%20to%20add%20to%2C%20I%20select%20my%20team%20(which%20has%20an%20associated%20SharePoint%20site%20with%20existing%20news%20posts)%20and%20click%20Install.%20Then%20I%20am%20prompted%20to%20select%20which%20channel%20to%20use%20and%20click%20Set%20up.%20I%20then%20am%20prompted%20to%20click%20Save%2C%20and%20when%20I%20do%2C%20I%20get%2C%20%22%3A-(%20Something%20went%20wrong.%20An%20unexpected%20error%20occurred.%20Please%20try%20again%2C%22%20with%20requestID%2C%20server%2C%20%26amp%3B%20date%20info.%20I'll%20see%20if%20I%20can%20find%20a%20solution%20elsewhere%20and%20if%20I%20do%2C%20loop%20back%20here.%20Too%20bad%20as%20this%20would%20be%20a%20very%20useful%20connector%20for%20our%20org!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281900%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281900%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20sharing.%20Your%20experience%20with%20support%20is%20similar%20to%20mine%20and%20I'm%20not%20surprised%20tbh.%20Will%20post%20an%20update%20here%20when%20I%20have%20new%20information.%20Still%20hoping%20that%20someone%20from%20the%20PG%20reaches%20out%20to%20me%20to%20look%20into%20this%20as%20the%20normal%20escalation%20paths%20aren't%20working.%20Have%20wasted%20a%20lot%20of%20time%20since%20I%20opened%20this%20ticket%20on%26nbsp%3B%3CSPAN%3E8%2F20%2F2018%2C%205%3A02%3A17%20PM.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281857%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281857%22%20slang%3D%22en-US%22%3E%3CP%3EPooya%2C%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20experienced%20the%20similar%20issue%20-%20but%20it's%20limited%20to%20using%20Teams%20Web%20client%20on%20IE.%20It%20works%20fine%20while%20using%20Teams%20desktop%20client%20and%20web%20client%20on%20Edge%20and%20Chrome%20browser.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20support%20ticket%20open%20for%20last%20three%20months.%20It's%20been%20escalated%20to%20product%20team%20but%20no%20updates%20on%20resolution%20and%20no%20ETA.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3CP%3EH.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281724%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281724%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20someone%20from%20Microsoft%20actually%20monitoring%20this%20forum%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-423134%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20connector%20%22sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-423134%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F123001%22%20target%3D%22_blank%22%3E%40Aim%20Zaab%3C%2FA%3E%26nbsp%3Bhaven't%20seen%20that%20before.%20AFAIK%2C%20you%20have%20the%20option%20to%20enable%2Fdisable%20connectors%20and%20that's%20it.%20When%20you%20have%20the%20option%20to%20select%20a%20connector%20and%20are%20getting%20an%20error%2C%20then%20I%20think%20all%20you%20can%20do%20is%20reach%20out%20to%20Microsoft%20support.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Pooya Obbohat
Regular Contributor

Hi all,

 

We noticed an issue with 1 specific Microsoft Team about 2,5 Months ago. The SharePoint connector for Teams wasn't working. It simply gave a 404 error or "sorry, something went wrong". Have created a ticket right away and have spent a lot of time showing this to Microsoft Support during numerous remote sessions, have sent many Fiddler logs and have answered the same questions too many times (e,g. have you tried using a different browser?). 


Just a couple of days ago, the same issue started happening for all our Microsoft Teams environments. Is anyone else experiencing this? The SharePoint connector is now not working for us at all. Have been trying to get this ticket escalated, but it doesn't look like we're making any progress. Can someone from the PG please reach out to me via DM and look into this ticket? 

 

 

29 Replies

Is someone from Microsoft actually monitoring this forum? 

Pooya, 

We have experienced the similar issue - but it's limited to using Teams Web client on IE. It works fine while using Teams desktop client and web client on Edge and Chrome browser. 

We have a support ticket open for last three months. It's been escalated to product team but no updates on resolution and no ETA.

 

Cheers,

H.

Thanks for sharing. Your experience with support is similar to mine and I'm not surprised tbh. Will post an update here when I have new information. Still hoping that someone from the PG reaches out to me to look into this as the normal escalation paths aren't working. Have wasted a lot of time since I opened this ticket on 8/20/2018, 5:02:17 PM. 

Pooya - we're having a similar issue here. Just tried installing the SharePoint News connector within Teams (desktop client). From the app store, I can find SharePoint News. When prompted for the team to add to, I select my team (which has an associated SharePoint site with existing news posts) and click Install. Then I am prompted to select which channel to use and click Set up. I then am prompted to click Save, and when I do, I get, ":-( Something went wrong. An unexpected error occurred. Please try again," with requestID, server, & date info. I'll see if I can find a solution elsewhere and if I do, loop back here. Too bad as this would be a very useful connector for our org!

Can confirm that the SharePoint News connector is also not working for us. Will send them an email to let them know and will ialso nclude a link to this thread. 

Thanks Pooya. Just had a conversation with MS tech support. Here's the best resolution we could reach for now (in short, the connector is still in targeted release and should be ready for standard adoption by the end of the year).

Assessment / Recommendations:
Some functionality is introduced gradually to organizations that have opted in to the Targeted Release program. This means that you may not yet see this feature or it may look different than what is described in the help articles.
More Information:
While on call I mentioned that the feature might not working fine as of now. Some of the features are introduced slowly into all of the accounts. You can refer also to this Microsoft support article at:
https://support.office.com/en-us/article/add-team-site-news-in-a-teams-channel-743607c0-9510-414b-8a...
While on call we also checked if you are on a standard release program or a targeted release. Any new release is first tested and validated by the feature team, then by the entire Office 365 feature team, followed by entire Microsoft. After internal testing and validation, the next step is a Targeted release (formerly known as First release) to customers who opt in. At each release ring, Microsoft collects feedback and further validates quality by monitoring key usage metrics. This series of progressive validation is in place to make sure the worldwide-release is as robust as possible.

Thanks for sharing. Find it strange that users (not in targeted release) are seeing that connector and AFAIK, the SharePoint connector isn't in preview. They have to at least fix the issue my customer is experiencing with the normal SharePoint connector and they haven't made any progress in more than 3 Months. TBH, I'm not so sure that they can actually fix it as I have seen multiple bugs not being addressed. Based on my experience, I would not recommend any organization to make use of Microsoft Teams. There are too many bugs and Microsoft support is clearly not ready to support it. 

I think, it has nothing to do with standard and target release. The issues applies to both standard and target release users - not on a single tenant but multiple tenant. 

It's been over 4 months but issue is sill there - even after logging it via multiple client's tenant. 

I tested the same feature with my tenant, and I could add the connector successfully. So the feature is available and working as expected. If a feature is not working, either it is not yet released for you, or it needs troubleshooting to see why it is not working. Kindly contact Microsoft support for more information on the issue that you are facing.

I confirm that it seems we are several in this situation, i face similar situation with a customer's tenant.

For now MS support is still investigating logs captured with fiddler & correlation ID.

 

Any updates for others with same situation ?

We have been experiencing the same problem across all Teams on all platforms for a few weeks. I have created a support ticket with Office 365 support and I await their reply. We get the same "something went wrong" message with some text about lacking permissions when we try to modify the connector, add a new connector or remove an existing one. Very frustrating, I wish Microsoft could give us a concrete reply about it. Someone will know why it is no longer working and when the fix will be released. My guess is that it is related to SharePoint permissions. 

a fix is being made for this issue and should reach production soon

@Bruno Aleixo Many thanks for this precious information.

 

is it something we could follow with our customers through the Message Center ? 

 

a fix has been deployed

I had a call with MS yesterday and their Engineering team is still working on this- They were not able to provide any ETA. 

 

Fix is in prod. Please test. Thanks!

Can confirm that the SP news connector is working in our environment. We're now just waiting for the SharePoint connector to be fixed... 

if you are facing any other issues open a support incident. All my feedback below was related to the SP News one

Thanks for the tip. Created this thread to see if anyone else is experiencing issues with the SharePoint connector and as you can see at the top, a ticket was created for that more than 3 Months ago. 

Can confirm that it is now working in our environment as well.  Thanks!

Glad to confirm that the SharePoint News connector is working for us again now too. Thanks for the pretty speedy fix and publication Microsoft guys...

Just had another call with MSFT support and they asked for a screen sharing session and a new Fiddler log w.r.t. the SP connector issue. We talked a bit and then it was concluded that the correlation ID should be enough. Looking forward to the next screen/fiddler log sharing session. Does anyone know the options when it has become clear that Microsoft can't fix a specific bug? It there any documentation on this? 

Hello,

 

Hope you have tried on  Teams Web & Desktop clients,  I have this issues only on desktop client. then the issues was diapered , reached out to an admin and they were talking about  it setup rules for port forward, I am not sure what port but while searching for it I have got the below info .. worth checking 

 

Teams Audio: UDP 50000-50019

Teams Video: UDP 50020-50039

Teams Sharing: UDP 50040-50059

Hi. Indeed. That's the first thing I tried before creating a ticket with support. It's impacting all Microsoft Teams environments in all browsers, all machines, networks etc. When I created the ticket it only impacted one Microsoft Team. Have received another email from support mentioning something new and that they are still investigating it. Will share an update here when I have new information. Think it's safe to conclude that this isn't something my customer can fix as it's all happening on the backend. 

Solution

Happy to say that Microsoft fixed the issue with the SharePoint connector for us yesterday. To anyone else that faces the same issue, make sure to create a ticket and also add a reference to this thread. 

I've created a SharePoint via Microsoft Teams. I'm trying to add a facebook page to my sharepoint homepage, but continually get ':-( something went wrong' message like many others here.

 

Has there been a fix yet? Am I doing something wrong or do we just wait?

Any new issue on connectors should not be associated with the previous one. My advice is to open a support case.

@Pooya Obbohat 

 

Was testing that on a test tenant, and it worked only in Microsoft Edge. I was getting the same error in Chrome.

 

But for a prod tenant I'm getting a different error "Something went wrong. Connectors have been disabled for client - SkypeSpaces. Please contact your administrator. ".

 

Any idea? SharePoint News app is enabled at the tenant level under Microsoft Teams settings in the admin center.

 

@Aim Zaab haven't seen that before. AFAIK, you have the option to enable/disable connectors and that's it. When you have the option to select a connector and are getting an error, then I think all you can do is reach out to Microsoft support. 

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