topic Re: SAS/ACCESS Interface to PC Files error in SAS Programming

SAS/ACCESS Interface to PC Files error

bhavya123 — Sat, 14 Oct 2017 11:06:57 GMT

I am getting the following error while running proc import command in SAS 9.4

"The SAS/ACCESS Interface to PC Files is not installed. Please install this module in order to

IMPORT/EXPORT to these file types."

I have SAS and Windows(64-bit) and Microsoft office(32-bit), so I installed SAS PC Files Server(32-bit). But still while running proc import syntax, I am getting the same error.

Please help me resolve this.

Re: SAS/ACCESS Interface to PC Files error

LinusH — Sat, 14 Oct 2017 16:21:07 GMT

Please share the log including the import step.
Have you followed the syntax for using a PC Files Server?

Re: SAS/ACCESS Interface to PC Files error

andreas_lds — Sat, 14 Oct 2017 17:54:11 GMT

Execute

proc setinit; run;

to verify that PC Files is part of your licence.

Re: SAS/ACCESS Interface to PC Files error

bhavya123 — Sun, 15 Oct 2017 03:24:36 GMT

I used proc import syntax below:

PROC IMPORT DATAFILE="C:\Users\Desktop\split.xlsx"

DBMS=EXCELCS

OUT=WORK.SASINVOICES REPLACE;

SHEET='Sheet1';

RUN;

please let me know if I have used the correct syntax.

Re: SAS/ACCESS Interface to PC Files error

bhavya123 — Sun, 15 Oct 2017 03:25:57 GMT

Yes I checked. PC File server is part of my SAS licence

Re: SAS/ACCESS Interface to PC Files error

Kurt_Bremser — Sun, 15 Oct 2017 05:50:50 GMT

You need to install SAS/ACCESS for PC Files, the log is very clear about that. The PC Files Server is something different.

Use the Deployment Manager to install the module; if you can't find it in your SAS depot, get in contact with your local SAS representative so you get a software order that matches your license.

Re: SAS/ACCESS Interface to PC Files error

Kurt_Bremser — Sun, 15 Oct 2017 05:53:34 GMT

BTW if you don't have the module licensed, save your Excel data as csv and import that. No additional license needed for text files.

It's the better method anyway.

Re: SAS/ACCESS Interface to PC Files error

bhavya123 — Sun, 15 Oct 2017 08:00:35 GMT

I have already installed PC file server. But even after the install, the
syntax wasn't working. I checked in the "services" folder also, it was
running.

I guess CSV would work.

Re: SAS/ACCESS Interface to PC Files error

Kurt_Bremser — Sun, 15 Oct 2017 09:18:04 GMT

The PC Files Server is NOT, I repeat NOT, SAS/ACCESS to PC Files.

The first is a special server program for Windows machines that allows non-Windows SAS computers access to the older MS Office formats. The second is a part of the Base SAS package and can be installed on all SAS-supported platforms.

You are missing the SAS/ACCESS to PC Files module, so you need to install/license it.

Re: SAS/ACCESS Interface to PC Files error

Patrick — Sun, 15 Oct 2017 09:23:05 GMT

@bhavya123

And you also did restart all your SAS services/servers after the install?

The SAS log is very clear: The SAS/ACCESS Interface to PC Files is not installed.

Proc Setinit will show you what license file got applied.

Execute also Proc Product_Status which will show you what SAS recognizes as being installed.

proc product_status;
run;

You need to then get in the log something like below:

For SAS/ACCESS Interface to PC Files ...
   Custom version information: 9.4_M3

Re: SAS/ACCESS Interface to PC Files error

bhavya123 — Sun, 15 Oct 2017 10:53:58 GMT

Thanks. I understood your point.
Product_status syntax doesn't show me "SAS/ACCESS Interface...." log

Re: SAS/ACCESS Interface to PC Files error

bhavya123 — Sun, 15 Oct 2017 11:01:11 GMT

@Kurt_Bremser
Thanks for the explanation. Just a reference to what I stated above:

When I ran "proc setinit; run;", I got this in log:
---SAS/ACCESS Interface to PC Files
14MAY2018
Even then this implies that I don't have SAS/ACCESS to PC Files installed?

Re: SAS/ACCESS Interface to PC Files error

Kurt_Bremser — Sun, 15 Oct 2017 17:58:43 GMT

For a module to function, 2 facts are necessary:

- the software has to be installed

- the module has to be licensed

As it looks, you are lacking prerequisite #1. Run the Deployment Manager to check if you can install the software.