|
View previous topic :: View next topic
|
| Author |
Message |
Hank Watson
New User
Joined: 25 Nov 2010
Posts: 6
Location: Miami, FL
|
|
|
|
We have had two jobsteps on different days and in different directories successfully PUT a file. We then have a dir command and both have failed.
We run this job daily and there are dozens of FTP steps and it has run without these errors for years now and just recently we had these two failures (on different days).
The error message:
| Code: |
| EZA1735I Std Return Code = 14426, Error Code = 00002 |
tells us that it was a DIR command (RC subcommand 14) and failed with a 426 error. Error Code 2 is FTP_SERVER_ERROR. This doesn't really tell me what happened.
Here's more specifics leading up to the error:
| Code: |
EZA1736I dir
PC0365 parseCmd: subcommand: dir
SC1368 initDsConnection: entered
EZA1701I >>> PORT 10,7,209,10,52,210
200 Command PORT succeed
EZA1701I >>> LIST
426 Transfer failed
CA1546 SETCEC code = 2
CX0389 main: RC=-0001 cmd_in_progress=14
CX0392 main: last_reply= 426 err=02
PC0945 setClientRC: entered
PC1015 setClientRC: std_rc=14426, rc_type=STD, rc=14426
EZA1735I Std Return Code = 14426, Error Code = 00002
CZ1355 ftpQuit: entered
CZ1436 ftpClose: entered
CZ1436 ftpClose: entered
EZA1701I >>> QUIT
221 bye
|
|
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
| The 426 says the server is shutting down, or the data connection was closed (data set error is unlikely). Have there been ANY network changes of any kind recently? If so, that is probably what is causing your problem -- even simply changing out a switch or router could lead to FTP problems. If your network support group cannot identify any recent changes, you may have to have them do tracing of your jobs to figure out why the disconnects. And yes, this may take a while and be difficult to set up -- but unless you're getting data about line traffic on your FTP sessions, there is little to no chance you will be able to resolve this issue. |
|
| Back to top |
|
|
Hank Watson
New User
Joined: 25 Nov 2010
Posts: 6
Location: Miami, FL
|
|
|
|
Appreciate your response. I had hoped for a miracle, because all my reading led me to believe that we would have to turn on logging or tracing. I guess we'll just wait for it to happen a third time and engage the network team. As you said, it will prove difficult if not impossible to find it. The job executes 27 FTP's and most of them include a dir command before and/or after the put. The two instances we had were 15 days apart and are the first we've seen since running this job (first implemented in 2009 with many fewer steps).
I had been hoping that it was a PORT issue with the return path, but the two that failed used ports that had been used on other days. So, the it's a firewall rule issue got thrown away. |
|
| Back to top |
|
|
|
|
  |
All times are GMT + 6 Hours |
|
