Resolve FileSystemObject related issues in WinXP IIS

filesystemobject|iis| Solution | Problem

With WinXP IIS, it is found that using FileSystemObject always fails to write to an existing file, and cannot delete a file, prompting--no permissions.

Try a variety of settings, but always do not cut the root, spent two days, using Google to finally find a solution, but also to obtain two points about WinXP knowledge points:

1, all the directories in the WinXP are read-only properties, cancellation is only the cancellation of the directory of the file read-only property, and the directory is read-only does not have its read-only meaning.

How do I remove the read-only property of a WinXP (SP2) file?

In Windows XP, all folders have a read-only attribute, and once you remove the read-only attribute, you will see that it is still read-only, but this does not affect the use of the file. Because in Windows XP, "read-only" in folder properties no longer represents the original literal meaning: For a file system, the read-only property of a folder has no practical meaning. Even if a folder is read-only, you can still create it in this folder. Modify or delete a file the folder "Read-only" attribute in Windows XP indicates that the folder is "Custom". Removing the read-only property loses all of the "custom" information for the folder, such as icons. Background. Therefore, the user interface is no longer available in Windows XP to set the read-only property of the folder itself. The "Read only" state in the folder property is always the third State. When you select or clear "Read only" in folder properties, you set the read-only attribute of the file in this directory.

If there is a problem with the operation, check your account permissions and NTFS permissions on the directory you want to install

2, remove "My Computer-Tools-〉 Folder Options-〉 View-〉 use Simple file sharing" before the check, now that you select Sharing and Security on the shortcut menu for the WinXP directory, you can find the Security tab in its dialog box, and then add the IUSR_ machine name to the directory for accessible permissions.

About the same permissions problem with objects marked with object in Global.asa, simply add the IWAM_ machine name (that is, start the IIS process account) to the safe list and set it up.

So, we should know that in the implementation of Global.asa, the OBJECT tag is loaded first and then the specific event is executed. And the Load object is not the same as the account used to execute the specific event script. Remember.

object is not created before Global.asa, and when it is used. Refer to Iishelp\iis\htm\asp\glob822b.htm