Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*AW\:\s+Preschedulecmd\s+not\s+executed\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*AW\:\s+Preschedulecmd\s+not\s+executed\s*$/: 2 ]

Total 2 documents matching your query.

1. AW: Preschedulecmd not executed (score: 1): Author: Salak Juraj <J.Salak AT ASAMER DOT AT>; Date: Mon, 7 Nov 2005 19:13:07 +0100; Hi, PreschedCMD starts a program, not a plain file. The last line in OPT file should be: Preschedulecmd "C:\WINNT\SYSTEM32\cmd.exe /C D:\Hyperion\Export\Scripts\EssExport_Schedule.bat" Note, the TSM; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-11/msg00136.html (14,030 bytes)
2. Re: AW: Preschedulecmd not executed (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Tue, 8 Nov 2005 08:04:39 -0700; The *SCHEDULECMD commands are launched via the command interpreter specified by the ComSpec environment variable, which points to the cmd.exe file on Windows NT systems. cmd.exe supports the launch o; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-11/msg00162.html (16,882 bytes)

Current List: 1 - 2
Page: [1]