FTP 426 errors and 1236 win32_status

Hello,

We recently migrated our websites to a new box (windows 2000 to
windows 2003 R2 x64) and now are experiencing problems with FTP
uploads. We are seeing a large number of 426 errors. Its never the
same files that have the error, it seems random.

Here is an example snippet from the log file:

cs-method cs-uri-stem sc-status sc-win32-status
[9]created /temp/wwwavalanche/wwwavalanche/campaign/index.html 226 0
[9]created /temp/wwwavalanche/wwwavalanche/campaign/left_column.jpg
226 0
[9]created /temp/wwwavalanche/wwwavalanche/campaign/left_column2.jpg
226 0
[9]created /temp/wwwavalanche/wwwavalanche/campaign/michigan.jpg 226 0
[9]created /temp/wwwavalanche/wwwavalanche/campaign/right_column.jpg
226 0
[9]MKD /temp/wwwavalanche/wwwavalanche/CollageData/master_pages 257 0
[9]created /temp/wwwavalanche/wwwavalanche/Connections/boyne2.asp 226
0
[9]created /temp/wwwavalanche/wwwavalanche/Events/description.html 226
0
[9]created /temp/wwwavalanche/wwwavalanche/Events/index.html 426 1236
[9]created /temp/wwwavalanche/wwwavalanche/Events/index-retry.html 226
0
[9]created /temp/wwwavalanche/wwwavalanche/GlobalAssets/Contribution
+Definitions.properties 226 0

FTP error 426 is "Connection closed, transfer aborted"
Win32-status 1236 is "The network connection was aborted by the local
system."

These errors are causing problems with our nightly updates to the
website. Does anyone know how to fix these?

Re: FTP 426 errors and 1236 win32_status

On May 24, 11:38 am, rkneeshaw wrote:
> Hello,
>
> We recently migrated our websites to a new box (windows 2000 to
> windows 2003 R2 x64) and now are experiencing problems with FTP
> uploads. We are seeing a large number of 426 errors. Its never the
> same files that have the error, it seems random.
>
> Here is an example snippet from the log file:
>
> cs-method cs-uri-stem sc-status sc-win32-status
> [9]created /temp/wwwavalanche/wwwavalanche/campaign/index.html 226 0
> [9]created /temp/wwwavalanche/wwwavalanche/campaign/left_column.jpg
> 226 0
> [9]created /temp/wwwavalanche/wwwavalanche/campaign/left_column2.jpg
> 226 0
> [9]created /temp/wwwavalanche/wwwavalanche/campaign/michigan.jpg 226 0
> [9]created /temp/wwwavalanche/wwwavalanche/campaign/right_column.jpg
> 226 0
> [9]MKD /temp/wwwavalanche/wwwavalanche/CollageData/master_pages 257 0
> [9]created /temp/wwwavalanche/wwwavalanche/Connections/boyne2.asp 226
> 0
> [9]created /temp/wwwavalanche/wwwavalanche/Events/description.html 226
> 0
> [9]created /temp/wwwavalanche/wwwavalanche/Events/index.html 426 1236
> [9]created /temp/wwwavalanche/wwwavalanche/Events/index-retry.html 226
> 0
> [9]created /temp/wwwavalanche/wwwavalanche/GlobalAssets/Contribution
> +Definitions.properties 226 0
>
> FTP error 426 is "Connection closed, transfer aborted"
> Win32-status 1236 is "The network connection was aborted by the local
> system."
>
> These errors are causing problems with our nightly updates to the
> website. Does anyone know how to fix these?

:(

Re: FTP 426 errors and 1236 win32_status

On May 28, 6:01 pm, rkneeshaw wrote:
> On May 24, 11:38 am, rkneeshaw wrote:
>
>
>
>
>
> > Hello,
>
> > We recently migrated our websites to a new box (windows 2000 to
> > windows 2003 R2 x64) and now are experiencing problems with FTP
> > uploads. We are seeing a large number of 426 errors. Its never the
> > same files that have the error, it seems random.
>
> > Here is an example snippet from the log file:
>
> > cs-method cs-uri-stem sc-status sc-win32-status
> > [9]created /temp/wwwavalanche/wwwavalanche/campaign/index.html 226 0
> > [9]created /temp/wwwavalanche/wwwavalanche/campaign/left_column.jpg
> > 226 0
> > [9]created /temp/wwwavalanche/wwwavalanche/campaign/left_column2.jpg
> > 226 0
> > [9]created /temp/wwwavalanche/wwwavalanche/campaign/michigan.jpg 226 0
> > [9]created /temp/wwwavalanche/wwwavalanche/campaign/right_column.jpg
> > 226 0
> > [9]MKD /temp/wwwavalanche/wwwavalanche/CollageData/master_pages 257 0
> > [9]created /temp/wwwavalanche/wwwavalanche/Connections/boyne2.asp 226
> > 0
> > [9]created /temp/wwwavalanche/wwwavalanche/Events/description.html 226
> > 0
> > [9]created /temp/wwwavalanche/wwwavalanche/Events/index.html 426 1236
> > [9]created /temp/wwwavalanche/wwwavalanche/Events/index-retry.html 226
> > 0
> > [9]created /temp/wwwavalanche/wwwavalanche/GlobalAssets/Contribution
> > +Definitions.properties 226 0
>
> > FTP error 426 is "Connection closed, transfer aborted"
> > Win32-status 1236 is "The network connection was aborted by the local
> > system."
>
> > These errors are causing problems with our nightly updates to the
> > website. Does anyone know how to fix these?
>
> :(- Hide quoted text -
>
> - Show quoted text -

We are seeing exactly the same problem - Windows 2003 x64 R2 on HP
Proliant DL585 servers. We receive nightly mainframe uploads for SQL
processing and on 8 other servers (non Windows 2003 x64 R2) they work
flawlessly - we recently upgraded 3 of the servers and all three
sporadically and randomly fail FTP uploads from the mainframe. We
have scripted test jobs from Microsoft clients and never see failures
- when we run the jobs from the mainframe (a script that uploads 50
plus files), random files (usually 1 or 2) will fail.

Have you found a resolution to this yet? Microsoft did release a FTP
patch for 2003 but it seems unrelated. Usually we would run Ethereal
to capture a trace of this, but how do you load it on a 3270 or x64 -
it is not supported.

Curious if you resolved this yet.

Thanks.

RE: FTP 426 errors and 1236 win32_status

We are having same kindda issues, were you able to resolve it

Thank you

From http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls =DMUS,DMUS:2006-46,DMUS:en&q=FTP+426+errors+and+1236+win32_s tatus

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

Re: FTP 426 errors and 1236 win32_status

On Oct 5, 7:02 pm, Mahesh wrote:
> We are having same kindda issues, were you able to resolve it
>
> Thank you
>
> Fromhttp://www.google.com/search?sourceid=navclient&ie=UTF-8 &rls=DMUS,DMU...
>
> Posted via DevelopmentNow.com Groupshttp://www.developmentnow.com

I haven't found a solution yet. We did find a workaround by
increasing the retry count on the ftp client application. I'm not
happy with it but it works for now.