Win 2008 Server - (EOSError) A call to an OS function failed

Advertisement

Socko71
Donor
Joined:
Posts:
20
Location:
Indiana

Win 2008 Server - (EOSError) A call to an OS function failed

When using commandline. scripts or Commander when I try to upload data to a remote server from a Window 2008 server that uses data deduplication I get the error (EOSError) A call to an OS function failed a various files through the tranafer until I abort it. Yet I can copy the exact set of files and folders to a 2003 server that doesn't have data deduplication and it transfers the files with no problem at all. I included 2 files label 2003 and 2008 of the transfers. I aborted the 2008 after a few errors.
Description: 2003 server no data deduplication
Description: 2008 server with data deduplication

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
40,476
Location:
Prague, Czechia

Re: Win 2008 Server - (EOSError) A call to an OS function failed

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

Reply with quote

Socko71
Donor
Joined:
Posts:
20
Location:
Indiana

Re: Win 2008 Server - (EOSError) A call to an OS function failed

martin wrote:

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

Thanks I ran the debug version and included the log file and trace file. Is that all you needed?
  • Winscp Debug.zip (1.43 MB, Private file)
Description: Contains log and trace file

Reply with quote

Socko71
Donor
Joined:
Posts:
20
Location:
Indiana

Re: Win 2008 Server - (EOSError) A call to an OS function failed

martin wrote:

Thanks. I'm sending you a new debug build.

Sending 2 new files using latest debug winscp

Thanks
  • Winscp Debug-Socko71.zip (1.41 MB, Private file)
Description: Contains log file and ytace file using Socko71 debug version of Winscp

Reply with quote

Advertisement

Socko71
Donor
Joined:
Posts:
20
Location:
Indiana

Re: Win 2008 Server - (EOSError) A call to an OS function failed

martin wrote:

Please one more time.

Thanks for putting your time into this issue
  • WinscpDB-Socko71-030615.zip (1.39 MB, Private file)
Description: 2 filss log and trace

Reply with quote

martin
Site Admin
martin avatar

Re: Win 2008 Server - (EOSError) A call to an OS function failed

Thanks. It behaves really strange. It seems that accessing the affected file fails only once. When trying the same operation immediately after, it succeeds.
I'm sending you yet another build to confirm this.

Reply with quote

Socko71
Donor
Joined:
Posts:
20
Location:
Indiana

Re: Win 2008 Server - (EOSError) A call to an OS function failed

martin wrote:

Thanks. It behaves really strange. It seems that accessing the affected file fails only once. When trying the same operation immediately after, it succeeds.
I'm sending you yet another build to confirm this.


sending 2 files log and trace...I ran it until I got 3 errors before aborting
  • Winscp Socko71b.zip (1.45 MB, Private file)
Description: sending 2 files: log and trace

Reply with quote

Advertisement

Socko71
Donor
Joined:
Posts:
20
Location:
Indiana

Re: Win 2008 Server - (EOSError) A call to an OS function failed

martin wrote:

OK, if you do not mind, one more time...

Ran a long time and timed out on connections but does show where it failed on copies
  • Winscp030915.zip (6.19 MB, Private file)
Description: 2 files trace and log

Reply with quote

martin
Site Admin
martin avatar

Re: Win 2008 Server - (EOSError) A call to an OS function failed

Socko71 wrote:

Ran a long time and timed out on connections but does show where it failed on copies
Thanks. Though there's no "A call to an OS function failed" error.

Reply with quote

martin
Site Admin
martin avatar

Re: Win 2008 Server - (EOSError) A call to an OS function failed

OK, I've investigated the log anyway, only to confirm that your system behaves inconsistently. The API call for the same file returns different results each time. There were no errors because the calls that fails is done for logging only. And the later call that's actually used for error-detection does not indicate any error anymore.
So it's looks like either bug in the system or some driver.

Reply with quote

Advertisement

Advertisement

You can post new topics in this forum