Forum Discussion
Unable to add connectors on any channel
Hello Team,
We are unable to add/manage connectors on any channel. I am the owner of the Team and also I am unable to. Any help please?
RequestId: unknown Server: XYZ Date: 2021-11-22 11:19:51 +0100
It was working earlier, the only change we did is.. renamed the Team name. Since then its not working.
1. I tried to clear cache
2. Checked the permissions from Team Settings -> Manage connectors was enabled
I dont know any other options, please help
Thanks and have a nice day!
Bhargav
- The issue is fixed for us today, but its different story.
We renamed the MS Teams name and since then we noticed this issue. But we are not sure if that is the cause of this connectors issue which we got initially.
But what we did was changing the mail address of the group to the new changed MS Teams name, that did the trick. So Nevertheless, we are back happy again. π
42 Replies
- brogyiBrass ContributorOur issue is gpt resolved too. MS confirmed, that there was an active issue, and they resolved it, no more information given to me. And like magic, the connector started to work.
- johndpalmBrass ContributorI get the same error trying to add a new connector or configure an existing one. Watching this thread for any updates or fixes.
- SimonWeissCopper ContributorHi! This issue was solved by Microsoft today and it works for me again.
Hope it works for you guys too- Bhargav56Brass ContributorNope still not working for me atleast.
Something went wrong.
Login required
RequestId: unknown
Server: DB8XXDDDDXXX
Date: 2021-12-02 12:35:18 +0100 - BR180Copper ContributorReally? It isn't working for me so far...nor in web app. Maybe I'm hooked to a server they didn't fixed yet...Thanks for the post, anyway.
- Bhargav56Brass ContributorIs it still working for you?
Today we are getting new error..
Connectors have been turned off for this mailbox by the admin. Contact your admin if you want to have connectors turned on.: Access to Connectors is disabled.
https://answers.microsoft.com/en-us/msteams/forum/all/how-to-enable-or-disable-connectors-in-office-365/33d4b2c1-00eb-420a-ad83-01a2b42ad098
I tried following this, settings seems to be fine but no luck
Thanks,
Bhargav
- brogyiBrass Contributor
My patience is run out. The issue is existing more than 7 days, no solution. So I also did open an MS ticket. I did wrote every piece of information. Unfortunately, when first Microsoft called me, I was unable to speak with them, because I was at a meeting. So they wrote me some instructions to try. I explicitly wrote down that the problem can be reproduced via web but these tips I got:
Hint: it did not solve my issue, but you can try.
1. Compatibility mode
Right-click the MS Team icon on the taskbar then select quit.
- Then right-click the MS Team icon on the desktop > select properties > Under the compatibility tab, check the "Run this program in compatibility mode for" option then select Windows 7 from the dropdown list
- Right-click the MS Team shortcut on the desktop > select run as administrator.
2. Clear cache
Fully exit the Microsoft Teams desktop client. To do this, either right click Teams from the Icon Tray, select βQuitβ. Or run Task Manager and fully kill the process.
Go to File Explorer, and type in %appdata%\Microsoft\teams.
Once in the directory, delete any file in the following folders:
%appdata%\Microsoft\teams\application cache\cache
%appdata%\Microsoft\teams\blob_storage
%appdata%\Microsoft\teams\Cache
%appdata%\Microsoft\teams\databases
%appdata%\Microsoft\teams\GPUcache
%appdata%\Microsoft\teams\IndexedDB
%appdata%\Microsoft\teams\Local Storage
%appdata%\Microsoft\teams\tmp
3. Reinstall Teams
- brogyiBrass ContributorIt is not going to help, /but I wrote this above/ if you have exactly the same problem and same symptoms as mine. But it could resolve the problem if you have only client side / application problem. I could not know, just shared the information.
- dave99gallowayCopper ContributorI was getting this error with a brand new channel I created today. I worked around it by VERY quickly clicking on the "Incoming WebHook" button before the error messge popped up. Took several attempts but surprisingly worked.
- Bhargav56Brass Contributor
dave99galloway For us, its working on other Teams, but only NOT working on one.
We tried to open it in web browser, use inspect mode.. We somehow feel there is an issue with channel mail authentication, but no idea why all of a sudden it is working like this.- BR180Copper ContributorConfirm what you're saying, message error asks me for a login...I really hope I don't have to recreate the affected teams, I prefer a kick in the **bleep**...
- BR180Copper ContributorIt's only a workaround...hope they fix it soon, anyway if you click on three dots on the left menu in Teams, search for "incoming webohook" app, then you can create a webhook without quick-hand intervention...
- BR180Copper Contributor
Same problem here, no solutions, nothing worked (readd the owner, enable/disable connectors).
- Bhargav56Brass ContributorDid you try raising a support case with Microsoft?
- dave99gallowayCopper Contributor
Bhargav56 no - i thought they might reply here....
- dave99gallowayCopper Contributor
- Bhargav56Brass ContributorOhh it worked? Strange, we are still unable to. I tried to remove some connectors to see if there was any issue with them, but no luck. Post us further updates.
- brogyiBrass ContributorWe have exactly the same problem. All channels and all users are affected. The problem started 2 days ago. I think this is a global problem, yet did not found any information to confirm.
- Bhargav56Brass ContributorStrange this is, if you got any info OR if it got fixed for you.. please tell here
- I'd still recommend opening a support case, might as well be something on the backend.
- Check with some other Team just to exclude the possibility that there is some ongoing issue. And then open a support request and report this.
- Bhargav56Brass Contributor
VasilMichev I have other Teams as well and there it is not having any issue in opening connectors and configuring them. Only with this MS Teams group I have the issue. Not sure what is wrong.