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
almubarak2000Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Languages and Standards

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.