Thanks for the follow-up. That's an interesting resolution that I haven't had to touch in years! And not for something like this...
Regards, *ASB* *http://XeeMe.com/AndrewBaker <http://xeeme.com/AndrewBaker>* *Providing Expert Technology Consulting Services for the SMB market…* * GPG: *860D 40A1 4DA5 3AE1 B052 8F9F 07A1 F9D6 A549 8842 On Wed, Apr 5, 2017 at 9:51 AM, Michael Leone <[email protected]> wrote: > I needed to increase the IRPStackSize registry entry (to 22), and then it > all Just Worked. > > On Thu, Mar 23, 2017 at 11:22 AM, Michael Leone <[email protected]> > wrote: > >> I'll admit, I know practically nothing about VBS (altho I do understand >> PowerShell ...). >> >> Anyway, we have a vendor provided set of scripts that suspend, and then >> resume, an application, so we can back it up. (it's EMC SourceOne mail >> archiving). We use Networker as a backup program. So years ago I wrote >> small batch files that run the suspend and resume scripts. >> >> C:\Windows\SYSWow64\cscript "name.vbs" >> >> And it Just Worked. That was like 4-5 years ago. >> >> Last week I upgraded the Networker client software to the latest version. >> And the backup is failing. Do a test run, I see this, in the Networker log: >> >> CScript Error: Initialization of the Windows Script Host failed. (Not >> enough storage is available to process this command. ) >> >> Oddly, if I execute the CMD file from a shell prompt, it all Just Works. >> I do not see this error. So it's only when it executes via Networker, that >> I see this problem. >> >> I've been searching the Interwebs, but not seem to be finding anything >> relevant to my issue. >> >> Anyone have any hints? I'll open a case with Networker, but it might be a >> Windows issue (some environment settings), so I thought I would ask here. >> >> Anyone? >> >> >
