Asp:activex cannot create Scripting.FileSystemObject object solution _ Application Tips

Today encountered a problem, an ASP site generated static page times error:

Microsoft VBScript run-time error ' 800a01ad '
ActiveX part cannot create object: ' Scripting.FileSystemObject '

In fact, this problem is more common, the error is due to the server does not support FSO components. such as wind, science, and easy to move these ASP's mainstream CMS system often encounter this situation, because they are to take the static generation mechanism, the need for FSO component support. Before you begin, it is necessary to test the server's support for the FSO component with an ASP probe, usually using a Windows 2003 System server.
The following is my specific solution, for each of the causes of the error may be caused by the corresponding analysis, I hope you can help.

1 "scrrun.dll" file is not registered. Line C:\WINDOWS\system32 folder, see if there are any scrrun.dll files. If not, go to the System installation directory I386 folder to copy one over. Next, Start menu-> run the following command to register the FSO component:
Regsvr32.exe%windir%/system32/scrrun.dll This opens the server to the FSO component support, if you want to turn off the FSO component, run the following command:

regsvr32.exe/u%windir%/system32/scrrun.dll Normal to here, your problem can be solved.

2 if not, check to see if the browser has disabled ActiveX controls. Normal is not, unless the server, the security level will be strictly limited. If this is the case, adjust the browser's security level to medium-low.
3 Your server itself does not support the FSO component.
4 Consider the issue of permissions. In turn, do the following:
Start Menu-> Run->regedit-> OK, find Hkey_classes_root\scripting.filesystemobject in turn, right-click "Permissions" plus everyone, Internet Guest account (IUSR ...) User's permissions, restart IIS to resolve.
5) Attached: server does not support the solution of scripting.dictionary components
The above steps can be a perfect solution to the problem of the ActiveX creation object failure. If you also see problems that do not support the Scripting.Dictionary component, the solution is similar, as the first step is to execute the regsvr32.exe%windir%/system32/scrrun.dll command. If it is not resolved, consider permission issues, and you can add permissions to the object in the registry by referring to step fourth. Extrapolate, if you encounter similar problems again, know how to solve it!
6) Attached: Server.CreateObject failure solution. A similar error may be prompted when we execute the program, as follows:
Server object error ' ASP 0177:800401f3 '
Server.CreateObject failure
/include/test.asp, line 38 open test.asp, check the source 38 line near, look at the creation of the object of the written error, the standard writing should be:

<% Set FSO = Server.CreateObject ("Scripting.FileSystemObject")%>
This situation is mostly caused by the careless programmer. In fact, the Scripting.FileSystemObject component can be renamed, this will increase the security of the server, we can change in the registry, the following methods:
Start Menu-> Run->regedit-> OK, find Hkey_classes_root\scripting.filesystemobject in turn, right-click "Rename", Then perform the first step to register the Scrrun.dll file. Note that when you write the program, you create the object with this new name, or you will report an error. 7) with: IIS self-contained components
There is a point where these problems are due to the components of the IIS itself, and the following common IIS components are provided for reference:
MSWC. AdRotator
MSWC. BrowserType
MSWC. Nextlink
MSWC. Tools
MSWC. Status
MSWC. Counters
SWC. PermissionChecker
Wscript.Shell
Microsoft.XMLHTTP
Scripting.FileSystemObject
ADODB. Connection Summary, About ActiveX can not create Scripting.FileSystemObject objects of similar problems, the main solution is similar, mainly the idea to clear: first consider the component registration problem, followed by the component permissions, if the server configuration no problem, then carefully check your program source!