Windows Scripting Component Caching
Posted on Tuesday, Mar 12, 2002 12:00 AM
I've been struggling for the past few weeks trying to find a solution to a problem. IIS caches Windows Scripting Components in memory, and won't let them go. It even keeps them there if the file itself no longer exists. I've found the solution. you MUST restart Microsoft Transaction Server. All of the objects are cached in memory there, under the IIS process. to fix this problem, run the following at the command line:
net stop iisadmin /y mtxstop net start w3svc net start smtpsvc net start msftpsvc
you can omit the smtp or ftp service line if you're not using those services.
I feel alot of stress lifting! I had begin to moving towards writing all business logic in scripting components, but this problem might have stopped that effort, and I REALLY liekd using them. what a great way to start a day!