Import file in EG server. The file source becomes #LN00001

[SullivanC]

When I import external(local) file in SAS server, the code in the import node shows that infile become like #LN000001. The import node works. However when I copy the code from the node with physical path instead. It fails. Howe the amend the code for infile path?

[Kurt_Bremser]

When you use the import wizard in EG, the following happens:

- EG converts the input to a standardized textual format; in case of Excel files, a MS-supplied module is used for that

- the resulting text file is copied to the WORK location on the server with a #LNxxxxx name

- EG writes a fitting data step and executes it on the server; this is what you see in the log

This means that the code you see in the log can't be run on its own, ir needs to be run as part of the import task that was created with the wizard. Depending on the type of infile, you will have to write a data/import step on your own or you can copy the code from the import task, but you will have to take care of the "copy to the server" part.

So the next questions are

- what type of file are you importing?

- what infrastructure is available for making the file "visible" to the SAS server process? (shared directories, sftp, ...)

[SullivanC]

Thanks.

I imported csv from network disk.

I'm not sure whether it is the problem of metadata.  If I have not registered the file to the metadata, I cannot use the path directly?

[Kurt_Bremser]

---

@SullivanC wrote:

Thanks.

I imported csv from network disk.

I'm not sure whether it is the problem of metadata.  If I have not registered the file to the metadata, I cannot use the path directly?

---

Very often network paths for data sharing/storing from desktops are not mounted on application servers. Check that with your network/system admins.

Also please post the log from the failed step, using the {i} button.