为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

How to fix the issue rtmmvras.dll cannot be found

  • 7 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 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?
已附加屏幕截图

被采纳的解决方案

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

定位到答案原位置 👍 0

所有回复 (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."