This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 24%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEN%3C/text%3E%3C/svg%3E)
We have a daily SSIS-job that runs in 3 environments. The job runs an SSIS-project that executes multiple SAS-scripts (on a seperate SAS-server per SSIS-environment).
There's never been any problems with this SSIS-project, until today. Although the SSIS-jobs appears to run well, and appears to execute the SAS-scripts, they don't actually get executed (on any of the SAS-servers).
According to the Execution Log in SSMS, each SAS-script is successfully executed. However it says that each script finished in under 1 second (a successful execution normally takes many minutes). And on the SAS-server side we don't find any trace of the scripts having been run (no log files are generated).
The SAS-scripts were successfully executed yesterday (and each day before that, for multiple years). We haven't changed the SSIS-project or the SAS-scripts in any way since then. And there apparently haven't been any changes to our infrastructure, network, drivers, etc. Not for SAS, nor for SQL Server. At least not according to anyone we've been in touch with so far...
It appears as though SSIS thinks it's communicating with SAS, while SAS ignores SSIS. And there's no errors or warnings.
If I try to execute a SAS-script manually by running an individual SSIS-package, the same thing happens: It appears to run well, but doesn't actually execute the SAS-program.
Do you have any suggestions on how to troubleshoot this?
Hi @Erik N. Martinsen ,
Have you tried to re-build the SAS-scripts and then run it for a try?
Thanks but the SAS-scripts are stored on a SAS-server, and run via an Execute Process task:
The arguments use the following script (unchanged for 3 years):
#!/bin/sh
dtstamp=$(date +%Y%m%d_%H.%M.%S)
sas_dir=/opt/sas94/$1/sashome/SASFoundation/9.4
script_dir="/data/DVHANALYSE/scripts/projects/monaco/current/sas_code"
log_dir="/data/DVHANALYSE/scripts/logs/monaco"
suff=".sas"
echo "This is running Monaco $2"
echo "env: $1" >> $log_dir/plink.log
echo "pgm: $2" >> $log_dir/plink.log
pgmname=$2
logname=${pgmname%"$suff"}"_$dtstamp.log"
#
$sas_dir/sas $script_dir/$pgmname -log $log_dir/$logname
#exit 0
When I execute the task, it immediately completes successfully. But there's no trace of anything happening on the SAS-server.
This solved the problem: