Answer
Since the script file itself matches a working copy, the cause is usually environmental rather than the script logic. Check that it's being run from the correct IFS_HOME directory (not copied elsewhere), that the machine has enough free disk space for its temporary staging area (the script gathers log files into a temp location before zipping, which needs meaningful headroom depending on how much log data exists), and run it from an elevated (administrator) command window so you can capture the full console output for clues. The script also writes its own log file during execution — if the run fails, that log records exactly what went wrong; if the run succeeds, that log file gets automatically deleted, which is itself a useful signal that a failed attempt actually did complete something abnormal.