Hi All,   We have a SAS 9.4 server and multiple user connecting and working via SAS EG 7.1 The SAS work is redirected from the config file to a different drive on the server.   I just noticed that there are sas tables in the SASAapp folder inside config. After investigation I found the user creating this and I checked the code he was using in EG. He was only doing output in work. Now after reruning all the files are ok transmitted to the correct work folder.   Any idea why the work folder could have been redirected to SASApp and now back to normal ?   Thanks for your input  ... View more

HI All,   I need your suggestion on an issue that our users are experiencing intermittently. From investigation i managed to do until now, they are experiencing I/O errors when transferring SAS tables from work to a file server via the network. This error doesn't appear all the time and that is why it is hard to gather evidence. Platform details: 16 cores server, 128 GB RAM, 250 GB C drive where windows server 2016 is installed, 250 GB D drive where SAS is installed, 3TB S drive where work space is. The throughput is sufficient to and from work drive in terms of SAS requirements and enough free space is on all drives for what the users are doing (using EG clients for manipulating data).   Findings until now:  - user tries to do a simple data step to transfer a table from work to an external file server folder via network - initial size of the table in work area 93 GB (big 2000 tributes table with 3 million records) the table is uncompressed - destination folder is a COMPRESSED folder on an external file server. - I/O error is returned and destination table is damaged (without possibility of repair using proc datasets) - same error may or may not happen on smaller tables like 40 GB but only if other users are writing in the same folder in the same time - did the same test with the 93 GB table and transferred it to the same file server in an uncompressed folder and it worked fine. - then the user moved manually the table from the uncompressed folder to the compressed one and it decreased size to 24 GB - this is the current workaround. The table is undamaged if transferred in this way. - The network connection was monitored during the transfer and nothing seems to fail, also the process was not interrupted - The user also used x command to transfer the file in the compressed folder and it arrived there damaged as well (which makes me think that the windows process that compresses big files somehow is not working correctly)   The question: Naturally I want to say that the conclusion is that when you transfer to a compressed folder using data step that does the compression while you transfer then SAS loses pointer to the rows of the table and ends the file in an unnatural way if the file is too big. What is your opinion? Am I jumping to conclusions? Any other tests I might do? ... View more

Hello everyone,   I am having a problem with new deployment of SAS 9.4 in an enterprise solution.   I received the SAS software depot from one internal colleague who used the SAS Download Manager and I don`t know what options he checked there (so it`s a black box for now - he is out of office). When I am going through the Deployment Wizard the option of selecting a plan is skipped (that window is not even in the wizard) it goes directly to the selection of products. So I can only install as a local full installation.   Like it is normal in an enterprise I want to install it according to a plan (at least a standard one) with metadata and all the servers in one place and the clients in another place. Without being able to chose a plan I can`t do that and it doesn't install any server locally nor being able to configure anything like metadata server, app server, object spawner etc.   The order e-mail clearly specifies that it is a planned installation.   Do you think that something might have been wrongly chosen in the download manager? Or do you think that it is something wrong with the order received by e-mail? ... View more