Unable to connect to a shared drive (FTP) via datastage 8.7

clmhwyfe · Post by **clmhwyfe** » Mon Feb 02, 2015 9:09 pm

Hi all,

We are in the process of migrating from 7.5 to 8.7 and we have a situation where we need to pull data from the FTP shared drive

While trying to read a file from the FTP server am getting the below mentioned error

Error executing View Data command:##E IIS-DSEE-PFTP-00071 20:58:29(000) <FTP_Enterprise_0,0> Import record error.

The same worked fine in 7.5 as they were using windows authentication.

Thanks

ArndW · Post by **ArndW** » Tue Feb 03, 2015 5:59 am

Is this "shared drive" on UNIX or still on Windows? If on Windows, you should ensure that the share is mapped to the DataStage user when running in the Background.

clmhwyfe · Post by **clmhwyfe** » Tue Feb 03, 2015 11:45 am

Hi ArndW,

The shared drive is on windows, We use a common ms/rptteam id to access the FTP location and the DS jobs run via my ID or a common project id.

So if we grant access to the project ID on the shared drive, We should be able to access those files ?

clmhwyfe · Post by **clmhwyfe** » Wed Feb 04, 2015 11:50 am

I have acces to the shared drive and am able to connect to the drive with (ms/vs4 (my ID)).

Am able to connect to the server frm the unix command line and able to 'get' files to the datastage server.

But when i try to read the file via FTP staga, am getting the below mentioned error.

>##E IIS-DSEE-PFTP-00071 11:44:13(000) <FTP_Enterprise_3,0> Import record error.
>##E IIS-DSEE-TFOR-00089 11:44:13(001) <FTP_Enterprise_3,0> The runLocally() of the operator failed.
##I IIS-DSEE-TFOR-00094 11:44:13(002) <FTP_Enterprise_3,0> Output 0 produced 0 records.
>##E IIS-DSEE-TFSU-00186 11:44:13(000) <FTP_Enterprise_3,0> processing failed for output /tmp/aptfc2.7184.54d25a6d.0, $pftpFifoConn: exit status = 255. FTP_Enterprise_3
>##E IIS-DSEE-TFOR-00089 11:44:13(001) <FTP_Enterprise_3,0> The runLocally() of the operator failed.
##I IIS-DSEE-TFOR-00094 11:44:13(002) <FTP_Enterprise_3,0> Output 0 produced 0 records.
>##E IIS-DSEE-TFPM-00040 11:44:13(003) <FTP_Enterprise_3,0> Operator terminated abnormally: runLocally() did not return APT_StatusOk
>##E IIS-DSEE-TFPM-00192 11:44:14(000) <node_node1> Player 1 terminated unexpectedly.
>##E IIS-DSEE-TFPM-00339 11:44:14(000) <main_program> APT_PMsectionLeader(1, node1), player 1 - Unexpected termination by Unix signal 9(SIGKILL)

ArndW · Post by **ArndW** » Thu Feb 05, 2015 4:01 am

I'm now unsure of what you are doing - is the error from a FTP stage or from a sequential file stage?

You could write a short Job sequence which uses execute command to do a "ls" on the mapped drive. If the DataStage process doesn't have that drive mapped then this job sequence would show an error.

FranklinE · Post by **FranklinE** » Thu Feb 05, 2015 8:29 am

There should be an Info message line above what you posted that shows a more specific error message. This is typical of my environment, where error messages for external processes don't get flagged for the Fatal designation.

Mostly, though, you have an access issue, not a DataStage issue. You really need your network support people to walk you through your access methods and the requirements for them.