I need to correct one piece of information I provided earlier. Both machines are running Windows 7 Professional. Here are the answers to your questions. Any tips or suggestions are greatly appreciated. Is the file being created ever, Yes/No? Yes. When I manually run or schedule the program on my computer the file is created/converted without issue. When the program is manually run on the production virtual machine the file is created without issue. When the program is scheduled through the task scheduler on the virtual machine, the file is not converted and the .vbs file/script is left behind. When we double click the .vbs it converts to the .xlsx file we need, but that does not work for programs that are automated to run and email to a distribution list. Is the file being created consistently? The .xls is being created consistently. The file is converted on my machine to .xlsx consistently. Are you trying to create both an XLSX and XLS file? The program first outputs the report as .xls using ODS TAGSETS.EXCELXP and then is supposed to convert that file to a .xlsx. Why is there an XLS file involved in this process at all? Is that the XML output from ODS TAGSETS.EXCELPXP you're referring to? That is how we initially set up the reports. I don't believe that is the issue since my machine can run the program without issue from the task scheduler. Are you creating the VBS script each time, or just running/calling it each time? The VBS script is created each time because it is specific to the report that is run, and the file name contains unique information (i.e. month, year, date) so each time the program runs the resulting file name is different. What happens if you call the VBS script from a command line or SAS, not in Batch? Again, the only time there is an issue is when the program is run from the task scheduler on our virtual machine that runs our production reports.
... View more