02-18-2015 12:15 AM
I run 64 bit SAS 9.4 M2 on Windows 7 and using PROC EXPORT with EXCELCS engine to export to 32 bit Excel. SAS PC Files service is installed. The workbook I export to has multiple sheets and has xlsb format. I have installed the correct version of PC Files Server to match the bits and SAS version. The problem I have is everything runs fine under my own account but the program hangs without errors under another account we have to run SAS batch jobs. Both accounts have administrator privileges. It's very puzzling, it looks like the cause may be some differences in the account properties/attributes? Would anyone be able to help?
02-18-2015 02:32 AM
Try to use ODS TAGSETS.EXCELXP to create Excel-readable .xml files.
- no 32/64 bit problems
- only Base SAS needed (no PC Files Server)
- will run on ANY platform
This should alleviate all problems arising from different configurations/privileges of the accounts involved
On top of this:
- can do report formatting (PROC EXPORT only delivers data)
02-18-2015 06:30 PM
Thanks for that. Would you have any example code using tagsets for Excel? Just in case, because I'm not familiar with this. Thanks!
02-18-2015 06:40 PM
Here's a simple test:
ods tagsets.excelxp file="\MyDir\class.xml"
proc report data = sashelp.class nowd missing;
ods tagsets.excelxp close;
02-18-2015 09:36 PM
Yes, it runs fine under my own account in batch or interactively. It's the other account we have specifically for batch jobs that is giving the problem. The workbook has quite a few sheets but I wouldnt think that would be a problem.
02-19-2015 01:25 AM
It may be that the other account has problems accessing the PC Files server because of some policies within Windows.