I have an issue with Windows SP1 workstations that are unable to download patch files from the replication share.

The error reported is:
[Timestamp] DownloadSMBFile: unable to copy file from: '[replication share]/thirdpartypatchfiles51.zip.6c279c1c6cb41e1054993eaf0ab52470' to: 'C:\Program Files\Dell\KACE\thirdpartypatchfiles51.zip': (2) The system cannot find the file specified.

The file in question is present, replication is working. The error continues after rebooting the workstation, the machine managing replication, and the KBOX 1000 server. I've also tried doing a replication inventory and restarting replication, to no effect, but then replication seems to be working fine anyway.

This error has been occurring for weeks, currently on 35 machines out of 1100. Most machines don't have an issue accessing the share and downloading the file.

Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


what os is your replication share on?

Answered 09/18/2012 by: SMal.tmcc
Red Belt

Please log in to comment



I logged a ticket with KACE support and the issue has now been resolved.

The eventual fix was:

1)Delete the affected file from the master repository on the KBOX server

2)Download patches from KACE again so that this file was recreated in the master repository

3) Create a new share (test only) and replicate all files to this to obtain a copy of the affected file.

4) Delete the affected file from the production share and replace it with the new copy of the file from the test share.

In other words it looks like the affected file was corrupted, and we had to go through steps to generate a new copy and place this on the replication share. Mind you most machines downloaded this file fine, so maybe some metadata relating to the file was corrupted, rather than the contents.

I've skipped several other steps we took during troubleshooting which weren't effective - we though replication was the issue initially.

Kace support had to perform some of these steps so if you have a similar issue you won't be able to resolve it without logging a ticket.

Answered 10/03/2012 by: ChrisPO
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity