You might find that your machine becomes corrupt occasionally. IIS is still running, most functions work (HTML pages and images etc. still serve correctly), but ASP pages no longer run properly. These scripts seem to timeout endlessly, never returning an error message or timeout warning (unless generated by the browser).
What may have happened is that your Windows Access Method (IWAM_<machine>) account has gone out of sync, or your application has changed such that IWAM can no longer function correctly. The easiest solution, according to Stefan B. Schachner, is to re-sync the IWAM account. You can do this in a couple of quick steps at a command prompt:
- CD to the AdminScripts folder (under Inetpub)
- Type cscript synciwam.vbs
For more information on the IWAM account, and more verbose steps at producing the same results as above, see KB #195956 and KB #236855...
After the above failed, one thing that has worked for some people is to change the Application Protection level of the Default Web Site to Low. This is found by right-clicking the application, choosing Properties, and moving to the bottom of the Home Directory tab.
Another thing you might check is whether URLScan and/or the IIS Lockdown tool have been set to disallow ASP. In IIS 6.0 (Windows Server 2003), you can check for this setting under Control Panel, Administrative Tools, Manage Your Server. Scroll down to Application Server and click on Manage this application server. You will get an MMC dialog like the following:
Make sure that Active Server Pages has an "Allowed" status. You can right-click the item and select "Allow" or you can highlight the item and click the "Allow" button on the Extended tab.
If you are using Access, see KB #838306.
If you are using IIS 5.0 and application.lock / application.unlock, see KB #271787.
You may also want to check out Article #2180 if your pages use FileSystemObject and you have Norton Anti-Virus installed.
Finally, if you only have certain ASP pages that are hanging the system, you'll want to check them for infinite loops. The most common is:
<%
do while not rs.eof
' stuff
loop
%> |
Since there is no rs.movenext right after the 'stuff line, the ASP code will just keep processing the same record over and over again, until you flip the kill switch.
[ Comment, Edit or Article Submission ]
Share this:
More about:
|
|
