搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

How to fix the issue rtmmvras.dll cannot be found

  • 7 回覆
  • 1 有這個問題
  • 38 次檢視
  • 最近回覆由 Lazarus

more options

Just updated to Build 68 and now Firefox will no longer launch a Skype meeting session. The error is in the attached screenshot. The dll is there and registered because there is no issue when I enter the meeting URL into IE, Edge, or Chrome. Has anyone else seen this issue? Does anyone have a resolution?

Just updated to Build 68 and now Firefox will no longer launch a Skype meeting session. The error is in the attached screenshot. The dll is there and registered because there is no issue when I enter the meeting URL into IE, Edge, or Chrome. Has anyone else seen this issue? Does anyone have a resolution?
附加的畫面擷圖

被選擇的解決方法

所有回覆 (7)

more options

rtmmvras.dll = Microsoft Lync Server 2013

You should get help from https://support.microsoft.com

http://answers.microsoft.com/en-US/windows/forum/windows_10

more options

You may have multiple versions of this DLL, so maybe search the hard drive.

more options

Good thought but after searching my hard drive, only one DLL was found in the Office 16 directory which matches the version of MSOffice that is installed.

more options

This sounds like an incompatibility issue between Skype and the MS Office version you use (lync.exe), so maybe try to contact Skype for support.

more options

This literally just started with the update of of Firefox. As I said before, this isn't an issue with other browsers so its not an incompatibility between Office and Lync (Skype).

more options

選擇的解決方法

could you test jscher's suggestion at https://support.mozilla.org/en-US/questions/1264881#answer-1238220 to debug the issue?

more options

After several days of not making any headway, I set this issue aside and it auto-magically fixed itself. Nothing new was installed, no OS or app updates (controlled by SCCM), no changes that I can find. The workstation was shutdown instead of rebooted is the only difference between logging the issue and now. With that said, jscher2000 post is great information, I don't recall seeing that in the "what's new posts."