IIS reported that the script language VBScript.encode error solution was not found on the server

This article mainly introduces the IIS report can not find the script language 'VBScript.encode' error solution on the server, in fact, this is a server security settings, the general virtual host will be disabled, need friends can refer to the VBScript The .Encode component is often used to encrypt some of the ASP's Trojan backdoors to achieve a kill-free effect, and some authors of the program will also use encryption in ASP to protect copyright.

Occasionally, a program was sent to the server, and the program reported an error:

The code is as follows: Active Server Pages error 'ASP 0129' The scripting language 'VBScript' could not be found on the server. Encode' /config.asp, line 5

According to the reason that the program was debugged locally, no problem, so I found the config file in the root directory of the website, looking at the 5th line, it is actually some garbled! Hey, it turned out to be encrypted, and the author of the program has an encrypted content for copyright.

So I found out what VBScript.encode is!

VBScript.Encode This component is often used to encrypt some ASP Trojan backdoors to achieve kill-free effects, and some authors of the program will also use encryption in ASP to protect copyright, but VBScript. Encode's encryption function is very weak, it is easy to be restored by the source code, and in the asp backdoor free killing field, it is used the most, then we naturally think that you can disable the VBScript.Encode component to achieve the encryption script The purpose of the failure, so that a lot of killing asp Trojans useless.

Disable VBScript.Encode (using IIS as a web server and virtual host user):

Run regedit to open the Registry Editor, expand to:

Code As follows: HKEY_CLASSES_ROOT\\VBScript.Encode Right click - Permission - remove the read permission of the users group or the denied permission to join the virtual host user group or directly delete the VBScript.Encode registry key, after modifying the registry, Restarting IIS and then opening the encrypted file will prompt you: the scripting language 'vBScRipt.EncOdE' is not found on the server.

Now that I know what the reason is, then choose a way around it, Baidu vbscript.encode decryption, everywhere, just pick one.