Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 11319 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to write to distribution location - Update manager issue

RokSaje

Hi guys,

Hope you will be able to help me. I have a problem with update manager in Sophos console. Updating works fine for 3 out of 4 servers. I checked permissions on folder, recreate shared folder on the faulty server but none resolved the issue. It is funny that sophos re-creates folders:

CIDs\S000\SAVSCFXP

moreover it copies all other subfolders (123 in total) but loads of files are missing. For example in crt,rms,sau,savxp,scf I have only 118 files. From other files just customer_ID, escdp.dat, instmsiw and ProductID.dat are copied to the root of SAVSCFXP folder.

Errors I can see in console:

80040404 Threat detection data update failed.
80040408 Unable to write to distribution location [path] for software subscription [subscription-name].
80040401 Software update failed.

Logviewer:

Error Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file

Any clues?

Thanks,



This thread was automatically locked due to age.
  • 0

    Hello Rok Saje,

    so you did already delete/empty the CIDs - did you clean the \Working\ and \Update Manager\Warehouse\ folders - might be an issue with the source for the copy operation? Perhaps it's better to check the SUMTrace logs for the error details - you should find the boost::filesystem::copy_file there and hopefully some details in one or more of the adjacent lines.

    Christian

  • 0 in reply to QC

    Hi Christian,

    Thanks for your reply. I did try to clean Working and Update Manager folder. All folders were re-created and update distribution works fine again for 3 out of 4 servers.

    SUMTrace (where it fails):

    2016-03-11 16:46:01 : Cmd-ALL << [E4037][boost::filesystem::copy_file] Deployment to a share failed because of an unexpected error. Details: boost::filesystem::copy_file
    2016-03-11 16:46:01 : Cmd-ALL << [E400D][ActionDeployCids-Sub0-4][DispatcherPrograms-2016-03-11T16-38-31-33] Action 'ActionDeployCids-Sub0-4' with caller 'DispatcherPrograms-2016-03-11T16-38-31-33' failed!
    2016-03-11 16:46:01 : Cmd-ALL << [I1021][ActionDeployCids-Sub0-4][DispatcherSupplements-2016-03-11T16-39-40-164] Action 'ActionDeployCids-Sub0-4' with caller 'DispatcherSupplements-2016-03-11T16-39-40-164' started...
    2016-03-11 16:46:37 : Fri Mar 11 16:46:37 2016 - No action
    2016-03-11 16:46:39 : Fri Mar 11 16:46:39 2016 - No action
    2016-03-11 16:46:40 : Fri Mar 11 16:46:40 2016 - No action
    2016-03-11 16:46:40 : Fri Mar 11 16:46:40 2016 - No action
    2016-03-11 16:47:20 : Cmd-ALL << [E4033][\\server-path][SAVSCFXP][7ba49542-049c-4154-aad9-cf19a9ec7be5][RECOMMENDED][Could not add network connection to \\server-path; user domain\SophosManagement A Windows API call returned error 64] The deployment to share '\\server-path\CIDs\S000' failed to connect with the error: Could not add network connection to \\server-path; user domain\SophosManagement A Windows API call returned error 64
    2016-03-11 16:47:20 : Cmd-ALL << [E400D][ActionDeployCids-Sub0-4][DispatcherSupplements-2016-03-11T16-39-40-164] Action 'ActionDeployCids-Sub0-4' with caller 'DispatcherSupplements-2016-03-11T16-39-40-164' failed!

    This time only folders (crt,rms,sau,savxp,scf) were copied to shared destination (7 files, 123 folders).

    Not sure what to do. I checked effective access for SophosManagement user on shared folder and it has full control.

    Thanks,

    Rok

  • 0 in reply to RokSaje

    Hello Rok,

    error 64
    is rather "generic" (ERROR_NETNAME_DELETED, The specified network name is no longer available) and indicates a lost connection. Thus it's a lower level networking problem and not a file system or a permissions issue and clearing the usual areas likely won't help. There's a wide range of possible causes - I'd rule out the "source" (SUM) server though as it works for the other destinations (unless the connections use different NICs) - and overload on the target server is one of them.
    Your SUM is writing to shares on remote servers - may I ask why? My gut feeling is that using a child SUM that reads from the parent and writes to a local CID is "better" (more reliable, faster) than writing a remote share from the central SUM (of course if the share is hosted by a non-Windows server you don't have this option).  

    Christian 

Unfiltered HTML