Jaa

Unable to Find VBScript Script Engine?

  • Artikkeli

Everyday SCOM teaches me something new, and necessarily about SCOM!  Recently I was onsite with a customer and we hit an OperationsManager event log that was full on red - never a good sign.  It appeared that every script SCOM tried to run failed...VBScript, JScript, etc.  So we selected an entry at random and tried to replicate what SCOM was doing - to manually run the script from the same location and with the same parameters as SCOM.  We got an unexpected error, “Can’t find script engine “VBScript” for script “<path to script>”.  

Normally that means you need to reregister VBScript.dll, but that didn't help.  After some careful searching, we found this article https://lifeofageekadmin.com/cant-find-script-engine-vbscript-for-script-error-on-windows-7-and-windows-2008/,  Basically the antivirus software had changed the regkey that should point to the VBScript.dll.  Fix that bad entry and the scripts all run fine.

  1. Logon to the server as an administrator.
  2. Open the registry editor (regedit.exe) and navigate to the following registry key.[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
  3. Check the path of the Default registry key, it will most likely point to the path of your Anti-Virus Product.
  4. Right click on InprocServer32 and select permissions. Give the Administrators group full access.
  5. Modify the Default registry key and change the path to C:\Windows\system32\vbscript.dll
  6. Change the regkey permissions back.

vbscripterr3

 

Thank you "LifeofAGeekAdmin!" and Mike Z!  Good find....