“找不到脚本引擎…”/“无法创建指定语言的脚本”错误消息

MediaMonkey 插件（脚本）依赖 Windows 脚本框架运行。如果未正确安装或配置，插件可能会失败或显示错误。

“找不到脚本引擎…”

某些防病毒应用程序可能会阻止脚本注册；如果防病毒应用程序在允许 Windows 脚本引擎运行插件之前尝试扫描插件，并且在扫描完成后无法找到 vbscript.dll 文件，则会出现此错误。

安装Microsoft 补丁MS10-020并运行卡巴斯基互联网安全软件后，有时会出现此问题。

要解决“找不到脚本引擎...”错误，您可以使用 REGEDIT 编辑注册表：

[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{B54F3743-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]

并将“C:\Windows\system32\vbscript.dll”作为键值写入


[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3743-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]

并将“C:\Windows\SysWOW64\vbscript.dll”写入键值

返回顶部

“无法创建指定语言的脚本”

在某些系统（特别是 x64 系统）上，用户访问控制（UAC）可能会干扰脚本组件的正确注册，从而导致上述错误。

要解决‘无法创建指定语言的脚本’：

  1. 以管理员模式运行 CMD（单击 Windows 开始按钮 -> 在搜索栏中键入 CMD 并右键单击，然后选择以管理员身份执行）。
  2. 键入/执行“cd \windows\syswow64”（对于 32 位 Windows，键入/执行“cd \windows\system32”）
  3. 键入/执行“regsvr32 /U vbscript.dll”以取消注册 Visual Basic Script (vbscript) 和 Windows Scripting Host (WSH) 库（如果已注册）
    键入/执行“regsvr32 vbscript.dll”以注册 Visual Basic 脚本 (vbscript) 和 Windows Scripting Host (WSH) 库
  4. 如果已注册，请键入/执行“regsvr32 /U jscript.dll”以取消注册 Java Script (jscript) 库
    键入/执行“regsvr32 jscript.dll”来注册 Java Script (jscript) 库
  5. 键入/执行“regsvr32 /U scrrun.dll”以取消注册 Microsoft Script Runtime 库（如果已注册）
    键入/执行“regsvr32 scrrun.dll”以注册 Microsoft Script Runtime 库
  6. 如果已注册，请键入/执行“regsvr32 /U msscript.ocx”以注册 Microsoft Script Control 库
    键入/执行“regsvr32 msscript.ocx”以注册 Microsoft Script Control 库

    注册这些库后，MediaMonkey 和任何第三方插件/脚本都应该可以正常运行。

    注意：要测试 VBScript，您可以使用以下测试显示系统上的 VBScript 版本：
    http://www.happymonkeying.com/eSupport/Test_VBscript.exe应该显示 VBScript 版本。
    如果无法显示版本，则您的系统上的脚本可能仍然存在问题。

NOTES

  • 编辑 Windows 注册表并非毫无风险。在修改之前，请务必通过在线搜索熟悉 Windows 注册表。
返回顶部

适用于:

Translated automatically (see original)

‘Can’t find script engine …’ / ‘A script for the specified language can not be created’ error messages

MediaMonkey Addons (scripts) depend upon the Windows Scripting framework to run. If it isn’t installed or configured correctly, then Addons may fail or show errors.

‘Can’t find script engine …’

Some antivirus applications may prevent scripts from being registered; this error can occur if the antivirus application tries to scan an Addon before allowing it to be run by Windows’ scripting engine, and fails to find the vbscript.dll file after scanning is complete.

The problem is sometimes introduced after Microsoft patch MS10-020 has been installed and Kaspersky Internet Security is running.

To resolve the ‘Can’t find script engine …’ error, you may edit the registry using REGEDIT:

[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\CLSID\{B54F3743-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]

And write “C:\Windows\system32\vbscript.dll” as key values


[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3742-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3743-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]

And write “C:\Windows\SysWOW64\vbscript.dll” as key values

Back to Top

‘A script for the specified language can not be created’

On some systems (particularly x64 systems), User Access Controls (UAC) may interfere with proper registration of scripting components, resulting in the above error.

To resolve the ‘A script for the specified language can not be created’:

  1. Run CMD in administrator mode (click the Windows Start button -> type CMD in the search bar and right click, then choose execute as administrator).
  2. Type/execute “cd \windows\syswow64” (“cd \windows\system32” for 32 Bit windows)
  3. Type/execute “regsvr32 /U vbscript.dll” to unregister Visual Basic Script (vbscript) and Windows Scripting Host (WSH) library if it is registered
    Type/execute “regsvr32 vbscript.dll” to register Visual Basic Script (vbscript) and Windows Scripting Host (WSH) library
  4. Type/execute “regsvr32 /U jscript.dll” to unregister Java Script (jscript) library if it is registered
    Type/execute “regsvr32 jscript.dll” to register Java Script (jscript) library
  5. Type/execute “regsvr32 /U scrrun.dll” to unregister Microsoft Script Runtime library if it is registered
    Type/execute “regsvr32 scrrun.dll” to register Microsoft Script Runtime library
  6. Type/execute “regsvr32 /U msscript.ocx” to register Microsoft Script Control library if it is registered
    Type/execute “regsvr32 msscript.ocx” to register Microsoft Script Control library

    After registering these libraries MediaMonkey and any third party addons / scripts should work without issues.

    Note: To test VBScript, you can use the following test show the VBScript Version on your system:
    http://www.happymonkeying.com/eSupport/Test_VBscript.exe should show VBScript Version.
    If it fails to display the version, there may still be a problem with scripting on your system.

NOTES

  • Editing the Windows Registry is not without risk. Make sure you familiarize yourself with the Windows Registry through online searches prior to modifying it.
Back to Top

Applies to:

Hide original

这篇文章有帮助吗？