Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Redirect and resource is in use 2

Status
Not open for further replies.

RevsEd

Programmer
Apr 2, 2001
33
GB
Hi, I wonder if anyone can help me with a problem I've been getting for the last couple of days? Basically I have an ASP page which redirects to one of two other ASP pages depending on some form input that is posted to it. This was working fine on my IIS NT4 server but has suddenly started to play up.

Basically, the first ASP page is called and executes, but when the redirection takes place it gives me the error "The requested resource is in use." from either of the the two ASP pages. Just to prove that the code is okay I changed the two pages from ASP to test HTML pages and they redirect fine.

As a final note, the error originally displayed as "HTTP 500 Internal Server Error" until I turned off friendly errors in my browser (IE5).

I'm totally at a loss with this - any help is greatly appreciated.

Darren

 
Have you tried rebooting, or reapplying the FP server extensions? I would guess something is corrupt.


hope this helps!
smbure
 
Thanks for offering some input. I've now re-installed the FP extensions and rebooted but it's made no difference. What I've since noticed...

I created an ASP page with a form which calls itself. If I click on the submit button once every 10 seconds the form redisplays and all is okay. However, if I charge in and click repeatedly on the submit button I can get the "resource in use error" to display. Usually within about 5 quick clicks.

I think I've got some kind of timing issue - in that ASP really does think it is still processing the last page. Obviously incorrect but where do I go now? I'm almost at the point of reinstalling the NT Option Pack!

Thanks again

Darren

 
Darren,

I think I have the answer for you. Basically, you need to go to your IIS management console, do a properties on your web application and make sure that the option to cache isapi applications is turned on. That is the default, but my guess is that somehow it has gotten turned off. I have run into this before when setting up a new application.

Here's a MS KB article on the subject:
 
Thanks for your help. I'm really annoyed at Microsoft as I've spent a lot of time on this and have trawled the MS Knowledgebase no end - and not once come across the article you posted me despite numerous searches.

Unfortunately, I reinstalled the NT Option Pack this morning and will never know "for sure" that this was the problem. Reinstalling cured it. In saying that, I reckon you're spot on but I daren't start playing with the server to see if I can recreate the error!

Thanks again for your help - it's very much appreciated.

Darren

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top