HOME > PHP > PHP Forum > asp กำลังจะตาย รัน ทีhost ไม่มีปัญหาคับ iis บน win2000 and win2000 server ไม่มีปัญหา Server.CreateObject("Scripting.FileSystemObject")
asp กำลังจะตาย รัน ทีhost ไม่มีปัญหาคับ iis บน win2000 and win2000 server ไม่มีปัญหา Server.CreateObject("Scripting.FileSystemObject")
รัน ทีhost ไม่มีปัญหาคับ
iis บน win2000 and win2000 server ไม่มีปัญหา
มีปัญหาที่เครื่อง xp pro_sp1,sp2, xp 2003 server
-Server.CreateObject("Scripting.FileSystemObject")
ใครรู้บอกที...........
ถ้าไม่มีใครตอบได้
- ผมว่า asp กลังจะตาย เพราะ xp ตัวใหม่ๆเอา componant ของ asp ออกเกือบหมดแล้ว
โดยเฉพาะ xp server 2003 sp1
- เน้น .net , xml
ใช้ asp ทำอะไรก็ต้องหามาลงเพิ่ม น่าเบื่อ
...............ว่ามั้ย php ดีกว่าเยอะ.........
Tag : - - - -
Date :
5 พ.ย. 2548 12:08:18
By :
dekbaza
View :
2336
Reply :
2
No. 1
Guest
เอาจากฝรั่งถาม-ตอบ ปัญหาเดียวกันคับ
Curtis
Jan 22 2002, 5:47 am show options
Newsgroups: microsoft.public.inetserver.iis, microsoft.public.scripting.vbscript, microsoft.public.windowsxp.general
From: "Curtis" <[email protected]> - Find messages by this author
Date: Mon, 21 Jan 2002 17:43:59 -0500
Local: Tues, Jan 22 2002 5:43 am
Subject: Can't use File System Object on XP Pro
Reply to Author | Forward | Print | Individual Message | Show original | Report Abuse
I have a bunch of ASPs on my laptop running XP Pro with the built in IIS. I
try to access the File System Object from the code, and it hangs. Is
accessing the File System Object not allowed on the Workstation level? If it
is allowed why is it bombing on me?
It works fine on my server, but I want to demo it from my laptop on the
road. Here's the line that bombs...
set fso = Server.CreateObject("Scripting.FileSystemObject")
-Curtis
คำตอบ...
PRB: Antivirus software causes FileSystemObject calls to hang IIS
View products that this article applies to.
Article ID : 295375
Last Review : July 8, 2005
Revision : 3.1
This article was previously published under Q295375
Important These steps may increase your security risk. These steps may also make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to, or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you choose to implement this process, take any appropriate additional steps to help protect your system. We recommend that you use this process only if you really require this process.
Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.
SYMPTOMS
When you browse to an Active Server Pages (ASP) page that contains FileSystemObject calls, the request for that page stops responding (hangs), and then eventually times out in the browser.
CAUSE
This problem occurs because the Script Blocking feature in Norton AntiVirus software blocks scripting operations that access the file system, such as FileSystemObject. Although this problem is prevalent in Active Server Pages (ASP) Web applications, it can also occur in other technologies, such as Windows Scripting.
Note This problem occurs even if Norton AntiVirus has been disabled.
In August 2003, Network Associates McAfee added a feature that is named Script Stopper. Script Stopper is similar to Norton AntiVirus Script Blocker. Currently, Script Stopper blocks access to the FileSystemObject. However, Script Stopper may do more than just block access.
RESOLUTION
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk. To resolve this problem in Norton AntiVirus, contact Norton AntiVirus Software Support. The following Symantec Web site describes how to remove the Script Blocking feature: http://service1.symantec.com/SUPPORT/nav.nsf/8d071816eedd7cac88256c0e005a96e5/32066c6bf6a78ded88256ab7006a3a25?OpenDocument (http://service1.symantec.com/SUPPORT/nav.nsf/8d071816eedd7cac88256c0e005a96e5/32066c6bf6a78ded88256ab7006a3a25?OpenDocument)
Note You may have to reboot the server after you make the above-mentioned changes to the Norton AntiVirus software.
To resolve this problem in McAfee VirusScan, contact McAfee Technical Support.
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Load balance : Server 01
