No Visualizo páginas ASP en windows 2003 server

[Myakire]

ASP Error The requested resource is in use
Guest Author - Lisa Shea

The following error - The requested resource is in use - is caused in ASP by the ISAPI caching setting in IIS.

If you go into IIS for our site and go into the Home Directory area, click on the Configuration button. You will see a "Cache ISAPI Applications" option. You should ONLY turn this off for testing purposes. When you turn it off, if two people try to hit the same page at the same time they will get:

The requested resource is in use

When this is off, you will also see an event log entry for EVERY time an ISAPI is loaded and unloaded from memory - i.e. constantly.

Check this box in order to cause the items to cache in memory - therefore always being available.

You receive "The requested resource is in use." error message when browsing ASP pages

From time to time, you will get this error msgs when browsing ASP pages on both IIS 5 and IIS 6. In IIS 5, you might be able to fix it with this kb Cache ISAPI Application Option Causes ASP to Return Error. However, I have seen many times that this KB didn't solve the problem and you continue to get the above error msgs. Especially with IIS 6. The possible cause for this is vbscript.dll reference in registry got messed up and you need to re-register it. Try - regsvr32 %windir%/system32/vbscript.dll.

How do I solve 'The Requested Resource is in Use' errors?
Check your code, make sure all objects are closed and set to nothing. This includes any command or ADOX objects using an Active.Connection property, make sure this property is set to nothing as well.

If you are using thisPage.NavigateURL method, use response.redirect or server.transfer instead - avoid the thisPage object.

Install the latest service packs and security releases (see Article #2151), and make sure you have the most recent MDAC refresh (MDAC Download Page).

If you have 'Cache ASP applications' checked, try unchecking it temporarily (see KB #182059 for more information).

Try changing the address space and/or isolation settings for the application / site in question.

Try dropping and re-creating the application.

In addition to these suggestions, if you are getting Event ID 36 in your event log, see Article #2226.

If you are getting 'The RPC Server is Unavailable', make sure you are not accessing a machine with an underscore in the name, and otherwise follow the suggestions in Article #2147 -- most importantly to restore the IWAM account.

http://classicasp.aspfaq.com/general...se-errors.html