Desktop productivity for business analysts and programmers

Why EG export/import wizard work but proc export/import fail?

Reply
Occasional Contributor
Posts: 5

Why EG export/import wizard work but proc export/import fail?

I just started my new job and they only use SAS EG on a UNIX server there. The first challenge I met is failure in using proc export/import to/from PC server. The weird thing is the same codes successfully worked on one of my coworkers' computer, and I can export/import without problem if I use wizard.

The error I got for EXPORT is:

ERROR: CLI error trying to establish connection: [Microsoft][ODBC Excel Driver] The Microsoft Access database engine cannot open or

       write to the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view and write

       its data.

ERROR: Error in the LIBNAME statement.

Error:  Unable to open file filedirectory\filenname.xlsx. 

The error I got for IMPORT is:

It does not exist or it is already opened exclusively by another user or you need permission to view its data. 

Anyone who have ran into similar situation or have a clue about this? Thanks!

Esteemed Advisor
Posts: 5,198

Re: Why EG export/import wizard work but proc export/import fail?

To understand this, you need to understand what runs where.

PROC IMPORT runs in the SAS server session, typically named SASApp. That is probably a remote host session.

Import/export tasks are executed on the EG client.

You need to fins out what's the difference how your colleague EG/server/authisraztion/etc setup differs from yours.

Data never sleeps
Respected Advisor
Posts: 3,062

Re: Why EG export/import wizard work but proc export/import fail?

One possible explanation is your Unix user account does not have the same permissions as your co-worker. Check with your Unix admin.

Ask a Question
Discussion stats
  • 2 replies
  • 598 views
  • 2 likes
  • 3 in conversation