11-05-2017 09:50 PM - last edited on 11-05-2017 10:11 PM by ChrisHemedinger
We used to have desktop licenses for SAS/PC, and recently moved to a server solution (also PC). And its giving us endless grief. Desktop setups are just so much simpler to work with. We can't import/export files to/from network drives, even with the network drives mapped.
After a while we figured out that we can import, if you use the import step in EG, but not have any code accociated with it. Similarly we can export excel files to the network, but we can't export SAS data files (.sas7bdat) files to the network wit this method. It keeps on giving the error "Unable to export to xxxxxx.sas7bdat. Please ensure the target file is not already open within your project. If so, please close the file and try again."
11-06-2017 04:35 AM
Not sure entirely what the question is here? Obviously your missing some key part on your network infrastructure, be that permissions settings, access. I assume your network is not Windows driven if you can't import/export Office files - if so then you need PCFiles server installed, and use that to read/write as Office is only available on Windows - another is a very long list of reasons not to use Office software of file formats!! As for what your issues are specifically, not much we can do here, this is a SAS Q&A board, not a system analysis contract work board. Consult with your IT group, and liase with your SAS representative, they should be able to do a full analysis of what is installed, what you need permissions to, and what drivers need to be present - if anything this should have been done way back in concept stage before anything was installed.
To note, network based working has many advantages over desktop based work.
11-06-2017 07:26 AM
Windows has many "features" in its security setup that make use of shares quite difficult; there have been many posts on this problem here.
Have your IT people check that the userid's in question have their permissions to use a network share correctly propagated to the server.
Bottom line: it's not a SAS problem, it's a Windows problem. And do not use the crappy Excel file format for data export. Use csv. It's done with a simple data step, and the resulting file can be viewed with any text editor.