• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 407
  • Last Modified:

IIS not Responding when try to open text file in local machine.

I have the followling asp file:

<%
Set fs=Server.CreateObject("Scripting.FileSystemObject")
Set f=fs.OpenTextFile(Server.MapPath("testread.txt"), 1)
Response.Write(f.Read(5))
f.Close
Set f=Nothing
Set fs=Nothing
%>

It stops right after the first line. I'm sure everything is correct. The file runs perfectly on my machine at work, network. At home , local machine, it stops responding. After serveral trials I get the message :
HTTP 403.9 - Access Forbidden: Too many users are connected

The problem has nothing to do with the users. I did turn off HTTP Keep-Alives Enabled

any clue?

IIS 6.0 windows Xp prof

thanks in advance
0
almubarak2000
Asked:
almubarak2000
  • 2
1 Solution
 
ZontarCommented:
Does testread.txt actually exist?

Also, try using

Set f=fs.OpenTextFile( Server.MapPath("testread.txt"), 1, -2)

This will allow the file to be opened and read as the default format for the webserver (ASCII or Unicode). Also try -1 (force Unicode) and 0 (force ASCII) for the second argument. If you try to open a Unicode text file as ASCII, this can cause problems.

Also make sure that scrrun.dll exists on your system. If it's missing or corrupted, then you'd not be able to instantiate a FileSystemObject.
0
 
almubarak2000Author Commented:
Hello,

 The file does exist and is not corrupted. None of the parameters solved the problem. It is still the same. When I hit the file around 10 times it complains no more users can be conncted.

Any other possiblities? BTW, all the people I consulted did face the same problem when trying to do the same for stand alone PCs. On networks it works fine.

 Regards,
0
 
ZontarCommented:
It may be that you've got some other apps running on that machine that are confusing IIS because they're also instantiating COM objects. Try shutting down EVERYTHING (including any non-essential background processes) except IIS and a non-MSIE Web browser and see what happens.

Also -- if you're using localhost to access the site, try using http://192.168.0.1/ or the machine name instead, or vice versa.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now