D ditonth Guest Jan 20, 2005 #21 I presume that the end result is eventually the same. With the application I did, the application pool is only restarted when needed though.
I presume that the end result is eventually the same. With the application I did, the application pool is only restarted when needed though.
1 1swsoft1 Guest Jan 20, 2005 #22 hi ditoh...it´s been 3 days and have no more problems with the wesites... Reclycing in IIS every 5 or 20 minutes is also a good solution cause you prevent the site from going service unavailable than actually wait for it to happen before fixing it.
hi ditoh...it´s been 3 days and have no more problems with the wesites... Reclycing in IIS every 5 or 20 minutes is also a good solution cause you prevent the site from going service unavailable than actually wait for it to happen before fixing it.
R rranieri Guest Jan 20, 2005 #23 Windows 2003 has a limit of simultaneous applications pool. Edit you register: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters] and add this key: UseSharedWPDesktop value (dword) = 00000001 It solved all our problems.
Windows 2003 has a limit of simultaneous applications pool. Edit you register: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters] and add this key: UseSharedWPDesktop value (dword) = 00000001 It solved all our problems.
W webyhost Guest Jan 27, 2005 #24 You can always delete the website and re-create it in Plesk. That fixed my issue...