Sometimes the exact same code on the same OS but on a different machine will not produced the same result, or more likely will produce an error on one machine but not another. If that happens, consider using the SASIQ.EXE utility to verify that SAS is properly installed.
The below macro assumes the sastest folder is below the install folder (!SASROOT). When you run the macro a new subfolder named validate_yyyymmdd.000 will be created. In my case, a 349 page PDF file named sasiq.pdf was created. The first page (see below) is a quick summary followed by details showing expected vs actual checksum values for critical SAS files.
%macro validatesas( path = c:\temp\ ) ; systask command "'%sysget(sasroot)\sastest\sasiq.exe' -outputpath &path." wait ; %mend ;
For more information, see this link: http://support.sas.com/rnd/migration/planning/validation/sasiq.html