IIS access ASP page times wrong The requested resource is in use. Solutions _ Application Techniques

Reboot server IIS service found all ASP pages show http500 error, Khan, in IIS, the Web site ASP program works correctly when the application process protection is set to low, but when the application process protection is set to medium and High, the ASP program displays a http500 error.
Find solutions on the Internet, said is IWAM user password is not synchronized cause, but view log file, found that the log record description and IWAM user password is not synchronized, the specific log is as follows:
Event Type: Error
Event Source: COM +
Event Type: SVC
Event id:4194
Date: 2005-10-13
Event: 13:02:12
Users: N/A
Computer: ABCD148
Describe:
The system called a customer custom component that failed with an exception error. This indicates that there is a problem with the custom component. Please inform the developer of the failure of the component about and provide them with the following information.
Component Prog ID: Server application ID: {3D14228D-FBE1-11D0-995D-00C04FD919C1} server application name: IIS out-of-process Pooled Applications
The severity of this error has caused the process to terminate.
Exception: C0000005
Address: 0x7cf6322e
Call stack:
ole32! Updatedcomsettings + 0X66BF
ole32! Updatedcomsettings + 0x53c7
ole32! Updatedcomsettings + 0x4e7c
ole32! Olereggetusertype + 0x2c3
ole32! Updatedcomsettings + 0xd02b
ole32! CoCreateFreeThreadedMarshaler + 0x17e1
ole32! Olereggetusertype + 0x3b8
rpcrt4! Checkverificationtrailer + 0x5b
rpcrt4! NdrServerCall2 + 0x25a
rpcrt4! Cstdstubbuffer_invoke + 0xa8
ole32! Wdtpinterfacepointer_usersize + 0x6c2
ole32! Wdtpinterfacepointer_usersize + 0x99d
ole32! Updatedcomsettings + 0xb7ce
ole32! Cogetpsclsid + 0x104a
ole32! Wdtpinterfacepointer_usersize + 0x5a7
ole32! Wdtpinterfacepointer_usersize + 0xCCB
ole32! Stggetifilllockbytesonfile + 0x1a5e9
rpcrt4! Ndrsimpletypemarshall + 0x303
rpcrt4! Ndrsimpletypemarshall + 0x26c
rpcrt4! Ndrsimpletypemarshall + 0x177
rpcrt4! Rpcmgmtsetcanceltimeout + 0x14c8
rpcrt4! Rpcmgmtsetcanceltimeout + 0x148b
rpcrt4! Ndrconformantarrayfree + 0x5d1
rpcrt4! Ndrallocate + 0X7C8
rpcrt4! UuidCreate + 0x13e
rpcrt4! Rpcmgmtsetcanceltimeout + 0xe3
KERNEL32!LSTRCMPIW + 0xb7


Event Type: Error
Event Source: COM +
Event Type: SVC
Event id:4097
Date: 2005-10-13
Event: 11:05:35
Users: N/A
Computer: ABCD148
Describe:
The runtime environment detects inconsistencies in its internal state. Please report this error to Microsoft product Support services. Error in __file__ (926): Application image dump failed. C:\winnt\system32\com\dmp\{3d14228d-fbe1-11d0-995d-00c04fd919c1}_2005_10_13_11_05_35.dmp

After viewing the specific HTTP500 error, it appears as:
The requested resource is in use

1, the permission problem, find System32 under the VBSCRIPT.dll and JSCRIPT.dll to read with everyone, run permissions.

2, in accordance with this foreign site to find results.
Discovery is due to missing DLL registrations for VBScript and JScript.
It is hereby noted that the problem is resolved after you re-register the DLL components in the following way.

A:

If you are in IIS for we site and go to the Home Directory area, click on the Configuration button. You'll have a "Cache ISAPI applications" option. You are should only to turn this out for testing purposes. When you are turn it off, if two people try to hit the same page at the same time they'll:

The requested resource is in use

When it is off, you also to the entry of the event log, for EVERY time A, loaded and unloaded from MEMORY-I.E. C onstantly.

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

Also:

We ran into this problem and it is due to a corruption of the
Vbscript.dll as we noticed it is not running.

The steps we took to fix it were:

1) c:/winnt/system32
2) regsvr32 vbscript.dll
3) regsvr32 jscript.dll

This is seemed to fix it although we had to mess around with the IWAM as we
Adjusted then trying to fix the error

Hope this helps

Incidentally this happened due to the roleup patch just
Beware ...