Hi all -    Using SAS 9.4 TS1M5   We (me and several others at a large state entity) have been using code similar to below to connect to Access databases. We are using 32-bit Access databases and 64-bit SAS.   This has been working since we put the code into place many years ago, with many different databases.    libname dbtest PCFILES path="X:\PCFS_TEST\testDatabase.accdb" scan_text=no usedate=yes; Something has changed on our systems about a week ago, perhaps due to a system-wide software patch, upgrade etc., that has resulted in our inability to connect to Access using PC files server. We now get the following error in our log file:   ERROR: A pipe communications routine failed: The pipe is being closed. (232) ERROR: Internal error: unable to communicate with PC Files Server process. ERROR: Error in the LIBNAME statement.   The first thing I did was to google it, and found some proposed solutions, none of which helped 1) A SAS support item (http://support.sas.com/kb/46/541.html) recommending installing newer ODBC drivers. * I tried doing the Access 2010 drivers, then the Access 2016 drivers, neither worked. * Other employees have Office 365, and are experiencing the identical error in the log. So I'm not clear if there is a consistent characteristic of ODBC drivers among the employees.. except none of them work now, when they had worked before. 2) A SAS forum post where the user gave admin role to the process running the task. * I tried this too, no difference. 3) I upgraded to the latest PC files server, no difference.   The SAS page also suggested it is more likely on network drives. This issue occurs on both network and local drives, so no difference there.   We do have servers running SAS 9.3, running the older PC files server version, and this error does not occur on the servers.   Since we haven't been able to figure it out, we have created tickets with the IT support people in our organization, but they seem to not have many ideas. They rarely deal with SAS or PC files server. We can give them the date at which the issue started, but if they roll out many updates at that time (antivirus software, etc.) then they may not know which one caused it, nor know what to do even if they could pinpoint which one did it.   Strangely, among about 5 employees, for all of them it went away a few days after occurring (and after rebooting), and now it has come back for all of us, rebooting or not. Ideally IT would look to see what changed during these times, but again, no luck with that.   So I'm hoping someone here has had some experience this which might help us get to the bottom of this. I have to think there is some SAS or other system environmental info that might be relevant here, which perhaps we could record in the event that this issue resolves for at least one person. Then we can compare it to that environmental info for the users where the issue is occurring, in order to help track it down. Not sure what else to do.   Any ideas at all are welcome! Though I know we can run certain code on our servers, not all our users have access to them. And our servers are locked down with few ports open to the outside world, and some of our SAS code connects to online to run, so the server wouldn't be able to do that. I'm hoping we can get back to where things were when the PC files connection worked on our PCs.   Thank you.   ... View more

Hi all - I am attempting to run some code that seems to run fine on my colleague's computer. We are both using SAS 9.4 on Windows 7. 64 bit desktop SAS.   It occurs when using proc geocode. The log says that a particular variable length is 1136 (it's not, when I look at the dataset properties, it shows the length is 1), then that the system stopped processing because of insufficient memory.   The machine has 16gb of memory, Windows 7 shows about 9gb free, and the memory details are below via the fullstimer option. One thing I'm not clear on is whether "memory 1587.15k    OS Memory 30956.00k" indicates that there may be an actual memory problem.   Can anyone suggest something to try? Though I know the "cnty_name_mod" variable only has a length of 1, I tried deleting it from the dataset (it was the first column/variable in the dataset) and the next time I ran it, it simply said the same thing (except this time it claimed the length of that other variable was 1128) about another variable which was then the first one in the dataset, and still only had a real length of 1.   Thank you for any ideas.   ------- Here is the log from the failed step: ------- 1512 proc geocode method=street data=ADDRESS out=ADDRESS_GEOCODED 1513 lookupstreet=lookup.usm 1514 attribute_var=(tract countyfp); 1515 run; ERROR: The length of variable "cnty_name_mod" in dataset WORK.ADDRESS is 1136. This is greater than the maximum allowed length, 1000. ERROR: The SAS System stopped processing this step because of insufficient memory. WARNING: The data set WORK.ADDRESS_GEOCODED may be incomplete. When this step was stopped there were 0 observations and 0 variables. WARNING: Data set WORK.ADDRESS_GEOCODED was not replaced because this step was stopped. NOTE: PROCEDURE GEOCODE used (Total process time): real time 0.01 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds memory 1587.15k OS Memory 30956.00k Timestamp 09/07/2018 02:03:35 PM Step Count 66 Switch Count 0   ... View more