Brethren help me!

Following the latest round of Windows Security Patching, as mandated and inflicted on us by the I.T. group, we have begun to get erratic failures in one of our scripts which appear as: 

Can't spawn "C:\WINDOWS\system32\cmd.exe": Bad file descriptor

[download]
The line in question is: 
my $_retVal = system $ENV{ ComSpec }, '/c', $_fullCmd ;

[download]
Where $_fullcmd is simply the path to another script.

A given machine might execute this line fine many times, then will issue this error repeatedly over a period of a few minutes, before maybe working again. There appears to be no consistency.

I'm hoping someone else may have seen this...

thanks,
~Jeff

In reply to Windows "Bad File Descriptor" problem by HuckinFappy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.