"Spencer" <> wrote in message
news:9deb9e58-8ca1-4d69-a858-...
> We leverage ControlM as our scheduling tool to kick off jobs on our
> Windows 2003 Server. We have noticed that there seems to be an upper
> limit regarding the number of concurrent cscript.exe that will run at
> any point in time under a single users account. We get a return code
> of 1 back and nothing else returned to stdout. Not even the header
> declaring what version of WSH we are running and the Microsoft
> copyright information. It simply fails immediately prior to executing
> any of the script. The same script gets executed around 100 times a
> day or so and it seems when we have somewhere around 20+ cscript.exe
> executing all of a sudden we can't execute anymore and we get
> failures. I am positive there isn't an error in the script and am
> most certain that this is something to do with a maximum number of
> vbscripts executing at a single time. I see no error messages in the
> event log or anywhere else. The script is a simple vbscript and we
> run it using the cscript. I have found some vague references to
> limits and similar problems that others have had regarding this but I
> have found no solution. I am looking for a solution and hopefully it
> doesn't involve re-writting my vbs to a bat file. We need to get this
> fixed asap due to the random nature of the failures and the production
> impact.
> Spencer
>
Slight correction: I saw 51, not 50 concurrent cscript instances.
|
Similar Threads
Linear Mode
