The failure to generate a static file was originally FSO (FileSystemObject) at work

I used to help some friends to build a free space when they encountered some failures in generating static files, but they never found out what the problem was. I initially put my own computer software and hardware application network www.45it.com The same is true when .cn gets the free space test. I recently read some articles to know that the problem with the server FSO (FileSystemObject) is at play. What is FSO? FSO (FileSystemObject) is actually a file manipulation control of Microsoft ASP. This control can read, create, modify, delete directories and file operations on the server (generating static files is one of the powerful functions). FSO is a very useful control in ASP programming.

Of course, there are naturally benefits to its opposite side: because of the problem of access control, many FSOs of virtual host servers become a public back door of this server, because customers can be in their own ASP. The control is programmed directly on the web page to control the server and even delete files on the server. Therefore, many of the industry's web hosting providers have simply turned off this control, leaving customers with less flexibility. Free web hosting providers naturally want to reduce the attack, it is not difficult to understand this control.

Finally, talk about the enabling of server FSO support:

1. First find scrrun.dll in the system disk. If this file exists, please skip to the third step. If not, please Perform the second step.

2, found scrrun.dl_ in the installation file directory i386, decompress with winrar, get scrrun.dll, and then copy to x (your system disk): \\windows\\system32\\ directory

3, run regsvr32 scrrun.dll.

4, if you want to close the FSO component, please run regsvr32 /u scrrun.dll
Refer to other related tutorials "Three ways to disable the FileSystemObject component" http://www.45it.com/Net/201208/31772.htm