Forum Discussion
DanielWM
Sep 07, 2020Copper Contributor
Activating NDI in Teams not working
Hi, we just turned on NDI for our organization, and I see it in my Settings>Permissions panel.
When I try to activate it i get the message saying "There was a problem downloading the file
Try turning NDI on again"
I have tried activating it both on my laptop and my desktop computer with the same error.
I've also tested on several of my colleagues computers and it activates and downloads the files for them.
I've also tested on several of my colleagues computers and it activates and downloads the files for them.
I've added a screenshot of the message I see.
Does anyone know what the issue is and how I can fix it?
- It’s not 100% rolled out so maybe for some reason your account isn’t fully enabled. You could maybe try a new policy and assign to your account but outside of that that’s only other thing I could think it could be.
- swingbadaboomCopper Contributor
I have the same issue... I reviewed the error logs in teams (~/Library/Application Support/Microsoft/Teams/Logs.txt and found the following:
PluginDownloader::downloadAsync - Failed to download and install ndi bundle due to reason=DIR_MOVE_FAILURE, details=Message: EACCES: permission denied, rename '/Users/ben/Library/Application Support/Microsoft/Teams/plugins-tmp/ndi-2020.20.01.11/extracted/libndi.4.dylib' -> '/Applications/Microsoft Teams.app/Contents/Resources/app.asar.unpacked/node_modules/slimcore/bin/libndi.4.dylib'
This indicated that there was a permission issue here: /Applications/Microsoft Teams.app/Contents/Resources/app.asar.unpacked/node_modules/slimcore/bin which is inside the package contents of the application. Mine had system 'read/write access' and everyone 'read'. After updating the folder and its contents to grant read and write for my user the NDI package downloaded and installed into the folder.
However....
I now have another issue in that when I download the NDI package I get a new error saying 'NDI is not supported.'Logs:
slimcoreVersion: 2020.20.11, isSlimCoreHotSwapped: false, reason: NDI not present yet, reasonCMD: NDI not present yet, ndiVersion: 2020.20.01.11, status: success, scenario: 6f6b728c-e35a-4bf8-b1b2-637125d6c133, scenarioName: intialize_ndi, name: intialize_ndi, step: stop, sequence: 1, delta: 262, scenarioDelta: 262, elapsed: 12645, stepDelta: 262, vdiMode: 0, eventpdclevel: 2, Scenario.Name: intialize_ndi, Scenario.Step: stop, Scenario.Status: success,
- PhilippeL1080Copper ContributorHad the same problem, because i was under Windows 7. No problem under Windows 10.
- Pete SkellyCopper Contributor
EA-2020 Any ETA on resolving this issue for macOS users?
- DanielWMCopper Contributor
EA-2020 I am on Windows on both of my computers.
I've just formated and reinstalled windows on my desktop, this didn't help either.
The interesting thing is that it works for all of my colleagues except me.
I've also tried logging on to users in other tenants where I have activated the NDI policy in Teams admin center, this did not help.
- HenryPhillipsNimbitechBronze ContributorHi,
Do your colleagues have different hardware? Do they experience the same issue when signing into your device?
Trying to determine if it is following the device or user.
Thanks
Henry
- It’s not 100% rolled out so maybe for some reason your account isn’t fully enabled. You could maybe try a new policy and assign to your account but outside of that that’s only other thing I could think it could be.
- HenryPhillipsNimbitechBronze Contributor
Hi DanielWM ,
It sound like you must have followed or the following had already been done for your account with the fact that you have the option:
https://support.microsoft.com/en-gb/office/broadcasting-audio-and-video-from-teams-with-ndi%c2%ae-technology-e91a0adb-96b9-4dca-a2cd-07181276afa3?ui=en-us&rs=en-gb&ad=gb#:~:text=Network%20Device%20Interface%20%28NDI%29%20allows%20you%20to%20broadcast,your%20own%20production.%20Turning%20on%20NDI%20in%20TeamsNot sure it would be required for activating the setting itself within your Profile settings but would be interesting to see if this is allowed within Meeting Policies in the Teams Admin Centre. But like I say I would expect this to just impact you at the point of making use of it within a Meeting.
I would do a right click on the Teams icon in the system tray and do get logs. See if there is anyone more meaningful error message wise in there.Thanks
Henry